Stranded Domain in Locked 365 Account

Question

Hi all,

I created a Microsoft 365 Account on the 7th of March and linked my business domain to it.

A few days later, I was unable to sign into the account and I had an email from Microsoft saying 'As requested, your MIcrosoft 365 Business Basic subscription was cancelled.' No other details were provided.

Neither I nor my business partner requested the cancellation so not sure what happened there, however neither of us are able to sign into the account.

When trying to link the business domain to a new 365 account, an error appears stating 'this domain is already connected to a 365 account, please unlink it to use it here.' Which we cannot do.

I've tried reaching out to support but so far haven't got very far. Any ideas on what can be done to get this sorted? This is stopping us from using the domain we wanted for our business and also hindering us from setting up some other bits and pieces for the business launch.

Any advice appreciated.

Thanks,

Matt

Answer 1

Hi @Matt Fowkes,

Thanks for explaining the situation. I can see how disruptive this must be, especially when it’s blocking your business setup.

From what you’ve described, even though the Microsoft 365 subscription was cancelled and the tenant appears to be locked, the custom domain is still attached to the original Microsoft 365 tenant on the backend. Because a domain can only be associated with one tenant at a time, it can’t be added to a new tenant until it’s explicitly released from the old one. Unfortunately, there’s no self‑service way to remove a domain if you can’t sign in as an admin to that original tenant.

If you are able to verify ownership of the custom domain, Microsoft Support may use that validation (usually via DNS records or registrar verification) to either:

• Restore or re-enable access to the original tenant long enough for you to sign in as an admin and remove the domain yourself.
• Manually release the domain from the locked tenant on the backend so it can be added to a new tenant.
• In the event that the original tenant cannot be recovered, Microsoft Support will provide notification along with further guidance.

To help me understand where things stand and how best to advise, could you clarify a couple of things?

• As you mention reaching out to support, have you successfully create a support case?
• If yes, what exactly did you ask the support agent to do (for example, did you explicitly ask them to verify domain ownership or release/detach the domain from a locked tenant)?
• Did they mention restoring access to the original tenant or escalating the case to backend, tenant, or data protection teams?
• If you have a support ticket number, please send it to me via private message so I can take a closer look and help guide next steps if possible. Please reset this page and you'll see a pop-up on top of your thread. You can click on View Messages to check what I've messaged you.     

When speaking with support, it’s important to be very explicit that:

• The original tenant is inaccessible or locked.
• No global admin can currently sign in.
• You can prove ownership of the custom domain if required.
• The end goal is either temporary tenant access to remove the domain or a backend domain release.

Once I know where the support case stands, I can better advise on the next step to get this resolved.

I'm looking forward to your response so we can get this sorted out for you together.

---

If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

The domain is still attached to the original Microsoft 365 tenant, so it cannot be added to a new tenant until it is removed from the old one. A custom domain can exist in only one Microsoft 365 organization at a time.

Based on the documented behavior, the situation matches this case:

• When trying to verify/add the domain in the new tenant, Microsoft 365 reports that the domain is already in use in another Microsoft 365 account/tenant.

The supported resolution paths are:

1. If there is any way to sign in to the original tenant as an admin (for example, via the original onmicrosoft.com admin account), remove the domain there first. The domain must be removed from its current location before it can be added to a new tenant.
2. If sign-in to the original tenant is not possible (for example, the subscription was cancelled and no admin access is available), the only supported option is to work with Microsoft support so they can handle the domain on the backend:
   • Clearly state that the custom domain is already associated with another Microsoft 365 organization/tenant that cannot be accessed.
   • Confirm that ownership of the domain can be proved (for example, by adding DNS records if requested).
   • Ask specifically for help removing or releasing the domain from the old tenant so it can be added to the new one.

If the tenant is locked and there is no other global admin, support typically escalates to the Data Protection or back-end support teams to validate identity and domain ownership and then free the domain. This cannot be done from the portal alone.

Until the domain is removed from the original tenant by an admin or by Microsoft support, it will not be possible to attach it to the new Microsoft 365 account.

---

References:

• Error message when you try to verify a domain in Office 365
• Troubleshoot domain verification issues in Office 365
• An administrator can't add a domain to Microsoft 365, Azure, or Intune
• Find and fix issues after adding your domain or DNS records
• Domain is in another o365 as a tenant - Microsoft Q&A