DMARC with Microsoft 365: what the provider specifies
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.
The tenant’s onmicrosoft.com domain is often forgotten. It can be abused as a sender too and gets its own DMARC record: in the Microsoft 365 admin center you add a TXT record with the name _dmarc and the value v=DMARC1; p=reject under the DNS records of that domain.
As a receiver, Microsoft 365 sends aggregate reports to the rua address of the sender domain, but only for mail to recipient domains whose MX points directly to Microsoft 365; if another service sits in front of Microsoft 365 there are none. Microsoft never sends forensic reports. Inbound, Microsoft evaluates the sender’s policy: with p=reject the message is rejected, with p=quarantine it goes to Junk, provided the anti-phishing policy honors the DMARC policy.
v=DMARC1; p=none; rua=mailto:dmarc@example.comHow to set up DMARC for Microsoft 365
The procedure in four steps:
- Check that SPF and DKIM are in place for Microsoft 365: include:spf.protection.outlook.com in the SPF record and signing enabled in the Defender portal.
- At the DNS host create a TXT record with the name _dmarc and the starting value with p=none and a rua address.
- Evaluate reports for a few weeks, fix further senders such as a newsletter tool or ticket system, then tighten to p=quarantine and p=reject.
- In the Microsoft 365 admin center add a TXT record _dmarc with v=DMARC1; p=reject to the onmicrosoft.com domain.
Publishing at the DNS host
The DMARC record is a TXT record with the name _dmarc. It applies to the whole domain and every service sending on its behalf, not just the mail provider. The guides per host below show how to enter the name in the respective DNS editor.
Verify and keep an eye on it
The DMARC checker below reads the record, checks policy, reporting addresses and alignment and shows whether it matches SPF and DKIM of Microsoft 365. DomainWarn keeps checking the record afterwards and alerts you when it changes or the policy is relaxed.