How to Fix Microsoft 365 Domain Verification Failure with Microsoft Nameservers
Question details
The user is unable to verify their custom domain in Microsoft 365 because the setup wizard fails to detect external DNS nameservers for TXT or MX verification.

- Product
- Microsoft 365
- Device & OS
- not provided
- Scenario
- Verifying a custom domain during the Microsoft 365 setup or administration process.
- Observed behavior
- Domain verification fails as the system cannot detect external DNS records for the domain when Microsoft 365 nameservers are currently in use.
Ensure you have global administrator or domain administrator privileges in the Microsoft 365 admin center before attempting to modify DNS records.
Manage DNS Records Directly in Microsoft 365 Admin Center
When Microsoft 365 nameservers are authoritative for your domain, you must add and manage your TXT and MX records within the Microsoft 365 admin portal instead of your domain registrar.
If you previously switched your domain's nameservers to point to Microsoft, any DNS record changes made at your domain host (like GoDaddy or Namecheap) will not take effect. Microsoft 365 now acts as your DNS host.
Navigate to the Microsoft 365 admin center and sign in using your administrator credentials.
In the left-hand navigation menu, select Settings, and then click on Domains.
Click on the specific domain you are trying to verify to open its properties panel.
Navigate to the DNS records tab. Here, you can view, add, or manage your current TXT, MX, and CNAME records.
Ensure the required TXT or MX verification records are correctly added. Wait for DNS propagation, which can take a few hours, and attempt the verification process again.

Open a Support Request with Microsoft
If your DNS records are correctly configured in the admin center but verification still fails, contact Microsoft Support for backend assistance.
Looking for a Lightweight and Hassle-Free Office Suite?
If managing domains and complex cloud admin centers is slowing down your workflow, consider WPS Office. It provides a powerful, offline-capable productivity suite that lets you focus on creating documents rather than configuring IT infrastructure.

Frequently Asked Questions
Why is my TXT record not verifying in Microsoft 365?
This usually happens because DNS changes haven't fully propagated yet, which can take up to 48 hours. Alternatively, the TXT record may have been added to your domain registrar's control panel instead of the Microsoft 365 admin center when Microsoft nameservers are authoritative.
Can I use external nameservers with Microsoft 365?
Yes. You can choose to keep your nameservers at your domain registrar (like GoDaddy, Cloudflare, or Namecheap) and manually add the required TXT, MX, and CNAME records there instead of pointing the nameservers to Microsoft.
How do I check if my DNS records have propagated?
You can use free online DNS lookup tools like MxToolbox or Dig to check the public TXT and MX records for your domain. If the public results match the records you entered in the admin center, the propagation is complete.




