|Target MailUsers will be hidden from the GAL during cloud migrations after they have been prepared and until they have been provisioned. A matched target Mailbox will continue to be visible in the GAL after being prepared.
Power365® does not support migration of the following mailbox settings at this time:
Out of Office Settings
Safe/Blocked Senders from Junk Email Rule
High Resolution User Photo (Root of the Mailbox)
External Calendar Sharing
Mailbox Shortcuts to Shared Mailbox folders
|The Power365 mail migration engine supports migration of an archive to an archive only. Mailbox to an archive or archive to a mailbox migration is not supported.
|The Power365 mail migration engine does not support migration of client-side delegates or delegation for groups.
|The Power365 mail migration engine does not support Modern attachments (links to OneDrive files).
|A duplicate source folder exception occurs when the same folder is copied multiple times as part of multiple migrations.
|Power365 only supports Free/Busy lookup when the recipient is being selected from the GAL.
|Signed and encrypted messages will not be rewritten by the email rewrite service (ERS).
|Additional custom SMTPs added to groups (outside of the email address policy) are not migrated during Group Sync.
|When using Directory Sync Lite, nested groups that exist in the target cloud only cannot be synced as group members.
|When Power365 creates groups using Directory Sync Lite, the groups will be created in the target on-premises hybrid exchange environment automatically, regardless of the origin of the source group.
|Accepted Senders (within Delivery Management) and Moderation settings (in Message Approval) are not migrated by Power365 Group Sync.
|MailTips (msExchSenderHintTranslations AD property) are not migrated by Power365 Directory Sync.
|Discoverability by Power365 may be delayed for new groups or recent updates to existing groups. This is due to delays in graph returning updated information.
|If a "matched" group is manually deleted from the target Exchange forest, the matching status in Power365 is not removed. This may result in errors during the group sync, as Power365 believes the target group already exists.
|Source mailbox retention policies and retention tags applied at the folder level are not copied to the target mailbox during mail migration.
|Power365 does not support changes to the mail-enabled folder's display name on the target.
|Contacts that are linked may not be copied during the mail migration if the PidLidIsContactLinked property is true and the linked ID points to an address hidden from the GAL.
|Prepare Job will fail if Power365 Directory Sync finds an existing contact object in the target tenant that is not created by DirSync.
|Hidden Public Folders will not be provisioned or migrated.
|Messages filtered with Azure Information Rights Management (IRM) will be migrated, but they will not be accessible by the end user. Messages encrypted with Office365 message encryption will be migrated, but they will need to be opened and decrypted via the web browser using the original source mailbox credentials.
|Hidden folders are not copied during mailbox migration.
|For on-premises migration projects, if a user is renamed in the on-premises environment after the upload has completed, Power365 will be unable to migrate that user. The migration will have to be deleted, and re-uploaded.
|If the Discovery Hold (eDiscovery in Office 365) hasn't been enabled, the DiscoveryHold folder will not exist in the Target. DiscoveryHold is a system folder which Power365 does not create. Migration of Litigation Hold settings isn't possible in this scenario.
If there are any items in the purges folder that are within the retention period the item can't be deleted, therefore errors will appear in the logs. The overall status of rollback job will be successful. The purges folder isn't visible to the user. See the below link for information about the retention period settings, which defaults to 14 days.
If the Outlook Categories XML configuration file gets corrupted, the categories will not be copied, however the rest of the sync will continue, and will still be marked as completed if no other errors occur.
Workaround: A workaround would be to open Outlook and edit the categories in any way, which would cause the XML file to be rewritten.
|EWS access policies are not currently supported in Power365. (8061)
|Mail migration cannot be performed on mailboxes that are assigned an Office365 Kiosk License as MAPI connection is disabled for this license type. As a workaround, assign the mailbox an E1 or higher license during the migration, and then revert to the kiosk license.
|For on-premises migration projects, any user “Receive-As” permissions are not copied to the target. (Note: “Send-As” permissions ARE copied.)
|For on-premises migration projects (“on-premises to cloud”, or “cloud to on-premises”), any source forwarding addresses will not be set on the target.
|If the Shared Mailbox has In-Place archive or litigation hold enabled, an Exchange Online Plan 1 or Plan 2 license is required. Therefore, the target mailbox may also require a license. More information from Microsoft can be found here: https://docs.microsoft.com/en-us/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits
|The incorrect domain is selected as the default domain for the Public Folder domain mappings. When the default domain is calculated, the initial domain (IsInitial) is set as default instead of the default domain (IsDefault).
|Public Folder domain mappings are case-sensitive. The DomainName value in the database can be set to lowercase to work around this issue.
|PowerBI reporting is not available outside of the US. (8103)
|Due to an Outlook bug, duplicate rules are added to the target when rules are viewed or edited using Outlook.
|Mailbox migrations will fail if the PowerShell User and the Archive and User Mailboxes are in different Exchange Online regions.
|Holiday calendars may be duplicated in the target mailbox after migration if the OWA holiday calendar is enabled.
|The assigned owner of tasks is not updated with the target username after migration, the owner will remain the source username.
|Although address translation in Power365 will work for attached messages in the .MSG format, it does not work for messages in .EML format or calendar attachments in iCal format. Any attached messages in .EML format or appointments in iCal that are migrated will still have the source display name and SMTP address after migration.
|If a contact with a birthday or anniversary appointment is migrated, and the birthday or anniversary date is changed, the corresponding appointment on the calendar is not updated and a new appointment will be created with the new birthday or anniversary date and the old appointment is retained.
|A Contact linked to a user that is migrated does not migrate with the link.
|After migrating a mailbox with conversation history, the "From" and the Subject for the conversation history items are being left as-is with the source user names still visible in the conversation history items.
|After the mailbox migration completes, the Skype for Business Meeting URL and Voice Mail Message listed in appointments and meetings will not be translated with target tenant information. The Skype for Business Meeting URL will be invalid once the source tenant is switched off.
|Birthday calendar appointments may be duplicated in the target mailbox after migration if the OWA Birthday calendar is enabled.
|When a calendar request is migrated, the "Accept" button does not add the calendar to the target user's Outlook/OWA.
|When using "Reply All" to a migrated conversation history message the source user's name is added to the recipient list.
|Internet calendars are migrated to "My Calendars" instead of "Other Calendars" Any updates to the internet calendars are not received as they are no longer internet calendars on the target.
|Not all Internet, Sharepoint, and Shared calendars for all Outlook versions are migrated. Users must manually re-add any calendars they have permissions to after the migration is complete.
|Folder permissions are not removed on the target when the permissions are removed on the source and synced again.
|Junk mail rules are not copied to the target.
|During mailbox sync and cutover, OOF (Out of Office) Rules, Junk Email Rules, Sweep Rules, and any client-side Rules cannot be read in the source tenant or written to the target tenant. Note that most mailbox server-side inbox rules and OOF settings are synchronized.
The following server-side inbox rules cannot be synced:
Action "Pin to Top"(Outlook Web Access only)
Action "Apply retention policy"
Condition "Classified as"(Outlook Web Access only)
Condition "From any RSS feed"
Condition "From any RSS feed with xxx in the title"
|Migration does not work if an on-premises user has an online archive.
|In a hybrid environment with a "Basic" project, Power365 cannot automatically enable the archive for on-premises source users. Upgrade to a Power365 "Advanced Migration" or "Premium Integration" project, or, as a manual workaround, enable each archive manually.
OneDrive for Business content migration will not be successful, unless the user opens OneDrive for Business from the portal.office.com, if the following is true:
The target user was prepared and synced with OneDrive for Business enabled.
The target tenant administrator deletes the target user and mailbox.
The target mailbox was then recreated and provisioned with OneDrive for Business.
|When there is a Preservation Policy enabled in the Target tenant One Drive or OneNote syncs will fail.
|OneDrive for Business content does not sync when using the Advanced from File project type.
|OneDrive for Business migration does not sync the "Restricted View" sharing permission during Cutover.
|The OneDrive for Business sync will not start during Cutover if the target user's UPN has changed.
|For OneDrive for Business migrations, an error message is not logged when you attempt to migrate a file currently in use.
|Full discovery is needed to detect OneDrive for Business changes.
|Power365 will discover the user’s OneDrive used storage size and quota based on SharePoint’s current information. The used storage size reflects all used space, including the Recycle Bin. Power365 does not migrate the user’s recycle bin therefore comparing used storage between source and target users does not indicate the success of a user’s OneDrive migration.
|OneNote data being edited in the source during a OneDrive for Business migration will log an "item has active edits" error.
|During OneNote cutover, if a Notebook is open in the source, edits will not be reflected in the target when cutover completes.
|OneNote fails to sync when the source is a Team that was converted from an Office 365 Group and the target is an Office 365 Group.
|Microsoft Teams/Office 365 Group OneNote pages are not synced at this time.
|OneDrive for Business migration does not set the folder/files containing shareable links to the matched users in the source.
|Some Site Permissions Levels such as Full Control, Design and Edit are not fully migrated during the OneDrive for Business Final Cutover Sync Job. The default level assigned to the target during migration is the “Contribute” permission level. Read and Contribute permission levels are migrated successfully to the target.
|OneDrive for Business migration does not set permission inheritance flag correctly.
|OneDrive for Business quotas are not set or enforced in the source and target.
|The OneDrive for Business migration report does not contain permissions that cannot be applied because there is not a matching target user in the target tenant.
|The Admin will be listed as last modifying a migrated OneDrive for Business item instead of the actual migrating user.
|When enabled, the OneDrive backup feature may duplicate OneDrive known folders (desktop, documents, photos).
|OneDrive for Business syncs fail if Legacy Authentication is disabled.
|The Admin is removed as an owner in target when Admin is a co-owner of the Office 365 Group in source.
|The Get-BTWorkflowLog cmdlet does not support the -Filter parameter.
|The Set-BTEnvironment -SkipUserDiscovery PowerShell command can only specify the parameter with numerical values as the boolean value (1=True, 0=False). If a user mistakenly attempts to enter a numerical value such as "16", the setting will get set to True because the "1" will be accepted as the boolean value.
|Folder permissions that are removed from the source are not updated on the target when synchronized.
|If a Source user is deleted after being discovered, Power365 will not process the deletion. The user will remain in the UI and in the Target if previously prepared. An error is received when a user is deleted on the Source or Target and the migration (Sync) is run again.
|An error message is displayed and the subfolder on the target is not deleted when the subfolder on the source is deleted and the migration is run again.
|The Public Folder engine will not rewrite source folder email address to target folder email address during content copy.
|Power365 does not support public folder sync if the folder name contains a back slash (\).
|Public Folder content copying will not start if the Provision job reported an error when mail enablement failed.
|If a migrated public folder is renamed after the first synchronization, upon the next sync, the "Folder Renamed" count will be incorrectly incremented again.
|During Public Folder migration, the job can be archived when the status is "Syncing".
|Security group sync and Security group membership sync are not supported. Permission sync on Public Folders and mail folders will use matched users and mail-enabled security groups, but permissions to members of the mail-enabled security group will not be propagated unless the admin has set up the target security group to have the same members as the source.
|If ERS is disabled, the DKIM-Inbound rule is removed. Any custom actions of the DKIM-Inbound rule would need to be set up again if ERS is enabled.
|The group owner is displayed as the author of Team conversations entered by a member who has left the team when synced.
|Synchronized Team conversations display up to 15 user reactions only.
|When an Office 365 Group is converted to a Team or matched to an already existing Team in the target, OneDrive for Business syncs may remove channels from the target Team if they were created directly in the target.
|Microsoft Teams migrated conversation history does not display reactions, emoji, and file icons in Internet Explorer.
|Team syncs may take longer when creating new Private Channels if delays to access to the channel folders occur.
|Due to changes by Microsoft, migration of files for Private Channels is not currently supported.
|The Admin account is removed from the source and target regardless of whether the account was added or it was already an owner. To ensure that removal of temp permissions does not remove any actual owners, connect the source and target tenants using accounts that are not owners of any users, groups, or teams.
|The ERS user's SMTP address is not rewritten to the target SMTP address when they send on behalf of a non-ERS user.
|There is an issue in a project using the Address Rewrite Service (Email Rewriting) with a single source tenant and multiple target tenants. Messages sent from one of the targets ("Target A") that contain the source address of another target ("Target B"), will not be rewritten.
|ERS mailflow jobs do not remove connectors and rules on a tenant when the tenant is removed from the ERS-enabled project.
|If a member of the "DayOne" (BT-IntegrationPro-DayONE) email rewrite group is manually mailbox-enabled after the "Prepare" action has been run, rewrites from the target tenant will fail. As a workaround, when you manually mailbox-enable a mailuser, you must also manually move the mailuser's TargetEmailAddress to the mailbox's ForwardingSmtpAddress. If the mailbox's ForwardingSmtpAddress is empty, opt-in sync assumes the mailbox has already been cutover.
|Messages sent to a unified group in the source cannot be delivered during the Domain Move process.
|When performing a domain move, ensure that AzureADSync has synchronized all proxy addresses to the cloud before restoring the Office365 MX record.
|Directory Sync Lite does not remove the source email address if the object does not have a mail or ProxyAddress attribute value.
|The source email addresses of Office 365 Groups are not added to the target during a Domain Move.
|Free/Busy for Room and Resource meeting requests are displayed as tentative when the request is sent from the target tenant.
|Notification emails from Power365 may be delivered to the Junk Mail folder instead of the Inbox.
|Due to a limitation of Azure B2B, collaboration is not supported across national cloud boundaries. For example, if your Azure tenant is in the public, global cloud, you cannot invite a user as a guest whose account is in a national cloud.
|A timeout error is encountered in the Directory Sync Lite installer when attempting to connect to the SQL Server.
|When installing French or German versions of Power365 Directory Sync, the installation path, localized SSDT install helpers, and SQL installation screens appear in English.
|The Power365 Directory Sync Lite installer cannot install .NET 4.6.1 if the machine is not fully patched and updated.
|During cutover process, target contact's LegacyExchangeDN will be added to the target mailbox as a x500 address by Power365 DirSync, Microsoft Entra Connect Sync will need to sync these changes to O365 Tenant in the cloud. However, sometime the x500 address is not being stamped in the cloud object even though it was synced by Microsoft Entra Connect Sync per Entra Sync log.
|Users must run the Outlook/Desktop Setup Pro agent again if the cutover is stopped after the cutover message is sent and Outlook/desktop is already configured.
|An issue has been found where the Prepare job for users will fail, in the rare instance that a naming convention is used where the only difference between names is a special character. For example, Special#User and Special$User.
|Power365 will not update the msExchRecipientDisplayType,msExchRecipientTypeDetails and msExchRemoteRecipientType attributes if the target mailbox was already provisioned in the cloud directly. Since AADC Sync will not back-sync the changes to AD, the AD local object will not be shown as remote mailbox in the on-prem Exchange environment.
|Office 365 Groups created by Power365 cannot have aliases added to them using the Microsoft admin interface. Aliases can be added using PowerShell.
|ERS Opt-in Groups will be created in the target On-Prem Exchange Environment if the source group was added to a migration profile that has group sync set to continuous mode.
|Cutover email cannot be sent when EWS is set to use an Allow list.
|Outlook Setup Pro does not provide an error message when an incorrect password is entered for Outlook 2016 and the profile is created.
|Outlook Setup Pro incorrectly displays the profiles from Outlook 2013 if Outlook 2010 is currently installed and Outlook 2013 was previously installed.
|When Outlook Setup Pro is run, the cutover job log incorrectly displays the status information for OneDrive for Business and Teams.
|The Desktop Setup Pro agent displays "Success" for the status of Teams before the password for the Teams app is validated.
|Desktop Setup Pro cannot configure Outlook in Windows 7.
|Desktop Setup Pro appears as "OutlookAgent.exe" in Task Manager.
|When Desktop Setup Pro is run more than once, the results of additional runs are not recorded in the summary section of the Cutover job log.
|The content in the Planner is not migrated to the target when syncing Office 365 Groups.
|Email Rewrite Services (ERS) currently does not support Office 365 (Unified) Groups. Attempts to enable Unified Groups will fail.
|After Office 365 Group Mailbox migration, email attachments uploaded to the group files have broken links in the target.
|Cutover does not copy a Office 365 Group's direct access shares if the trustee is not a member of the group.
|DirSync does not enable user objects not created by DirSync.
|In a one-to-many migration scenario where the source tenant’s domain is being mapped to two different target domains in two different tenants in the same project, duplicate users will be created if Power365 is configured to create users. To remedy this, target users should be pre-created in the target tenants prior to the migration so source users can be properly matched with the target users. Alternatively, create a separate project for each tenant pair.
|The Tenant's Org Name is not updated by Discovery if the name is changed after the project is created.
|When a source tenant is removed from a project (by clicking the "X" next to tenant in the project wizard) the user migration records associated with the removed tenant are not removed. This could cause issues if future migration actions are attempted against the orphaned users.
|Only some nested groups used for group migration filtering are added during the first discovery pass.
|The source Room or Equipment Mailbox Capacity is only copied from the source to the target object during the Prepare action. Any changes to the source mailbox capacity will not be reflected during the migration or if Prepare was successfully completed.
|Automatic detection of deleted contacts is no longer support by Microsoft Graph. In order to remediate deleted contacts (for example, during a Domain Move), users will need to run a Reconcile discovery and then mark the un-discovered contacts as deleted or remove them from the database.
|Task request and reply messages are synced when the content filter is set to sync only task items.
|Auto-Expanding Archives are not supported due to the way that Office 365 spreads the data over multiple mail stores. A workaround to migrating such an archive is to export to PST and import manually via Outlook. More information about this issue can be found at https://techcommunity.microsoft.com/t5/exchange-team-blog/office-365-auto-expanding-archives-faq/ba-p/607784 and https://docs.microsoft.com/en-us/microsoft-365/compliance/enable-unlimited-archiving?view=o365-worldwide
|For Email from File project types only, a user’s UPN value must not be changed while the project is being configured via the wizard. Any changes to the UPN value during this process (before the "Submit" button) will cause the user's Exchange attribute to fail to be located.
|The SharePoint Admin Role will be added to the Binary Tree PowerShell account created during project setup when the client has the OneDrive license added to their account. This includes when using the Basic Migration Project. However, the Basic Migration Project does not support OneDrive migrations. Use the Advanced Migration or Premium Integration project type to migrate OneDrive.
|On Windows 10 Enterprise - Build 1511 and Internet Explorer version 11.589.10586.0, the Add Tenant window fails to close after authentication which prevents the tenant from being listed on the Project Wizard screen.
|The Power365 portal requires users to re-authenticate when the browser token expires.
|If a user, with Modern Authentication and MFA, selects the option to "Allow organization to manage this device", Teams will display the source user account instead of the target user account after Teams is reconfigured by Desktop Agent.
|Email Rewrite Service will always use the PrimarySMTPAddress to rewrite the messages. Users with the Sending From Email Aliases feature turned on will have their email rewritten based on the target user's PrimarySMTPAddress.
|Teams conversations under General or Public channels are not migrated.
|When ERS is disabled, external email addresses of MEU's are not removed.
|Delta changes for a Group will not be triggered by only adding only the Group Owner. In order to update the delta, a member must also be added.
|Cloud Rewrite workflows will not run when prepare jobs are queued for both hybrid and cloud-only target objects.
|Public Folders cannot be provisioned. Public Folder provisioning fails with an "Exception creating Remote PowerShell RunspacePool Source" error.
|Forwarding from mailbox cannot be removed if ERS was enabled using skip setting up forwarding.