Add AADConnect/DirSync after O365 cutover migration

%3CLINGO-SUB%20id%3D%22lingo-sub-145307%22%20slang%3D%22en-US%22%3EAdd%20AADConnect%2FDirSync%20after%20O365%20cutover%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-145307%22%20slang%3D%22en-US%22%3E%3CP%3ELooking%20at%20doing%20an%20Exchange%202010%20to%20O365%20cutover%20migration%20in%20a%20few%20weeks%20and%20wanted%20to%20make%20sure%20I%20can%20use%20AADConnect%2FDirSync%20AFTER%20the%20migration%20is%20done%2Flicenses%20applied%2Fetc.%20It%20is%20~50%20users%20and%20not%20a%20lot%20of%20mailbox%20items.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20plan%20is%20to%20do%20the%20following%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EConnect%20Office%20365%20to%20Exchange%202010%20server%20(already%20have%20Outlook%20Anywhere%20and%20a%20legit%20cert)%3C%2FLI%3E%0A%3CLI%3EStart%20mailbox%20migration%20batch%3C%2FLI%3E%0A%3CLI%3EGrant%20licenses%20to%20mailboxes%3C%2FLI%3E%0A%3CLI%3ELet%20that%20sit%20for%20a%20couple%20of%20days%20(start%20mid-week)%3C%2FLI%3E%0A%3CLI%3ECut%20over%20DNS%20(Saturday)%3C%2FLI%3E%0A%3CLI%3EFinal%20mailbox%20migration%3C%2FLI%3E%0A%3CLI%3EStop%20mailbox%20batches%3C%2FLI%3E%0A%3CLI%3ESet%20up%20AAD%20Connect%3C%2FLI%3E%0A%3CLI%3EAfter%20a%20week%2C%20remove%20mailboxes%20and%20decommission%20Exchange.%26nbsp%3B%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EDo%20I%20have%20that%20correct%3F%20My%20LAST%20step%20should%20be%20to%20set%20up%20AADConnect%2FDirSync%3F%20If%20so%2C%20anything%20I%20need%20to%20be%20aware%20of%3F%20Just%20make%20sure%20the%20SMTP%20attribute%20in%20AD%20matches%20what%20is%20in%20O365%3F%20Is%20anything%20going%20to%20happen%20after%20I%20remove%20Exchange%3F%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-145307%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMigration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn-Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206466%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20AADConnect%2FDirSync%20after%20O365%20cutover%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206466%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Roger%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20will%20need%20Exchange%20Hybrid%20to%20have%20full%20support%20from%20Microsoft%2C%20and%20depending%20your%20license%20you%20do%20not%20pay%20Exchange%20Server%2C%20you%20can%20view%20and%20request%20the%20key%20here%26nbsp%3B%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fhybridkey%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fhybridkey%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-206121%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20AADConnect%2FDirSync%20after%20O365%20cutover%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-206121%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20currently%20have%20AD%20Sync%20running%20inside%20our%20network%20with%20no%20Exchange%20Server%20locally.%26nbsp%3B%20We%20don't%20have%20any%20problems%20however%20its%20a%20pain%20when%20we%20need%20to%20make%20user%20changes%26nbsp%3B%20as%20we%20need%20to%20use%20the%20attribute%20editor%20in%20AD%2C%20can%20be%20a%20pain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20did%20not%20want%20a%20local%20Exchange%20Server%20as%20the%20end%20goal%20was%20to%20migrate%20to%20365%20removing%20the%20local%20hassle%20of%20managing%20a%20local%20Exchange%20box.%20which%20has%20been%20done.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWithout%20installing%20a%20local%20exchange%20server%26nbsp%3Bis%20there%20anything%20else%20we%20can%20install%20%2F%20do%20to%20help%20managing%20users%20(without%20using%20Attribute%20editor%3F)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-169975%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20AADConnect%2FDirSync%20after%20O365%20cutover%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-169975%22%20slang%3D%22en-US%22%3EI%20am%20attempting%20the%20same%20in%20a%20few%20weeks%20and%20from%20what%20I%20understand%20you%20are%20correct%20in%20the%20case%20of%20a%20cutover%20migration.%20I%20have%20done%20a%20hybrid%20migration%20in%20the%20past%20and%20I%20couldn't%20remove%20my%20on-premises%20Exchange.%20Hence%20I%20will%20be%20doing%20cutovers%20from%20now%20on.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-145599%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20AADConnect%2FDirSync%20after%20O365%20cutover%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-145599%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mark%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20do%20that%2C%20but%20you%20will%20not%20have%20support%20from%20Microsoft%20because%20you%20need%20to%20maintain%20the%20Exchange%2C%20if%20you%20uninstall%20your%20Exchange%20you%20cannot%20have%20AD%20Connect%20fully%20supported.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20read%20more%20here%20%3CA%20href%3D%22https%3A%2F%2Fblogs.msdn.microsoft.com%2Fvilath%2F2015%2F05%2F25%2Foffice-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.msdn.microsoft.com%2Fvilath%2F2015%2F05%2F25%2Foffice-365-and-dirsync-why-should-you-have-at-least-one-exchange-server-on-premises%2F%3C%2FA%3E%20and%20here%20%3CA%20href%3D%22https%3A%2F%2Fjaapwesselius.com%2F2016%2F06%2F14%2Foffice-365-directory-synchronization-without-exchange-server-part-ii%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fjaapwesselius.com%2F2016%2F06%2F14%2Foffice-365-directory-synchronization-without-exchange-server-part-ii%2F%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20will%20need%20to%20install%20a%20new%20Exchange%20Hybrid%20a%20Hybrid%20License%2C%20you%20can%20read%20more%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2939261%2Fhow-to-obtain-an-exchange-hybrid-edition-product-key-for-your-on-premi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2939261%2Fhow-to-obtain-an-exchange-hybrid-edition-product-key-for-your-on-premi%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1533448%22%20slang%3D%22en-US%22%3ERe%3A%20Add%20AADConnect%2FDirSync%20after%20O365%20cutover%20migration%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1533448%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BHey%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F61336%22%20target%3D%22_blank%22%3E%40Mark%20Valpreda%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20was%20finally%20you%20did%20the%20setup%3F%20i%C2%B4m%20about%20to%20do%20the%20same%20cutover%20migrtion%2C%20and%20i%20have%20the%20same%20doubt%20about%20when%20deploy%20AAD%20Connect%20and%20if%20going%20to%20have%20problems%20with%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20you%20can%20answer%20my%20concern%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Looking at doing an Exchange 2010 to O365 cutover migration in a few weeks and wanted to make sure I can use AADConnect/DirSync AFTER the migration is done/licenses applied/etc. It is ~50 users and not a lot of mailbox items.

 

