Fix Microsoft 365 Domain DNS Records Managed in AWS
Question details
The administrator needs to understand whether Microsoft Online nameservers are required and how to resolve missing Microsoft 365 domain DNS records managed in AWS.

- Product
- Microsoft 365 and AWS Route 53
- Device & OS
- not provided
- Scenario
- A domain administrator is configuring Microsoft 365 services while DNS is managed through AWS.
- Observed behavior
- The Microsoft 365 domain list shows a domain.microsoftonline.com entry with setup in progress, and Microsoft 365 reports missing DNS records.
Sign in to the Microsoft 365 admin center and the AWS account that manages the domain's DNS. Check the domain's nameservers at its registrar so you know which DNS provider is authoritative.
Add Microsoft 365 records to the authoritative AWS DNS zone
Use this method to keep DNS hosted in AWS while completing Microsoft 365 domain verification and service setup.
Microsoft Online nameservers are not required when another provider hosts the domain's DNS. A domain.microsoftonline.com entry or setup-in-progress status alone does not mean you must change nameservers.
In the Microsoft 365 admin center, go to Settings > Domains, select the domain, and open its setup or DNS records page. Note the verification status and records Microsoft lists as missing.
If verification is incomplete, copy the TXT verification record shown in the domain setup wizard. In AWS Route 53, open Hosted zones, select the authoritative public zone, and create the TXT record using Microsoft's specified name and value.
In the same Route 53 hosted zone, add the remaining records shown by Microsoft 365 for the services you use. These may include MX, CNAME, TXT, or SRV records; use the exact names and values from the admin center.
Return to the Microsoft 365 domain setup page and select Verify or recheck the DNS records. Allow time for DNS changes to propagate if the records are not detected immediately.

Check nameserver delegation before changing DNS providers
Use this check if records added in AWS are not being detected or you are considering moving DNS hosting.
Use WPS Office as a Free Microsoft 365 Alternative
WPS Office is a free, lightweight alternative for working with documents, spreadsheets, and presentations. Its familiar interface and Microsoft Office format compatibility make moving existing files straightforward. It does not change Microsoft 365 domain or DNS settings.

Frequently Asked Questions
Do I need Microsoft Online nameservers to use Microsoft 365?
No. You can keep DNS with an external provider such as AWS and add the verification and service records listed under Settings > Domains in the Microsoft 365 admin center.
Why does Microsoft 365 still report missing DNS records?
Verification or service configuration may be incomplete, records may have been added to a non-authoritative zone, or DNS changes may not have propagated yet. Compare the registrar's nameservers and the records in the authoritative zone with those shown under Settings > Domains.
Where do I add the Microsoft 365 verification record in AWS?
In Route 53, open Hosted zones, select the authoritative public zone for your domain, and create the TXT record shown in the Microsoft 365 domain setup wizard.
Should I change the MX record as soon as Microsoft 365 lists it?
Change the MX record when you are ready for incoming mail to be routed to the service specified by Microsoft 365. Review your existing mail configuration first, because changing MX can affect mail delivery.




