Custom domain <pii removed> locked in inaccessible tenant - cannot verify in Entra ID

Question

Custom domain <pii removed> locked in inaccessible tenant - cannot verify in Entra ID

Abdul Wahab Qazi 0

Hi,

I am trying to add a custom domain <PII REMOVED> to

my Microsoft Entra ID tenant but verification keeps failing.

After investigation I found the domain is already registered

in another tenant:

Tenant ID: <PII REMOVED>

I confirmed this by running:

Invoke-RestMethod -Uri "https://login.microsoftonline.com/

choosycloud.com/.well-known/openid-configuration"

This old tenant belongs to a previous Azure account which

is now blocked and inaccessible to me.

I am the verified owner of <PII REMOVED> on Namecheap

(domain registrar). The TXT record MS=ms27855831 is live

and fully propagated globally (verified on dnschecker.org).

Questions:

How can I release<PII REMOVED> from tenant <PII REMOVED>
Is there a self-service way to reclaim a domain from an old inaccessible tenant?

Thank you

Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-05-12T06:15:01.94+00:00

Abdul Wahab Qazi

Thank you for reaching out to Microsoft Q&A.

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: https://learn.microsoft.com/en-us/entra/fundamentals/add-custom-domain?context=azure%2Factive-directory%2Fusers-groups-roles%2Fcontext%2Fugr-context#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: https://support.microsoft.com/en-us/topic/customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

If it doesn't work for you—let us know, we are happy to assist you further!
Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-05-14T06:49:47.4+00:00

Abdul Wahab Qazi

Following up to check if the resolution provided was helpful. Let us know if you need any further assistance.

1 answer

Your answer

Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-05-12T06:15:01.94+00:00

Abdul Wahab Qazi

Thank you for reaching out to Microsoft Q&A.

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: https://learn.microsoft.com/en-us/entra/fundamentals/add-custom-domain?context=azure%2Factive-directory%2Fusers-groups-roles%2Fcontext%2Fugr-context#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: https://support.microsoft.com/en-us/topic/customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2

If it doesn't work for you—let us know, we are happy to assist you further!
Shubham Sharma 17,930 Reputation points Microsoft External Staff Moderator

2026-05-14T06:49:47.4+00:00

Abdul Wahab Qazi

Following up to check if the resolution provided was helpful. Let us know if you need any further assistance.

Answer 1

Releasing choosycloud.com from tenant 54df3c1e-4150-422f-a1ab-480be335ea3d

Microsoft Entra does not allow the same custom domain to be verified in more than one tenant at a time. As long as choosycloud.com is verified in tenant 54df3c1e-4150-422f-a1ab-480be335ea3d, verification in the new tenant will fail.

The only supported way to release the domain is to have it deleted from the old tenant. Because that tenant is blocked/inaccessible, this cannot be done self‑service and requires Microsoft support intervention:

Confirm that choosycloud.com is still present as a custom domain in the old tenant (which you effectively did by discovering the tenant ID and OpenID configuration).
Open a support case with Microsoft (Azure/Microsoft Entra support) and provide:
- The domain name choosycloud.com.
- Proof of ownership from Namecheap (registrar account screenshots, WHOIS, etc.).
- The old tenant ID 54df3c1e-4150-422f-a1ab-480be335ea3d and the fact that it is blocked/inactive.
Request that support either:
- Reactivate the old tenant long enough for the domain to be removed, or
- Perform a domain removal/domain takeover operation on the backend, based on proof of domain ownership.

Microsoft’s platform enforces that a domain can be verified in only one directory at a time:

“A domain name can only be verified in one directory. If your domain name is currently verified in another directory, it can't also be verified in the new directory. To fix this duplication problem, you must delete the domain name from the old directory.”

Until support removes the domain from the old tenant, verification in the new tenant will not succeed.

Self‑service reclaim options

There is no fully self‑service way to reclaim a custom domain from an old tenant that is blocked and cannot be accessed.

The normal self‑service options are:

Sign in to the old tenant as a Global/Domain Name Administrator and delete the custom domain.
If the tenant is only in an “inactive” state and still within the reactivation window, request tenant reactivation and then remove the domain.

However, once the tenant is blocked and inaccessible to the admin, and especially if it is past the supported reactivation window, only Microsoft support can intervene. The domain cannot be re‑verified in another tenant until it is removed from the old one.

After Microsoft removes the domain from the old tenant and you add it to the new tenant:

Add choosycloud.com as a custom domain in the new tenant.
Create the TXT (or MX) record provided by Entra at Namecheap with TTL 3600 seconds.
Wait for DNS propagation and then select Verify in Entra ID → Domain names.

If planning to use subdomains (for example, for custom URL domains), each subdomain that will be used for sign‑in must also be verified individually.

References: