'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Move an onmicrosoft.com Domain Between Microsoft 365 Tenants
Question details
The user needs to move an onmicrosoft.com domain from one Microsoft 365 tenant to another while managing Azure AD Connect synchronization and avoiding disruption.
- Product
- Microsoft 365 / Azure Active Directory
- Device & OS
- not provided
- Scenario
- Moving a custom or default domain across Microsoft 365 environments involving active directory synchronization.
- Observed behavior
- The domain is tied to multiple references (proxyAddresses, targetAddress, etc.) in the source tenant and must be systematically untied before registration to the destination tenant.
Ensure you have global administrator access to both the source and destination Microsoft 365 tenants, and that Azure AD Connect is accessible for forcing synchronizations during the cutover.
Migrate the Domain Using Azure AD Connect
Follow this systematic approach to safely remove the domain from the source tenant and attach it to the destination tenant.
Because an onmicrosoft.com domain can be associated with only one tenant at a time, it is crucial to inventory and remove every reference from the source tenant before attempting to add it to the destination tenant. Azure AD Connect synchronization must be carefully coordinated across both organizations.
Check Active Directory, Exchange Online, Microsoft Entra ID, applications, groups, contacts, and mail flow rules for any usage of the target domain in the source tenant.
Remove the domain from user proxies, targetAddress values, and group aliases. Allow Azure AD Connect synchronization to fully process these changes in the source tenant.
Confirm no resources still use the domain in the source tenant, then officially remove the domain from the source Microsoft 365 admin center under Settings > Domains.
Log into the destination tenant's Microsoft 365 admin center, add the domain, and verify ownership using DNS records.
Assign the domain to the synchronized users and groups in the new environment, then validate mail flow, sign-in names, and Azure AD Connect routing.
Enhance Your Productivity with WPS Office During Migrations
While navigating complex Microsoft 365 tenant migrations, your team still needs reliable tools to handle daily documents. WPS Office provides a free, lightweight, and highly compatible Office suite that works seamlessly without being tied to complex Azure AD environments.
- 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
- 2. Install WPS Office: Run the setup file and follow the simple on-screen instructions to complete the installation.
- 3. Open Your Office Documents: Launch WPS Office and directly open any existing Word, Excel, or PowerPoint files without losing formatting.
Frequently Asked Questions
Can a domain be active in two Microsoft 365 tenants simultaneously?
No, a single domain can only be registered and active in one Microsoft 365 tenant at a time. It must be completely removed from the source before adding to the destination.
Why is the domain removal failing in the source tenant?
Removal usually fails if the domain is still referenced by a user, group, application, or proxyAddress. You must identify and eliminate all dependencies first.
Does Azure AD Connect automatically move the domain for me?
No. Azure AD Connect only synchronizes on-premise directories to a specific tenant. You must manually configure the domain across both tenants and update the sync scopes accordingly.
How long does it take for Microsoft to release a removed domain?
While typically immediate, domain release can sometimes take up to 24 hours depending on backend replication and lingering hidden object references.
