Multi Forest in trust - New Hybrid Exchange Setup - Only one Exchange Server

%3CLINGO-SUB%20id%3D%22lingo-sub-207870%22%20slang%3D%22en-US%22%3EMulti%20Forest%20in%20trust%20-%20New%20Hybrid%20Exchange%20Setup%20-%20Only%20one%20Exchange%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207870%22%20slang%3D%22en-US%22%3E%3CP%3ETwo%20seperate%20AD%20domains%20(contoso.local%2C%20fabrikam.com)%20which%20are%20in%20a%20forest%20trust%20on%20the%20same%20LAN%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Econtoso.local%20AD%20domain%20has%20an%20exchange%20server%20setup%20with%20contoso.com%20to%20receive%20emails%20-%20the%20plan%20is%20to%20setup%20Hybrid%20Exchange%20on%20this%20domain%20to%20migrate%20mailboxes%20to%20365%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Efabrikam.com%20AD%20domain%20has%20Azure%20AD%20Connect%20setup%20and%20syncing%20all%20users%20to%20a%20365%20tenancy%20already.%20365%20is%20receiving%20on%20fabrikam.com%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAim%20is%20to%20migrate%20Contoso.local%20mailboxes%20into%20the%20SAME%20365%20tenancy%20as%20fabrikam.com%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20like%20to%20know%20if%20it%20is%20possible%20to%20add%20contoso.local%20into%20the%20Azure%20AD%20Connect%20so%20all%20users%20sync%20up%20to%20the%20365%20tenancy%20-%20and%20then%26nbsp%3Bsetup%20Exchange%20Hybrid%20on%20contoso.local%20to%20begin%20mailbox%20migrations%20to%20365.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEnd%20goal%20is%20to%20get%20rid%20of%20the%20contoso.local%20AD%20domain%20but%20keep%20receiving%20contoso.com%20emails%26nbsp%3Binto%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20not%20sure%20if%20the%20Exchange%20Hybrid%20environment%20will%20need%20to%20stay%20in%20that%20case%3F%20And%20what%20will%20happen%20if%20the%20contoso.local%20domain%20is%26nbsp%3Bremoved%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-207870%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-207954%22%20slang%3D%22en-US%22%3ERe%3A%20Multi%20Forest%20in%20trust%20-%20New%20Hybrid%20Exchange%20Setup%20-%20Only%20one%20Exchange%20Server%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-207954%22%20slang%3D%22en-US%22%3E%3CP%3EAzure%20AD%20Connect%20can%20certainly%20handle%20a%20multi-forest%20sync%20scenario%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fconnect%2Factive-directory-aadconnect-topologies%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Factive-directory%2Fconnect%2Factive-directory-aadconnect-topologies%3C%2FA%3E.%3C%2FP%3E%3CP%3EDoes%20Fabrikam%20have%20an%20Exchange%20hybrid%20in%20place%20already%3F%20If%20so%2C%20you'll%20need%20to%20be%20careful%20about%20setting%20up%20a%20second%20hybrid%20(for%20Contoso)%20to%20the%20same%20Office%20365%20tenant.%20Certainly%20possible%20though%20(%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj873754%2528v%3Dexchg.150%2529.aspx%3Ff%3D255%26amp%3BMSPPError%3D-2147217396%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fjj873754%2528v%3Dexchg.150%2529.aspx%3C%2FA%3E).%3C%2FP%3E%3CP%3ELastly%2C%20if%20your%20goal%20is%20to%20remove%20the%20Contoso%20AD%20entirely%2C%20you'll%20need%20to%20either%20(A)%20migrate%20the%20Contoso%20AD%20users%20into%20the%20Fabrikam%20AD%20forest%20and%20then%20perform%20a%20%22hard%20match%22%20with%20Azure%20AD%20Connect%2C%20or%20(B)%20convert%20the%20Fabrikam%20users%20to%20cloud%20only%20in%20Office%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20be%20honest%2C%20this%20is%20not%20going%20to%20be%20simple.%20I%20would%20highly%20recommend%20reaching%20out%20to%20Microsoft%2C%20a%20partner%2C%20or%20a%20migration%20vendor%20for%20assistance%20or%20guidance.%20Best%20of%20luck!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Two seperate AD domains (contoso.local, fabrikam.com) which are in a forest trust on the same LAN

 

contoso.local AD domain has an exchange server setup with contoso.com to receive emails - the plan is to setup Hybrid Exchange on this domain to migrate mailboxes to 365

 

fabrikam.com AD domain has Azure AD Connect setup and syncing all users to a 365 tenancy already. 365 is receiving on fabrikam.com

 

Aim is to migrate Contoso.local mailboxes into the SAME 365 tenancy as fabrikam.com

 

I would like to know if it is possible to add contoso.local into the Azure AD Connect so all users sync up to the 365 tenancy - and then setup Exchange Hybrid on contoso.local to begin mailbox migrations to 365. 

 

End goal is to get rid of the contoso.local AD domain but keep receiving contoso.com emails into 365.

 

I am not sure if the Exchange Hybrid environment will need to stay in that case? And what will happen if the contoso.local domain is removed?

 

1 Reply
Highlighted

Azure AD Connect can certainly handle a multi-forest sync scenario: https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-topologi....

Does Fabrikam have an Exchange hybrid in place already? If so, you'll need to be careful about setting up a second hybrid (for Contoso) to the same Office 365 tenant. Certainly possible though (https://technet.microsoft.com/en-us/library/jj873754%28v=exchg.150%29.aspx).

Lastly, if your goal is to remove the Contoso AD entirely, you'll need to either (A) migrate the Contoso AD users into the Fabrikam AD forest and then perform a "hard match" with Azure AD Connect, or (B) convert the Fabrikam users to cloud only in Office 365.

 

To be honest, this is not going to be simple. I would highly recommend reaching out to Microsoft, a partner, or a migration vendor for assistance or guidance. Best of luck!