Microsoft Account Errors

How to Fix Microsoft 365 Domain Verification Failed on AWS

Aamir Naveed AkramAamir Naveed Akram Nov 3, 2026 869 views

Question details

The user is unable to complete the Microsoft 365 domain verification process for a custom domain hosted on AWS Route 53.

How to Fix Microsoft 365 Domain Verification Failed on AWS Route 53
Product
Microsoft 365, AWS Route 53
Device & OS
not provided
Scenario
Attempting to connect and verify a custom domain hosted on AWS with a Microsoft 365 subscription.
Observed behavior
Verification fails due to missing or incorrectly formatted TXT records, DNS propagation delays, or the user being unable to access the admin center because of a lost multifactor authentication (MFA) device.
Before you start

Ensure you have your Microsoft 365 administrator credentials and access to your AWS Management Console before modifying DNS records.

Solution 1Recommended

Add and Verify the TXT Record in AWS Route 53

To prove ownership of your domain, you must add the exact TXT record provided by Microsoft into your authoritative AWS Route 53 hosted zone.

Domain verification typically fails if the TXT record is placed in the wrong DNS zone, contains formatting errors, or simply hasn't propagated across the internet yet.

1
Copy the TXT record from Microsoft 365

Log in to the Microsoft 365 admin center, navigate to Settings > Domains, select the domain you are trying to verify, and copy the required TXT value.

2
Add the record to AWS Route 53

Log in to the AWS Management Console and open Route 53. Select your domain's Hosted Zone, click 'Create record', select 'TXT' as the routing type, and paste the Microsoft value into the text box. Save your changes.

3
Wait for DNS propagation

Allow some time for the DNS changes to propagate. You can use an external DNS lookup tool (like MXToolbox) to check if your new TXT record is visible publicly.

4
Retry verification

Return to the Microsoft 365 admin center domain setup page and click 'Verify' to complete the process.

Add and Verify the TXT Record in AWS Route 53
DNS Propagation Delays: While DNS updates in AWS Route 53 are usually fast, global DNS propagation can occasionally take between 10 minutes and 48 hours.
Free Microsoft Office alternative

Looking for a Hassle-Free Office Suite? Try WPS Office

If you want to avoid complex admin centers, DNS configurations, and domain verifications, WPS Office is the perfect solution. It offers a free, lightweight, and user-friendly alternative to Microsoft Office that doesn't require cloud domain setups.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installer for your Windows, Mac, or Linux device.
  2. 2. Install the software: Run the setup file. The installation is lightweight and takes only a few moments to complete.
  3. 3. Start working immediately: Open WPS Office and instantly start editing your existing Microsoft Word, Excel, and PowerPoint files with zero compatibility issues.
Completely free and lightweight Office suiteFully compatible with Microsoft Office formats like DOCX, XLSX, and PPTXNo complex domain verification or admin center setups requiredFamiliar user interface makes switching effortless
microsoft office alternative - wps office

Frequently Asked Questions

Why is Microsoft 365 unable to find my TXT record on AWS Route 53?

This usually happens due to DNS propagation delays, incorrect formatting (like missing quotes), or adding the record to the wrong hosted zone. Verify that you updated the authoritative hosted zone in AWS and use an external DNS lookup tool to confirm it is publicly visible.

Can a Microsoft forum moderator fix my domain verification issue?

No. Microsoft forum moderators do not have backend access to resolve domain-verification issues or bypass administrator lockouts. You must contact official Microsoft phone support or your subscription reseller.

How long should I wait before clicking Verify in Microsoft 365?

After adding the TXT record to AWS Route 53, wait at least 10 to 15 minutes before attempting to verify. In some cases, global DNS propagation can take up to 48 hours.