Skip to content
DMARC Pulse

Microsoft 365

Setup DMARC Office 365: step by step on Microsoft 365 domains

Set up DMARC in Office 365: add a _dmarc TXT record at your DNS host, start with p=none, read the reports, then move to quarantine and reject with care.

Before you start

To set up DMARC for Office 365, publish one TXT record named _dmarc for each domain that sends mail, and start with p=none, which only monitors. Microsoft's documentation calls the service Microsoft 365.

  • Custom domain such as example.com. Create the record at your registrar or DNS host, because Microsoft 365 has no portal or PowerShell cmdlet for it. You need access to that account. If Microsoft 365 hosts your DNS, use Settings > Domains > your domain > DNS records > + Add records.
  • The *.onmicrosoft.com domain. You add the record in the Microsoft 365 admin center. Microsoft requires the Domain Name Administrator role to add or change domains. Its DMARC page names no role for this record.

First configure SPF for Microsoft 365 and DKIM signing for every custom domain and subdomain that sends mail. Microsoft's DKIM page says custom domains get no DKIM signing until you set it up.

Choose a shared mailbox or reporting service for aggregate reports, the XML summaries that receiving servers typically send once a day.

Steps

  1. At your DNS host, edit the existing _dmarc TXT record. Create one only if absent; keep one record per name. For a new record, use this monitoring value:

    TXT
    v=DMARC1; p=none; rua=mailto:dmarc@example.com
  2. Add a record for the *.onmicrosoft.com domain too. In the admin center at admin.microsoft.com, go to Show all > Settings > Domains and click that domain's row. Open the DNS records tab and select Add record. Enter _dmarc in TXT name, paste the value below in TXT value, and select Save.

    TXT
    v=DMARC1; p=reject

    Microsoft gives this value for domains that send no mail, including domains you registered and never use. Check first that no mailbox or app sends from that address. If one does, use p=none with a rua address.

  3. Read the aggregate reports weekly and fix all legitimate senders. Start with a low-volume domain. RFC 9989 advises mailing-list user domains against p=reject; if proceeding anyway, monitor at p=none for at least a month, then at p=quarantine for as long.

  4. When legitimate mail passes, edit the existing _dmarc record to move to quarantine. Do not add another record:

    TXT
    v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com

    Caution: from here, legitimate mail that fails DMARC can land in junk or quarantine. Microsoft also routes outbound mail that fails DMARC at the destination through its high-risk delivery pool when your policy is p=quarantine or p=reject. Many receiving servers refuse that pool, and Microsoft offers no override.

  5. After further monitoring, edit the same record to move to reject:

    TXT
    v=DMARC1; p=reject; rua=mailto:dmarc@example.com

    Caution: p=reject asks receiving servers to refuse failing mail. RFC 9989 says domains that publish it must apply valid DKIM signatures and must not rely on SPF alone. It also advises domains whose users post to mailing lists not to use it. Repeat these steps for each remaining subdomain, then the parent.

Confirm it worked

  1. Run nslookup -type=TXT _dmarc.example.com 1.1.1.1 or use the DMARC checker. You should see exactly one record that starts with v=DMARC1. Microsoft gives no propagation time for this record. A resolver that cached the old answer can keep it for the TTL (cache lifetime), which is 1 hour in the admin center.
  2. Send a message to a mailbox outside your organization and open its headers. In Authentication-Results, look for dmarc=pass and header.from=example.com.
  3. Wait at least a full day for the first aggregate report at your rua address.

Common problems

  • dmarc=bestguesspass in the header. No DMARC record exists for the domain. Publish the record and check its name.
  • DKIM passes but DMARC fails. If header.d= shows a *.onmicrosoft.com domain or another domain, DKIM does not align. Configure DKIM for the exact domain in the From address.
  • A third-party service fails DMARC. SPF can pass for the service's domain while smtp.mailfrom= (the envelope sender) is not yours. Set up DKIM with your domain at that service.
  • Two TXT records at _dmarc. RFC 9989 Section 4.10 discards them all. Keep one.
  • No reports from Microsoft. Microsoft 365 sends aggregate reports only when the recipient domain's MX record (mail routing) points directly to Microsoft 365. Hybrid setups and third-party gateways stop them. It does not send failure reports, even with a valid ruf= address. See DMARC reports not received.

Check it now

Look up and validate a DMARC record

Frequently asked questions

Does Microsoft 365 set up DMARC automatically?
No. Microsoft says SPF and DKIM are already configured for your onmicrosoft.com domain, but you still have to create its DMARC record. Custom domains need SPF, DKIM signing and a DMARC record that you set up yourself.
Where do I add the DMARC record for a custom domain in Microsoft 365?
At the registrar or DNS host for that domain, as a TXT record named _dmarc. Microsoft says Microsoft 365 has no admin portal or PowerShell cmdlet for DMARC records in custom domains. If Microsoft 365 hosts your DNS, use Settings, Domains, your domain, DNS records and + Add records.
Do I need DKIM before DMARC in Office 365?
Microsoft says to create SPF records and configure DKIM signing for every custom domain and subdomain that sends mail before you configure DMARC. RFC 9989 also says a domain that publishes p=reject must apply valid DKIM signatures and must not rely on SPF alone.
Should I use pct to roll out DMARC in Microsoft 365?
Do not depend on it. Microsoft's examples still show pct, and its headers can report pct.quarantine and pct.reject. RFC 9989 removed the tag because partial values were usually applied inaccurately. Move one policy level at a time and watch your reports.
Does Microsoft 365 send DMARC reports?
It sends aggregate reports when the recipient domain's MX record points directly to Microsoft 365. It does not send forensic (failure) reports, even when a valid ruf address is published.
What does dmarc=bestguesspass mean in a Microsoft 365 header?
No DMARC record exists for the sending domain. Microsoft says the message would pass the DMARC check if the domain had a record. Publish a record at _dmarc to get a real result.

Sources consulted

RFC 9989 §4.1: DMARC Basics
checked 2026-11-09

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.