Can't verify domain after adding TXT record on AWS Route 53

Question

Can't verify domain after adding TXT record on AWS Route 53

Joao Alpoim 20

I'm trying to verify a custom domain in Microsoft Entra ID (Azure AD). I added the required TXT record to AWS Route 53 for the domain, using the exact values provided in the Azure portal.

Record:

Type: TXT
Name: @
Value: MS=ms######## (from Azure)

After creating the record, I waited more than 72 hours, and it still fails to verify in the Azure portal. I've confirmed the record is visible via external DNS tools like nslookup and dig. TTL is set to default (300 seconds).

I've verified that:

The domain is registered and active.
The name servers are pointing to Route 53.
The TXT record matches exactly.

Despite all that, Azure won't verify the domain.

Any help would be appreciated.

Raja Pothuraju 43,505 Reputation points Microsoft External Staff Moderator

2025-05-12T19:12:21.29+00:00
Hello @Joao Alpoim,

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 AWS Route 53.

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

Common verification issues

First, let's check if your custom domain has already been verified in another Entra directory. You can do this by entering your domain name in the following URL to retrieve the tenant ID where it is verified:

https://www.whatismytenantid.com/

Once you have the tenant ID, verify whether it belongs to your tenant. If the tenant ID is different and you do not own that directory, the only option is to contact the Data Protection team via a support ticket to request the removal of the domain verification from the existing Entra ID tenant. After the removal, you should be able to verify the domain in your tenant without any issues.

To involve Data Protection team via a support ticket, I need a few details from you. As this information contains Personally Identifiable Information (PII), please share the following details via private message:

Custom domain Name:

Your tenant ID:

Contact Email address:

Contact Phone Number:

Country

TimeZone

Once you send me these details via private message, we can connect offline to discuss further and assist you in resolving this issue.

Answer accepted by question author

0 additional answers

Your answer

Raja Pothuraju 43,505 Reputation points Microsoft External Staff Moderator

2025-05-12T19:12:21.29+00:00

Hello @Joao Alpoim,

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 AWS Route 53.

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

Common verification issues

First, let's check if your custom domain has already been verified in another Entra directory. You can do this by entering your domain name in the following URL to retrieve the tenant ID where it is verified:

https://www.whatismytenantid.com/

Once you have the tenant ID, verify whether it belongs to your tenant. If the tenant ID is different and you do not own that directory, the only option is to contact the Data Protection team via a support ticket to request the removal of the domain verification from the existing Entra ID tenant. After the removal, you should be able to verify the domain in your tenant without any issues.

To involve Data Protection team via a support ticket, I need a few details from you. As this information contains Personally Identifiable Information (PII), please share the following details via private message:

Custom domain Name:

Your tenant ID:

Contact Email address:

Contact Phone Number:

Country

TimeZone

Once you send me these details via private message, we can connect offline to discuss further and assist you in resolving this issue.

Answer 1

Hello @Joao Alpoim,

Thank you for sharing the details over private message.

The issue relates to an unable to verify custom domain name as it is verified in different directory in Azure.

To resolve this, we have engaged our Data Protection team through a support ticket. They will reach out to you via email or phone to help restore access to the tenant and assist in resolving the issue.

Once the issue has been resolved by our support team, please feel free to revisit and kindly click "Accept Answer," as this will be helpful to other community members facing similar issues.

Share via

Can't verify domain after adding TXT record on AWS Route 53

0 additional answers

Your answer