What Happens When Moving a Domain Between Microsoft 365 Tenants
Question details
The user needs to understand the process, requirements, and potential impacts of moving a verified custom domain from one Microsoft 365 tenant to another.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Planning to migrate a verified custom domain, users, and services between two different Microsoft 365 tenant environments.
- Observed behavior
- A domain cannot exist in two tenants simultaneously. Removing and re-adding domains requires coordinated DNS changes, data backups, and account migrations to prevent severe service disruptions.
Ensure you have full Global Administrator privileges for both the source and target Microsoft 365 tenants, and verify you have administrative access to your domain's DNS hosting provider to modify TXT and MX records.
Step-by-Step Guide to Moving a Domain Between M365 Tenants
Follow this coordinated sequence to safely remove your domain from the source tenant, configure it in the target tenant, and prevent data loss or extended downtime.
Because a custom domain can only be associated with one Microsoft 365 tenant at a time, the migration must be meticulously planned. Moving the domain involves decoupling it from the source users, migrating the data, and updating DNS routing.
Before making any structural changes, perform a comprehensive backup of all mailboxes, OneDrive for Business files, SharePoint sites, and other critical data located in the source tenant.
Set up the target tenant environment. Instead of creating duplicate user accounts, prepare to migrate the existing accounts to ensure a seamless transition of permissions and identities.
Log into the Microsoft 365 Admin Center of the source tenant. Navigate to Settings > Domains, select your custom domain, and choose to remove it. You must remove all dependencies (like user aliases using the domain) before the system allows deletion.
Sign into the target tenant's Admin Center. Go to Settings > Domains and select 'Add domain'. Enter your custom domain and follow the prompts to verify ownership by adding a TXT record at your DNS hosting provider.
Once the domain is successfully verified in the target tenant, update the user accounts to use the newly added custom domain for their User Principal Names and primary email addresses.
Log into your DNS host and update your MX, CNAME, and SRV records to point to the new Microsoft 365 target tenant. This step officially routes incoming emails and services to the new environment.
Looking for a simpler, cost-effective alternative to Microsoft 365?
Managing Microsoft 365 tenants, domain migrations, and administrative overhead can be complex and expensive. If you are looking for a powerful yet simpler office suite for your daily document needs, WPS Office provides a lightweight, comprehensive alternative.
Frequently Asked Questions
Can a verified domain be registered in multiple Microsoft 365 tenants at the same time?
No, Microsoft strictly enforces that a verified custom domain can only exist in one Microsoft 365 tenant at a time. You must completely remove the domain from the source tenant before the target tenant will accept it.
Will I lose my user licenses when I remove a domain from the tenant?
Removing a custom domain does not automatically remove your Microsoft 365 licenses or delete the underlying tenant services. However, users attached to that domain will lose access to email and files until they are reassigned to the default '.onmicrosoft.com' fallback domain or moved to the new tenant.
How long does it take for DNS changes to propagate during a domain move?
DNS record updates (such as TXT for verification and MX for email routing) typically take anywhere from a few minutes to 48 hours to fully propagate globally. During this window, you may experience temporary disruptions in email delivery.
Should I create duplicate users in the target tenant before moving the domain?
No, creating duplicate users is not recommended as it complicates identity management. It is best to migrate the existing user accounts directly and update their email addresses and User Principal Names (UPNs) only after the target tenant is prepared and the domain is verified.
