Microsoft brings tenant migration into one admin workflow
Reviewed by Helen Jones
Microsoft announced cross-tenant orchestrated user data migration on 2 July 2026. Admins can create migration batches through Graph APIs for Exchange mailboxes, OneDrive files, Teams chats, and Teams meetings, then validate licenses, identity mapping, and permissions before committing to a migration date. The feature is public-cloud only and needs the right admin role plus a Cross-Tenant User Data Migration add-on license per user.
Before this, tenant-to-tenant user moves were often stitched together from separate tools and manual checks. That made mergers, restructures, and divestitures awkward for small IT teams because mailbox moves, OneDrive content, Teams chats, and meeting continuity could each fail in a different place. The practical change is that Microsoft is putting more of the migration path behind one orchestrated workflow. For SharePoint and Teams admins, the risk moves from chasing scattered tools to proving the basics early: identity mapping, permissions, licenses, OneDrive scope, Teams chat expectations, and who owns the migration date.
Analysis
Before using the workflow, create a migration readiness sheet with one row per user and columns for source identity, target identity, license, OneDrive scope, Teams chat scope, meeting impact, and validation status.
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Microsoft brings tenant migration into one admin workflow", Collab365 Spaces.