Unable to verify domain name.

David Acklin 0 Reputation points
2026-07-29T13:24:10.1833333+00:00

I placed the txt and mx on my register ant it will still not verify.

any help would be appreciated

Azure DNS
Azure DNS

An Azure service that enables hosting Domain Name System (DNS) domains in Azure.

0 comments No comments

1 answer

Sort by: Most helpful
  1. AI answer

    2026-07-29T13:24:32.7466667+00:00

    Common causes and checks for domain verification failure:

    1. Verify the TXT record value exactly matches the value shown in the portal.
      • For Microsoft 365, the value typically looks like MS=msXXXXXXXX.
      • A common mistake is missing the MS= prefix.
    2. Make sure the DNS record was actually saved at the registrar or DNS host.
      • Some providers require an extra save or publish step before the record is visible publicly.
    3. Allow time for DNS propagation.
      • DNS changes often appear within minutes, but can take a few hours.
      • In some cases, propagation can take longer depending on the registrar.
    4. Check the domain status in the admin portal.
      • In Microsoft 365, go to Setup > Domains and review the Status column.
      • If an issue appears, use Check health to see the reported problem.
    5. Confirm the TXT record is visible publicly.
      • From Windows Command Prompt, run: nslookup -q=TXT yourdomain.com
      • If the expected TXT record does not appear in the results, verification will fail.
    6. If using Microsoft Entra custom domain verification, recheck the DNS entry details.
      • Create the TXT or MX record exactly as shown.
      • Microsoft Entra documentation specifies a TTL of 3600 seconds (60 minutes).
      • If incorrect or duplicate information was entered, it may be necessary to wait for the TTL to expire before retrying.
    7. If the domain is already registered in another tenant, verification can fail even when DNS looks correct.
      • This is a common cause when TXT and MX records are correct but validation still does not complete.
    8. If this is a hybrid Exchange deployment and the domain is being added in Microsoft 365, check whether the domain is already used in the on-premises Exchange federation trust ApplicationUri.
      • In Exchange Management Shell, run Get-FederationTrust and review the ApplicationUri value.
      • If it matches the domain being verified, that can cause the verification error.

    If the goal is Microsoft 365 domain verification, the most direct path is:

    • Go to Settings > Domains.
    • Select the domain.
    • Select Continue setup.
    • Copy the exact TXT value shown.
    • Add that TXT record at the registrar.
    • Wait for propagation.
    • Return and select Verify.
    • After successful verification, remove the temporary TXT or MX verification record if no longer needed.

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

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