Azure Domain - Unable to verify custom domain though I have added TXT and MX record in my godaddy dns settings

Alok Prakash Adhao 20 Reputation points
2024-12-10T17:27:29.2+00:00

Hello,

I have a domain casacloud.com which I want to add to my custom domain.

As I added the custom domain. I got TXT and MX record which I have added to my Godaddy domain DNS settings.

I have verified from DNS checker and nslookup, I see that the TXT records are propagated.

Its been more that 72 hours still I am unable to verify my domain

User's image

Not sure what is the issue? Can you please help.

I have another domain in godaddy.. it got verified in minutes. but this one is not getting verified.

I did tried recreating the domain and adding the new TXT and MX records multiple times now still same result.

Thank you so much for your help.

Microsoft Security Microsoft Entra Microsoft Entra ID
{count} votes

Accepted answer
  1. FrankEscarosBuechsel-MSFT 900 Reputation points Microsoft Employee Moderator
    2024-12-11T11:39:34.59+00:00

    Hi @Alok Prakash Adhao • Thank you for reaching out.

    It looks like you a trying to register a custom domain with setting a TXT record in the public facing DNS. From what I can see when trying to resolve the DNS settings look correctly set.

    A very common cause for this happening is that the custom domain is already registered in a different tenant, a domain can only registered to exactly 1 tenant and not in multiple tenants.

    You can use the OIDC endpoint to test for your particular domain for this, I have already filled in the domain you are looking for: https://login.microsoftonline.com/casacloud.com/.well-known/openid-configuration

    If you load that page you will see it returns data, which to me means you either were already able to resolve the issue in which case it would be great if you could share feedback on how you resolved the problem.

    If you are still facing the problem, then the page loading data tells you the root cause, your custom domain is already registered in a different tenant which is why the validation is failing, since this can only be by someone who has access to the DNS server it is most likely someone in your organization, the token URL includes the tenant ID which may be helpful for further investigation internally to see in which tenant the domain name is utilized and if it can be freed from that tenant for your use or if a child domain should be used in your case.

    Should this not lead to resolution then Marti gave you the correct steps indeed to approach your Microsoft Support for further details if necessary.


    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Alok Prakash Adhao 20 Reputation points
    2024-12-14T08:15:31.4566667+00:00

    Hello,

    My issue is resolved after I have raised a support Ticket to Microsoft, Team helped me to point to which tenant the domain was already registered and guided me to remove it from that.

    Thank you so much for your help @FrankEscarosBuechsel-MSFT @Marti Peig

    Best Regards.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.