Domain registered under a managed tenant I don't control – requesting forced domain release

Question

Domain registered under a managed tenant I don't control – requesting forced domain release

Lucas Barros 0

I need to add a custom domain to my Azure/Microsoft Entra tenant, but the domain is currently registered under a different managed tenant that I have no access to and am not an admin of.

My situation:

I am the owner of the domain (I have full control over DNS at the registrar)
The domain is currently verified/registered under another organization's managed Entra tenant
I have no admin access to that other tenant
I need to use this domain under my own managed tenant

What I've already tried:

Attempting to add the domain in my tenant returns an error stating the domain is already in use by another organization
The self-service admin takeover process does not apply, as the other tenant is managed (not an unmanaged/viral tenant)
The PowerShell ForceTakeover option is also not applicable for managed tenants

What I need: A forced domain release from the tenant currently holding it, so I can verify and register it under my own tenant. I am able to prove domain ownership by publishing any required DNS TXT record (MS=xxxxx format) at any time.

Lucas Barros 0 Reputation points

2026-05-22T18:13:26.2833333+00:00

This doesn't solve my problem at all.
I need human assistance telling me how to proceed next.
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-05-22T19:14:39.85+00:00

Hello Lucas Barros,

Based on your description, it seems that you are unable to verify your custom domain in your Entra ID tenant, even after correctly adding the TXT records in your domain provider side.

This issue often occurs when the domain has already been verified in another Entra directory, as explained in the following document: Common verification issues

To resolve this, the recommended approach is to contact the Microsoft Data Protection team. You can reach them by calling Microsoft Customer Service using the phone numbers listed here: Customer service phone numbers - Microsoft Support.

If it doesn't work for you, please don’t worry—let us know, we are happy to assist you further!

1 answer

Your answer

Lucas Barros 0 Reputation points

2026-05-22T18:13:26.2833333+00:00

This doesn't solve my problem at all.
I need human assistance telling me how to proceed next.
Sridevi Machavarapu 33,820 Reputation points Microsoft External Staff Moderator

2026-05-22T19:14:39.85+00:00

Hello Lucas Barros,

Based on your description, it seems that you are unable to verify your custom domain in your Entra ID tenant, even after correctly adding the TXT records in your domain provider side.

This issue often occurs when the domain has already been verified in another Entra directory, as explained in the following document: Common verification issues

To resolve this, the recommended approach is to contact the Microsoft Data Protection team. You can reach them by calling Microsoft Customer Service using the phone numbers listed here: Customer service phone numbers - Microsoft Support.

If it doesn't work for you, please don’t worry—let us know, we are happy to assist you further!

Answer 1

A forced domain release from a managed Microsoft Entra tenant that is not under administrative control is not supported in the provided material.

The available guidance only covers:

Adding a custom domain to a tenant and verifying it via DNS TXT/MX records.
Common verification issues, including the case where a domain is already verified in another directory and must be deleted from that original directory before it can be verified in a new one.
Taking over unmanaged (viral) tenants, such as those created by self-service sign-up (for example, Power BI), via the “take over an unmanaged directory” process.

From the context:

A domain name can only be verified in one directory at a time. If it is already verified in another directory, it cannot be verified in a new directory until it is removed from the original directory.
The documented remediation for duplication is: delete the domain name from the old directory, then verify it in the new directory.
For unmanaged tenants created by self-service sign-up, there is a documented admin takeover process. This does not apply to managed tenants.

Because the current tenant holding the domain is a managed tenant that is not under administrative control, and there is no documented forced-release or forced-takeover mechanism for such tenants in the provided content, no supported technical steps can be given beyond what is already described: the domain must be removed from the original tenant before it can be added and verified in another.

References: