'%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 Transfer a Microsoft 365 Domain When the Former Tenant Won't Release It
Question details
A user needs to migrate their custom domain to a new Microsoft 365 tenant, but the domain is currently locked to a former tenant and the previous administrator will not release it.
- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Attempting to add an existing custom domain to a new Microsoft 365 tenant without the cooperation of the previous tenant's administrator.
- Observed behavior
- The Microsoft 365 admin center blocks adding the domain, stating it is already associated with another tenant, despite the user having full ownership of the DNS records.
Ensure you have full administrative access to your domain's DNS hosting provider, as you will need to prove domain ownership directly to Microsoft Support.
Request an Internal Domain Release via Microsoft 365 Business Support
Use your DNS ownership to prove to Microsoft that you own the domain, allowing them to force-remove it from the uncooperative tenant so you can add it to your new one.
DNS ownership alone does not automatically sever the connection between a domain and an existing Microsoft 365 tenant. Because Microsoft requires the domain to be removed from the old tenant before it can be added to a new one, you must engage Microsoft Support to perform an administrative override.
Sign in to the Microsoft 365 admin center for your new tenant. Navigate to Settings > Domains and select 'Add domain'. Follow the prompts until you receive the error stating the domain is associated with another tenant.
Click the 'Help & support' widget in the bottom-right corner of the Microsoft 365 admin center. Describe the issue, stating that the former tenant refuses to release the domain, and request a tenant-to-tenant domain release.
When contacted by the Microsoft support engineer, they will provide you with a specific TXT record. Log into your domain registrar's DNS settings and add this TXT record to prove you control the domain.
Microsoft will investigate and typically give the former tenant a brief notice. Once authorized, Microsoft will forcefully strip the domain from the old tenant, allowing you to finalize the 'Add domain' process in your new admin center.
Switch to WPS Office for a Hassle-Free Productivity Experience
While resolving Microsoft 365 tenant migrations and domain disputes can be complex and time-consuming, your everyday document editing shouldn't be. WPS Office provides a lightweight, highly compatible, and free alternative to Microsoft Office, ensuring your team stays productive without the administrative overhead.
Frequently Asked Questions
How long does it take for Microsoft to forcefully release a domain?
Once you provide proof of DNS ownership, the investigation and forced removal process usually takes a few days. The exact timeframe depends on Microsoft Support's current queue and the mandatory waiting period given to the former tenant to respond.
Can I just change my DNS MX records to bypass the old tenant?
No. While you can point mail flow to a different server, you cannot add the custom domain to the new Microsoft 365 tenant's ecosystem until the domain object is explicitly removed from the old tenant's Azure AD directory.
What happens to the email data on the former tenant when the domain is removed?
Removing the domain from the former tenant will change the user principal names (UPNs) and email addresses of the users on that tenant to the default .onmicrosoft.com fallback domain. It does not instantly delete their mailbox data, but you will need a separate migration strategy to transfer any historical data to your new tenant.
Do I need access to the old Microsoft 365 admin center at all?
If you have administrative access to the old tenant, you can manually remove the domain from Settings > Domains without calling support. If you do not have access, you must rely entirely on Microsoft Support and your DNS registrar control to facilitate the transfer.
