Data Protection team required: release a domain from an inaccessible, unused tenant

Question

Data Protection team required: release a domain from an inaccessible, unused tenant

Rachel Kidwell 0

I am requesting escalation to the Data Protection team to release a domain from an inaccessible tenant.

Summary: My organisation owns the domain. This domain is verified in a Microsoft Entra / Microsoft 365 tenant that was originally created by a former CTO who has since left the company. That tenant is unused and empty (no active mail, subscriptions, or resources that we rely on, our email runs on a separate provider). We no longer have any working administrator account for it, no other person in the organisation can sign in, and self-service password reset is not available on the former CTO's account (it was never registered for SSPR). We do not need to recover the tenant, we simply need the domain released so we can use it in a tenant we control.

Please release the domain from the old, inaccessible tenant so that it can be verified and managed in a tenant we control. We do not require any data or access from the old tenant, releasing the domain is sufficient.

0 comments

2 answers

Your answer

Answer 1

Good day @Rachel Kidwell,

Thank you for taking the time to explain your situation so clearly.

From what you've described, I just want to make sure I've understood correctly. You already have a Microsoft 365 tenant that you can access, and your goal is to have the domain removed from the old, inaccessible tenant so that it can be verified and used in the new tenant you now control, is that correct?

If that's the case, then based on similar situations I've seen, the best next step would be to open a support request directly with Microsoft and explain that you need assistance releasing a domain from an inaccessible tenant: Get support - Microsoft 365 admin | Microsoft Learn

User's image

Tips: You can switch off the Support Assistant as shown in the screenshot, then type a few short characters into the search box and select Get Help. After that, wait for the Contact Support button to appear and click it. At the final step, be sure to clearly describe your request in the description fields so the support engineers can quickly understand your issue and assist you more effectively.

Once the support ticket has been submitted, it will be assigned to a Microsoft technical support engineer. They may ask you to provide information that helps verify ownership of the domain and confirm the circumstances surrounding the old tenant. After reviewing the details, they can arrange a remote support session if needed, and work with you through the appropriate validation and recovery processes required to address this request.

Just to set expectations, this is a user-to-user support forum and I'm not part of the Microsoft Data Protection team or any internal Microsoft support organization. I also don't have the tools or permissions needed to make backend changes or submit an escalation on your behalf. However, I hope this answer helps point you toward the right team that can review your request and assist further.

If your situation is a little different from what I've understood, or if you run into any issues along the way, please feel free to reply under this post with an update. I'll be more than happy to continue helping and share any guidance I can.

Thank you again for taking the time to post your question. I wish you all the best with the process, and I hope you're able to get the domain successfully released and moved to your current tenant as smoothly as possible

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.

Rachel Kidwell 0 Reputation points

2026-07-03T09:29:19.81+00:00

Thank you for your suggestion. I am unable to sign in to the Microsoft 365 admin centre due to getting this error message: "You can't sign in here with a personal account. Use your work or school account instead."
This is my work email account that is the admin account on the new tenant. Do you have any suggestions to assist here?
Rachel Kidwell 0 Reputation points

2026-07-03T09:30:41.96+00:00

Thank you for your suggestion. I am unable to sign in to the Microsoft 365 admin centre due to getting this error message: "You can't sign in here with a personal account. Use your work or school account instead."
This is my work email account that is the admin account on the new tenant. Do you have any suggestions to assist here?
Rin-L 22,270 Reputation points Microsoft External Staff Moderator

2026-07-03T10:53:11.54+00:00

Hi @Rachel Kidwell,

Thank you for the update.

Based on your original post, I noticed that you mentioned you already have a new tenant that you can control. To help narrow down the cause of this sign-in issue, could you let me know which Microsoft 365 subscription or license was purchased for the new tenant?

Also, have you successfully signed in to this tenant before, or are you encountering this error from your first sign-in attempt?

Another thing worth checking is the account you're using to sign in. In many cases, the initial Global Administrator account created with a Microsoft 365 tenant uses the .onmicrosoft.com domain. Are you signing in to the Microsoft 365 Admin Center using that .onmicrosoft.com administrator account, or are you using a different account instead?

If possible, could you send me the full email address of the administrator account via private message so I can take a closer look at the sign-in scenario and see whether anything stands out?

To access private messages, please click the banner shown in the image below:

I look forward to your reply and will be happy to continue assisting from there.

Answer 2

Vincent Choy 10,975 Volunteer Moderator

Since you have a current working tenant, you will have to raise a support ticket and explain the situation to the support team and get them to raise a ticket to the data protection team, as per what Rin-L suggested, and let the data protection team validate ownership of that tenant.

0 comments