Hybrid Tenant moving to another Tenant

%3CLINGO-SUB%20id%3D%22lingo-sub-1610106%22%20slang%3D%22en-US%22%3EHybrid%20Tenant%20moving%20to%20another%20Tenant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1610106%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20everyone!%20My%20client%20has%20a%20Hybrid%20%3CSPAN%3Eenvironment%3C%2FSPAN%3E%2C%20with%20some%20users%20that%20are%20synced%20with%20ADConnect%2C%20and%20others%20that%20are%20just%20Cloud%20users.%20Now%20all%20these%20users%20have%20to%20move%20to%20another%20tenant.%20How%20can%20I%20do%20this%20in%20the%20best%20way%20possible%3F%20I%20was%20thinking%20to%20migrate%20first%20the%20mailboxes%20from%20Exchange%20Online%20to%20Exchange%20ONPrem%202016%2C%20since%20the%20Hybrid%20is%20configurated.%20Than%20disconnect%20the%20ADconnect%20from%20the%20old%20Tenant%2C%20the%20synced%20users%20will%20now%20become%20just%20Cloud%20users%2C%20and%20can%20stay%20in%20the%20olt%20Tenant%20as%20Backup.%20At%20this%20point%20delete%20the%20Domains%20and%20add%20them%20in%20the%20new%20Tenant.%20Then%20install%26nbsp%3B%20again%20the%20ADconnect%20and%20connect%20it%20to%20the%20new%20Tenant.%20After%20that%20disinstall%20and%20install%20again%20the%20HCW%20to%20connect%20the%20Exchange%202016%20to%20the%20new%20Tenant.%20Can%20something%20go%20wrong%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1616980%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Tenant%20moving%20to%20another%20Tenant%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1616980%22%20slang%3D%22en-US%22%3E%3CP%3EHey%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F764291%22%20target%3D%22_blank%22%3E%40Ornelam%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20should%20be%20good%2C%20first%20off%20begin%20with%20patching%20your%20exchange%20server%20to%20latest%20CU%20to%20be%20able%20to%20leverage%20full%20power%20of%20hcw%20with%20auotomatic%20configuration%20of%20oauth%2C%20you%20will%20have%20to%20watch%20out%20for%20a%20few%20things%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EIn%20cloud%20user%20migration%3C%2FSTRONG%3E%3A%20To%20offboard%20in%20cloud%20users%2C%20there%20has%20to%20a%20corresponding%20remote%20mailbox%20on-premises%26nbsp%3Bwith%20the%20same%20exchange%20guid%20as%20office%20365%20mailbox.%20So%20first%20you%20will%20have%20to%20get%20a%20remote%20mailbox%20provisioned%20on-premises%20with%20same%20exchange%20guid%20and%20make%20sure%20the%20objects%20sync.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fenable-remotemailbox%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EEnable-Remotemailbox%26nbsp%3B%3C%2FA%3Eif%20user%20already%20exists%20on-premises.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fpowershell%2Fmodule%2Fexchange%2Fnew-remotemailbox%3Fview%3Dexchange-ps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ENew-Remotemailbox%3C%2FA%3E%20to%20provision%20a%20new%20AD%20mail%20user%20for%20the%20mailbox%20in%20office%20365.%3C%2FP%3E%3CP%3EOnce%20done%20with%20above%20you%20will%20also%20have%20to%20stamp%20the%20exchange%20GUID%20from%20office%20365%20mailbox%20against%20the%20mail%20user%20on-premises%20to%20offboard%20successfully%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-in%2Fhelp%2F2956029%2Fmigrationpermanentexception-cannot-find-a-recipient-that-has-mailbox-g%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-in%2Fhelp%2F2956029%2Fmigrationpermanentexception-cannot-find-a-recipient-that-has-mailbox-g%3C%2FA%3E%3C%2FP%3E%3CP%3EOnce%20offboarding%20is%20complete%20for%20all%20the%20users%2C%20you%20can%20disable%20dirsync%2C%20optionally%20clear%20out%20old%20target%20address%20(mail.onmicrosoft.com)%2C%20remove%20connectors%20created%20by%20hybrid.%20Disable%20dirsync%2C%20free%20the%20domain%20add%20to%20target%20tenant%20and%20setup%20dirsync%20%2Fhybrid.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hello everyone! My client has a Hybrid environment, with some users that are synced with ADConnect, and others that are just Cloud users. Now all these users have to move to another tenant. How can I do this in the best way possible? I was thinking to migrate first the mailboxes from Exchange Online to Exchange ONPrem 2016, since the Hybrid is configurated. Than disconnect the ADconnect from the old Tenant, the synced users will now become just Cloud users, and can stay in the olt Tenant as Backup. At this point delete the Domains and add them in the new Tenant. Then install  again the ADconnect and connect it to the new Tenant. After that disinstall and install again the HCW to connect the Exchange 2016 to the new Tenant. Can something go wrong?

1 Reply

Hey @Ornelam 

You should be good, first off begin with patching your exchange server to latest CU to be able to leverage full power of hcw with auotomatic configuration of oauth, you will have to watch out for a few things:

 

In cloud user migration: To offboard in cloud users, there has to a corresponding remote mailbox on-premises with the same exchange guid as office 365 mailbox. So first you will have to get a remote mailbox provisioned on-premises with same exchange guid and make sure the objects sync.

Enable-Remotemailbox if user already exists on-premises.

New-Remotemailbox to provision a new AD mail user for the mailbox in office 365.

Once done with above you will also have to stamp the exchange GUID from office 365 mailbox against the mail user on-premises to offboard successfully:

https://support.microsoft.com/en-in/help/2956029/migrationpermanentexception-cannot-find-a-recipient...

Once offboarding is complete for all the users, you can disable dirsync, optionally clear out old target address (mail.onmicrosoft.com), remove connectors created by hybrid. Disable dirsync, free the domain add to target tenant and setup dirsync /hybrid.

 

Thanks