Warning
This guide describes changes related to an upcoming security update that has not yet been released. The steps outlined here may be completed in advance and will be required prior to the deployment. Additional details are available in the maintenance announcement.
The following article outlines the post-deployment action items you should complete and consider when planning or executing your migration.
Ongoing Projects with Delegated Permissions Limitations
Ongoing Migration Projects on standard tenants using Delegated Permissions will fail on the following scenarios:
- Teams Collaboration Projects
- Teams Private Chat Projects (PCH)
- Documents Migration Projects (OneDrive and SharePoint)
This failure is an expected behavior.
Resolution: Complete the steps listed below for your migration:
- Log in to your MigrationWiz account.
- Open your project and click Edit Project.
- Select your Endpoint (Source/Destination) and click Edit endpoint.
- Select the Endpoint Permissions for your migration.
- Enter the Tenant ID.
- Click on Next Step and go to Project Summary.
- Click Consent Permissions based on the permissions type you previously selected.
Private Chat History (PCH) Limitations
Private Chat History (PCH) migration projects will not be supported with this deployment as part of a planned re-implementation effort.
Resolution: PCH support is temporarily deferred while we complete work on an updated PCH implementation. This work is focused on delivering an improved and more robust PCH experience. PCH migration support will be reintroduced as part of a planned upcoming release.
GCC High Limitations
GCC High Migration Projects will fail with the current implementation. This is an expected behavior for the current implementation on the following migration scenarios:
- Teams Collaboration Projects
- Teams Private Chat Projects (PCH)
- Documents Migration Projects (OneDrive and SharePoint)
Resolution: These types of projects are blocked until a future implementation where GCC High support these workloads.
Email Project Migrations
The following email workloads will fail with the new implementation on MFA:
- Public Folders
- Tenant-to-Tenant (T2T)
- Microsoft 365 Groups
- Shared Mailboxes
Resolution: For each type of email migration, new scopes must be added. Please refer to the following Requirements and Changes on Microsoft 365 Migrations to New Microsoft MFA Enforcement. For more details on which scopes need to be added for each of these migration scenarios.
If you have any further questions or continue to experience issues, please contact Support.