This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Cross-tenant User Data Migration is Now Generally Available
Historically, admins that needed to move mailboxes between Microsoft 365 tenants were required to export or offboard the mailbox to on-premises and then import or onboard the mailbox to a new tenant. Today, we’re thrilled to announce that cross-tenant user data migration is now generally available. Specifically, the cross-tenant mailbox migration and cross-tenant OneDrive migration features previously in Preview are now generally available in our WW environment. GCC, GCC High, and DoD are still in Preview, so currently:
- WW tenants can use these features with other WW tenants;
- GCC High tenants can use these features with other GCC High tenants (Preview); and
- DoD tenants can use these features with other DoD tenants (Preview).
These features provide the ability for admins to complete user data migration between tenants, resulting in a faster and lower-cost migration. This is particularly beneficial for organizations undergoing mergers, acquisitions, divestitures, or splits.
Cross-tenant mailbox moves use an invitation and consent model to establish an Azure Active Directory application used for authentication between tenants. Using Azure Enterprise Application with Mailbox Migration permissions and a client secret, admins can now manage the authorization and scoping of Exchange Online mailbox migrations from one tenant to another. Additional components, such as an organizational relationship and a migration endpoint, are also required.
For more information, see the instructions for using these features using the documentation links above, which will be updated shortly to reflect general availability. Be sure to check out this video on cross-tenant user data migration from the Microsoft Exchange Community Technical Airlift, as well.
We look forward to hearing your feedback on these features.
-- Cross-tenant User Data Migration Feature Team