Unable to Verify Custom Domain Name

Kevin Foster 1 Reputation point

Hello -

We are trying to add our custom domain name into AAD so we can begin to use Single Sign-On with AD Connect. The verification process will not complete. The required TXT records are in place. I think this is because our domain is a subdomain - we do not own or have access to the parent domain (government agency) and the parent domain does appear to already be registered within Azure. How are we able to get this process to complete?

Error is "Failed to verify domain name"

We have a basic subscription so I am unable to enter a support case for this issue.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,827 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Carlos Solís Salazar 16,946 Reputation points MVP

    Hi @Kevin Foster

    Thank you for asking this question on the **Microsoft Q&A Platform. **

    Unfortunately, you can add a subdomain.

    If you want to add a subdomain name such as ‘europe.contoso.com’ to your organization, you should first add and verify the root domain, such as contoso.com.

    Source: https://learn.microsoft.com/en-us/azure/active-directory/enterprise-users/domains-manage

    Hope this helps,
    Carlos Solís Salazar


    179759-accept.png and 179670-upvote.png if any of the above helped, this threat can help others in the community looking for remediation for similar issues.

    NOTE: To answer you as quickly as possible, please mention me in your reply.

    1 person found this answer helpful.

  2. Tommy 1 Reputation point

    I had the same, or a similar problem.

    I created the MX and TXT records as directed, but the domain kept failing to verify.

    The issue was I still had the domain verified in my old Azure AD org. I deleted it, updated the TXT and MX records, and it worked. Either it just took an hour to detect the new DNS records, or the domain being claimed elsewhere in Azure AD was borking it. Good luck.

    0 comments No comments