Email

How to set up DMARC for a Microsoft 365 domain

In short. DMARC is the instruction that tells mail systems what to do with emails claiming to come from your domain without passing the checks: without it, anyone can write in your name, and your own emails are less well protected. A setting that is too strict too early can also cause your genuine emails to be rejected or sent to spam. It is up to you, or to your IT provider who manages your domain, to publish the rule at your domain host (in its directory, the DNS). The first line takes a few minutes; Microsoft then advises tightening the rule in stages, reading the reports you receive.

For a custom domain in Microsoft 365, you set up DMARC at your DNS host: a TXT record named _dmarc, for example v=DMARC1; p=none; rua=mailto:[email protected]. Set up SPF and DKIM first, then follow the rollout Microsoft recommends: p=none, then p=quarantine, then p=reject, reading the reports at each stage.

DMARC tells receiving mail servers what to do with an email that claims to come from your domain but fails SPF or DKIM: deliver it anyway, send it to junk, or reject it. It is your protection against fraudsters sending email in your name.

Last verified: November 18, 2026, against Microsoft's official documentation.

Prerequisites: SPF and DKIM on your domain

Microsoft asks for this explicitly: before DMARC, set up SPF and DKIM for every domain and subdomain that sends email from Microsoft 365.

Without DKIM on your own domain, Microsoft 365 signs with its .onmicrosoft.com domain. That signature isn't aligned with your address, so it doesn't count for DMARC.

Step 1: publish DMARC in monitoring mode

Microsoft 365 has no admin page or command for the DMARC record of your custom domains: you create it at your DNS host.

  • Type: TXT
  • Name / host: _dmarc (some hosts want the full name _dmarc.your-domain.com; check afterwards that the domain wasn't added twice)
  • Value:

    v=DMARC1; p=none; rua=mailto:[email protected]

Microsoft advises receiving the reports in a dedicated shared mailbox or Microsoft 365 group, not in an employee's mailbox. Start with rua only: detailed failure reports (ruf) can be very numerous, and Microsoft 365 doesn't send them itself.

For the exact clicks at your DNS host, see our guides for Cloudflare, GoDaddy, Namecheap, OVHcloud and Hostinger.

Step 2: read the reports

Aggregate reports usually arrive once a day from each mail provider, as an XML attachment that is often compressed. They show which servers send as your domain and whether they pass aligned SPF and DKIM.

What to look for:

  • a known service that fails (newsletter tool, CRM, invoicing): set up DKIM for it with your domain, or a sending address on your domain;
  • unknown addresses failing in volume: these are fraudulent emails, which DMARC will block once the policy is tightened;
  • Microsoft 365 passing: that's normal.

Microsoft advises reading them weekly during rollout, then monthly once stable. Not every receiver sends reports: Microsoft mentions a usual coverage of 70 to 90% of volume.

Step 3: move to quarantine, then reject

Once the reports are clean, tighten the policy:

  1. p=quarantine: emails that fail go to junk.

    v=DMARC1; p=quarantine; rua=mailto:[email protected]

    Microsoft suggests moving in steps with pct: 10, 25, 50, 75, then 100%.

  2. p=reject: emails that fail are rejected. This is the goal Microsoft sets for all your domains.

    v=DMARC1; p=reject; rua=mailto:[email protected]

Microsoft advises starting with a low-traffic subdomain and keeping the main domain for last.

A word on pct: the new version of the DMARC standard, published in May 2026 (RFC 9989), removed this parameter. A receiver that follows the new text may apply your policy to every message. Treat each step as a precaution, not a guarantee.

Good to know: when your policy is quarantine or reject, Microsoft 365 sends your outbound emails that fail DMARC at the recipient's end through its "high-risk delivery pool", and you can't change that behavior. One more reason to fix failures before tightening.

Check your domain for free. In a minute, with no account, AttackScout reads your DMARC, your SPF and the Microsoft 365 DKIM selectors, and tells you whether tightening the policy is already safe. Check my domain

The .onmicrosoft.com domain

This is the one exception: for the your-organization.onmicrosoft.com domain, you create DMARC in the Microsoft 365 admin center, not at a DNS host.

  1. Open https://admin.microsoft.com, then Show all > Settings > Domains.
  2. Select the .onmicrosoft.com domain (click the row, not the check box), then the DNS records tab.
  3. Select Add record. In the Add a custom DNS record flyout, choose Type TXT (Text), TXT name _dmarc, TXT value v=DMARC1; p=reject, TTL 1 hour. Select Save.

Microsoft recommends p=reject on this domain if you don't use it to send email.

Labels checked on November 18, 2026 in Microsoft's English documentation.

Step 4: check it works

  1. Run nslookup -type=TXT _dmarc.your-domain.com: there should be exactly one record, with the policy you chose.
  2. Send an email from Outlook to a personal Gmail mailbox, choose Show original and look for DMARC: 'PASS'.

You can also run our free DMARC checker again.

Frequently asked questions

Do subdomains need their own DMARC record?

No. The DMARC record of the main domain covers every subdomain that doesn't have its own, even those that don't exist. However, each subdomain that sends email needs its own SPF and DKIM.

A third-party tool fails DMARC. What should I do?

Its emails probably go out with the tool's own domain. In the tool, set up a DKIM signature with your domain, or a sending address (MAIL FROM) on your domain. Meanwhile, go back to the previous policy.

The reports don't arrive. Why?

Check that the rua mailbox exists. If it's on a different domain from the one being monitored, that domain must publish an authorization: a TXT record your-domain.com._report._dmarc.other-domain.com with the value v=DMARC1;.

Technical details

Exact configuration. A TXT record on the name _dmarc:

_dmarc.your-domain.com.  3600  IN  TXT  "v=DMARC1; p=none; rua=mailto:[email protected]"

Why. DMARC (RFC 7489, revised by RFC 9989) requires at least one of SPF or DKIM to pass with the domain of the visible address (From). Alignment is relaxed by default (aspf=r, adkim=r): a subdomain of your domain is accepted.

To check it yourself. Exactly one line should start with v=DMARC1:

dig +short TXT _dmarc.your-domain.com

Reference: https://www.rfc-editor.org/rfc/rfc7489

Sources

Accessed November 18, 2026.