Microsoft 365: what you should know
Microsoft 365 (Exchange Online) needs four things in DNS for a custom domain: one MX record to your own host under mail.protection.outlook.com, the SPF record with include:spf.protection.outlook.com, two CNAME records for DKIM and a DMARC record. The setup wizard in the admin center lists the first two, but not DKIM and DMARC.
That is exactly the gap in many tenants: for custom domains Microsoft 365 does not DKIM-sign outgoing mail until someone switches it on. Only senders of the onmicrosoft.com domain are signed automatically. DKIM is enabled in the Microsoft Defender portal, and DMARC exists in no portal at all: you create the record yourself at the DNS host.
The domain must be added in the Microsoft 365 admin center and verified through the TXT record shown there.
The values for Microsoft 365 at a glance
The records Microsoft 365 expects for a custom domain; the guides above cover the details.
- MX: 0 example-com.mail.protection.outlook.com
- SPF: v=spf1 include:spf.protection.outlook.com -all
- DKIM: Microsoft 365 uses two selectors, selector1 and selector2, and publishes the keys on its side rather than yours: you create two CNAME records pointing to Microsoft. That lets Microsoft swap keys without you touching DNS; only one of the two selectors is active at a time.
- DMARC: For custom domains Microsoft 365 has no portal and no switch for DMARC: the record is a TXT record at _dmarc that you create at the DNS host. Microsoft recommends starting with p=none and a reporting address, then p=quarantine with a rising pct value and finally p=reject, subdomains first and the parent domain last.
Where to create the records
Microsoft 365 specifies the values; they are created at the domain’s DNS host, the place the name servers point to. The guides by host show the way to the DNS editor of IONOS, STRATO, Hetzner, Cloudflare and other providers.