The plan is to do the following:

  • Connect Office 365 to Exchange 2010 server (already have Outlook Anywhere and a legit cert)
  • Start mailbox migration batch
  • Grant licenses to mailboxes
  • Let that sit for a couple of days (start mid-week)
  • Cut over DNS (Saturday)
  • Final mailbox migration
  • Stop mailbox batches
  • Set up AAD Connect
  • After a week, remove mailboxes and decommission Exchange. 

Do I have that correct? My LAST step should be to set up AADConnect/DirSync? If so, anything I need to be aware of? Just make sure the SMTP attribute in AD matches what is in O365? Is anything going to happen after I remove Exchange? 

5 Replies
Highlighted

Hi Mark,

 

You can do that, but you will not have support from Microsoft because you need to maintain the Exchange, if you uninstall your Exchange you cannot have AD Connect fully supported.

 

You can read more here https://blogs.msdn.microsoft.com/vilath/2015/05/25/office-365-and-dirsync-why-should-you-have-at-lea... and here https://jaapwesselius.com/2016/06/14/office-365-directory-synchronization-without-exchange-server-pa...

 

You will need to install a new Exchange Hybrid a Hybrid License, you can read more here https://support.microsoft.com/en-us/help/2939261/how-to-obtain-an-exchange-hybrid-edition-product-ke...

Highlighted
I am attempting the same in a few weeks and from what I understand you are correct in the case of a cutover migration. I have done a hybrid migration in the past and I couldn't remove my on-premises Exchange. Hence I will be doing cutovers from now on.
Highlighted

We currently have AD Sync running inside our network with no Exchange Server locally.  We don't have any problems however its a pain when we need to make user changes  as we need to use the attribute editor in AD, can be a pain.

 

We did not want a local Exchange Server as the end goal was to migrate to 365 removing the local hassle of managing a local Exchange box. which has been done.

 

Without installing a local exchange server is there anything else we can install / do to help managing users (without using Attribute editor?)

Highlighted

Hi Roger,

 

You will need Exchange Hybrid to have full support from Microsoft, and depending your license you do not pay Exchange Server, you can view and request the key here http://aka.ms/hybridkey 

Highlighted

 Hey @Mark Valpreda 

How was finally you did the setup? i´m about to do the same cutover migrtion, and i have the same doubt about when deploy AAD Connect and if going to have problems with that.

 

I hope you can answer my concern