Forum Discussion
Solved
Microsoft 365 Minimal or Cutoff Migration?
Hello, I am currently running an on-premises Server 2016 domain with Active Directory and Exchange 2016 with around 65 users. I am starting to plan for migrating our Exchange server to Microsoft...
- You can re-enable sync after the migration, that's not a problem. Do note that if you plan to decommission Exchange, having AAD Connect in the mix puts you in an unsupported configuration. Every configuration involving dirsync/AAD Connect requires you to keep at least one Exchange box for management purposes.
MSFT recommendation in currently described scenario is to go with hybrid (minimal/express) migration as you won't have any problems related to synchronization and management. If your plan is to get rid of complete on prem-infrastructure, then cut over is the best choice because you got only 65 mailbox users. One of the requirements before starting cut over is to actually stop the directory synchronization (AAD Connect). Once migration is done, you can reconfigure the AADConnect. If you choose to go with Cut Over but still wants to keep the on Prem AD, then you need to manage some properties on daily basis via powershell or AD tools. Most common example is proxy address. As the source of authority is on prem AD, any change in proxy of M365 will be written over once synced.
Thanks for the suggestion, Shane. It does seem like it's entirely possible to administer Exchange Online via powershell or other tools, but in order to stay in compliance with Microsoft I am just going to leave my on-prem Exchange server online for now, which will also make it easier to manage. Even though I would absolutely love to completely decommission Exchange I would rather stay in compliance for now. Hopefully these tools are eventually built directly into Exchange Online at some point so this is no longer a concern.