SOLVED

Office 365 Tenant to Tenant Migration with AAD Connect tool

%3CLINGO-SUB%20id%3D%22lingo-sub-308853%22%20slang%3D%22en-US%22%3EOffice%20365%20Tenant%20to%20Tenant%20Migration%20with%20AAD%20Connect%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308853%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20an%20existing%20Office%20365%20tenant%2C%20which%20we%20want%20to%20migrate%20to%20another%20Office%20365%20tenant.%20We%20currently%20use%20the%20AAD%20Connect%20tool%20to%20synchronize%20user%20accounts%20from%20our%20on-premise%20AD%20to%20Office%20365.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20understand%20it%20is%20only%20possible%20to%20configure%20AAD%20to%20point%20at%20a%20single%20O365%20tenant.%20We%20are%20going%20to%20use%20the%20Quest%20On-Demand%20migration%20tool%20to%20do%20the%20actual%20data%20copy%20-%20this%20can%20create%20a%20set%20of%20onmicrosoft%20usernames%20in%20the%20new%20tenancy%2C%20but%20obviously%20they%20wouldn't%20be%20AAD%20synced.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20the%20only%20option%20we%20have%20to%20create%20the%20new%20onmicrosoft%20accounts%2C%20migrate%20the%20data%20and%20domain%2C%20then%20enable%20AAD%20connect%20against%20the%20new%20tenant%3F%20Is%20there%20any%20better%20option%20to%20reduce%20the%20risk%20of%20email%20loss%20during%20the%20switch%20over%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%26nbsp%3B%3C%2FP%3E%3CP%3EDavid%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-308853%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-308856%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Tenant%20to%20Tenant%20Migration%20with%20AAD%20Connect%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308856%22%20slang%3D%22en-US%22%3EHi%20David%2C%3CBR%20%2F%3E%3CBR%20%2F%3EYes%2C%20you%20would%20need%20to%20stop%20AAD%20Connect%20on%20the%20existing%20tenant%20and%20then%20enable%20it%20on%20the%20new%20tenant%20hard%20matching%20the%20users.%20AFAIK%2C%20there%20is%20no%20proprietary%20or%20third%20party%20tool%20which%20will%20automate%20this%20element.%3CBR%20%2F%3E%3CBR%20%2F%3EBest%2C%20Chris%3C%2FLINGO-BODY%3E
Highlighted
Occasional Visitor

Hi,

 

We have an existing Office 365 tenant, which we want to migrate to another Office 365 tenant. We currently use the AAD Connect tool to synchronize user accounts from our on-premise AD to Office 365. 

 

I understand it is only possible to configure AAD to point at a single O365 tenant. We are going to use the Quest On-Demand migration tool to do the actual data copy - this can create a set of onmicrosoft usernames in the new tenancy, but obviously they wouldn't be AAD synced. 

 

Is the only option we have to create the new onmicrosoft accounts, migrate the data and domain, then enable AAD connect against the new tenant? Is there any better option to reduce the risk of email loss during the switch over? 

 

Thanks, 

David

 

 

1 Reply
Highlighted
Best Response confirmed by Juan Carlos González Martín (MVP)
Solution
Hi David,

Yes, you would need to stop AAD Connect on the existing tenant and then enable it on the new tenant hard matching the users. AFAIK, there is no proprietary or third party tool which will automate this element.

Best, Chris