Microsoft 365 Migration Orchestrator (Preview): What It Is, What It Migrates, and Where It Fits

-

 

Migration Orchestrator is Microsoft's tenant-to-tenant migration approach for moving personal user workloads between separate Microsoft 365 tenants (for example in mergers, acquisitions, divestitures, or internal reorganizations). It is designed to migrate workloads in an order that accounts for dependencies and aims to minimize end-user disruption.

What Orchestrator migrates (and what it does not)

Orchestrator supports the migration of personal, user-scoped workloads. In the current preview scope, it includes:

·       Exchange Online mailbox (user-visible content such as email, contacts, calendar, tasks, and notes).

·       OneDrive (personal) content, moved to the target with a redirect left in the source location (no incremental/delta passes).

·       Teams chats and Teams meetings (with dependency on mailbox success for meeting migration).

Orchestrator does not migrate shared data such as Teams teams/channels or SharePoint sites; that content remains in the source tenant.

A crucial rule: it migrates content, not identities

The service moves content from source locations into target locations, but it does not create identities for you. You remain responsible for correctly creating and configuring target users. Identity mapping is a required step for orchestrated migration.

Licensing and availability (high-level)

Cross-tenant migrations require a per-user license (one-time fee) that can be assigned on either the source or target user object. In preview, Microsoft indicates no additional licenses are required specifically for Teams meetings and Teams chats migration.

Orchestrator vs. dedicated OneDrive and SharePoint migrations

Orchestrator is best understood as an end-user workload orchestrator (mailbox, Teams, OneDrive personal). For shared SharePoint sites, and for projects that want workload-specific runbooks, Microsoft provides dedicated cross-tenant migration guidance:

·       Dedicated OneDrive cross-tenant migration: schedules up to 4,000 OneDrive accounts at a time, runs in the Microsoft 365 cloud, enforces a short read-only window, and leaves redirects. It is "one and done" with no incremental/delta passes.

·       Dedicated SharePoint cross-tenant migration: schedules up to 4,000 migrations at a time, is also "one and done," leaves redirects, and supports multiple SharePoint site types. It does not migrate Teams channels/content/structure - only the SharePoint site content.

A practical planning approach is to use Orchestrator for user-scoped workloads, and use dedicated SharePoint migration for shared sites where needed.

Source links (Microsoft Learn)

·       https://learn.microsoft.com/en-us/microsoft-365/enterprise/migration-orchestrator-1-overview?view=o365-worldwide

·       https://learn.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-onedrive-migration?view=o365-worldwide

·       https://learn.microsoft.com/en-us/microsoft-365/enterprise/cross-tenant-sharepoint-migration?view=o365-worldwide

Comments

Post a Comment

Popular posts from this blog

Skype for Business, Lync and Exchange Web Services (EWS) and different DNS Domains- Exchange crawling e.g. for presence

-
Image
Hi all, (This is an updated version 2.2: 09 .07.201 5 ) This blog entry is valid for Lync 2010, Lync 2013 and Skype for Business Server. Generally, I'll write a new blog article, since the conversion history over multiple device and other service have change with Skype for Business 2015 Server. Once this written, I post the link here. there is always confusion in how Lync is crawling Exchange Web Services (EWS). Generally it is necessary to understand how DNS must be implemented: Just remember, identify if you have DNS Split configuration, different internal and external DNS names and what are your SMTP and SIP Domains. Very often you find in Lync/ Exchange deployments an issue, where the Lync configuration show up with empty: EWS Internal URL EWS External URL and EWS Information = EWS not deployed Therefor Exchange Web Service are not connected deployed and several Lync Integration Features are not working, e.g. Presence Information based on your Outlook Calendar....
Read more

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modif...
Read more

Exchange x500 address x500:/o=ExchangeLabs

-
Image
 You have Exchange Hybrid in place. Now you wonder about an address with you see on-premises with all users. This address has the following format: x500:/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOxxxxxx)/cn=Recipients/cn=234xxxx This address is now found in the Exchange proxyAddresses in On-Premises as well as in Entra ID. Additionally you will see them in msExchShadowProxyAddresses The ExchangeLabs is Microsoft internal Exchange Online Organization and therefore needed. This x500 address is created in Exchange Online and sync'ed via Azure AD Connect (Entra ID Connect) back on-premises. If you delete this address on-premises, the connection between will sync this Cloud leading attribute back to on-premisses. If you have multiple Domains and Active Directories connected to your Tenant, this x500 address from your tenant will be added to ALL users. Also to users which are from an local AD without Exchange / Exchange Hybrid. As long AAD Connect/ Entra ID Connect will...
Read more