Forum Discussion
Migrating from AD hybrid to new AD because of company adquisition.
I have this scenario where a company have an on-premises domain syncing to Azure AD, and using standard on-premises services like file servers, and also Microsoft 365, all type of Azure services, Intune, etc. Let's call it company.com.
The company has a parent company that exist only in paper, parent.com
The management team decided to migrate everything under company.com to the new domain parent.com. That would affect everything, users, files servers on premise, Intune, the old domain, the mailboxes, Onedrive. etc.
What is the best path to manage that migration?
- Are you intending to migrate to a brand new Active Directory Forest, or is this closer to a rebranding where you are changing the domain used from company.com to parent.com?
- Technically it is more like a rebranding, but not sure if that can be done. The old domain company.com, needs to disappear and become parent.com. But everywhere. On premise, on Azure. It will affects everything.
No sure what is the best patch considering the sheer amount of moving parts. In an old world migrating to a new on-premise domain should do it. But because of the deep integration with Azure and Office 365 tenant, the problem is way more complex.- Ok, cool. Unless I've misunderstood, I would recommend trying to go down the route of adding partent.com as an additional suffix to the existing AD, and then adding parent.com to your AzureAD Connect/AzureAD.
While the AD domain internally would still be company.local or company.com, adding parent.com as an additional suffix means that you can change users UPN from email address removed for privacy reasons to email address removed for privacy reasons. so for sign into the domain and Azure they would use the new suffix (as well as for email etc).
While there would be some reconiguration, it would certainly be less disription than ripping out AD/Azure and starting over again.
If there is a real need to rename the On Prem AD domain, there is a process to do this, although I've done done this myself and is quite involved.
https://www.rebeladmin.com/2015/05/step-by-step-guide-to-rename-active-directory-domain-name/
- So the parent entity doesn't have any AD or Azure AD insfrastructure or presence. This is simply rebranding with new email adresses?
HidMov pretty much has it right. You can add the new parent.com has a allowed upn suffix in AD, verify it in Azure Ad starting changing users primary email address and UPN's.
I would do some reading on the impact of doing this to SharepointOnline and Ondrive especially when users have shared content out their OneDrive and someone else is hitting that share, If I recall correctly OneDrive URLs get changed and so does Sharepoint
