The MX values for Microsoft 365
Microsoft 365 expects exactly one MX record. It points to a host under mail.protection.outlook.com whose first part is built from the domain name, with dashes instead of dots. The admin center shows the exact value when you set up the domain.
The priority must be lower than that of any other MX record so Microsoft 365 is tried first; Microsoft names a TTL of 3600 seconds. Old MX records of the previous provider should be removed after the move, otherwise part of the mail keeps arriving there.
Setup also includes a CNAME autodiscover pointing to autodiscover.outlook.com so Outlook finds the mailboxes. If a gateway in front protects the mailboxes, the MX points to the gateway instead of Microsoft.
0 example-com.mail.protection.outlook.comHow to set up the MX records for Microsoft 365
The order when switching to Microsoft 365:
- Add the domain in the Microsoft 365 admin center and verify it through the TXT record shown.
- Copy the MX value from the wizard and create it at the DNS host as the MX record for the apex domain, with the lowest priority.
- Remove MX records of the previous provider and create the CNAME autodiscover pointing to autodiscover.outlook.com.
- Let the admin center check the DNS records of the domain and cross-check with the MX checker.
Publishing at the DNS host
MX records sit on the apex domain and consist of priority and host name; the lowest number is tried first. Before the switch it pays to lower the TTL of the old records so the change arrives everywhere quickly. The guides per host below show the fields in the respective DNS editor.
Verify and keep an eye on it
The MX checker below shows the domain’s mail servers with priorities and checks whether they are reachable and offer TLS. You see whether only the Microsoft 365 servers are returned. DomainWarn then monitors the MX records permanently and reports every change.