Microsoft 365 and Outlook.com combine SPF, DKIM and DMARC with their own signals — sender reputation, history, behaviour — into one verdict for the From domain: composite authentication. A fail means Microsoft could not confirm the message really came from that domain; the reason code says why. It often sends the message to Junk.
spf=none (sender IP is 192.0.2.1) smtp.mailfrom=example.com; dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=example.com;compauth=fail reason=001
How other mail servers write it
DMARC failed with quarantine or reject
compauth=fail reason=000
Your own domain, sent from outside
compauth=fail reason=601
A soft pass
compauth=softpass reason=201
Not checked, or bypassed
compauth=none reason=905
| Result | compauth=fail reason=001 |
| Usually fixed by | The sending domain’s owner |
| Written by | Microsoft 365 and Outlook.com |
| Values | pass, fail, softpass, none — with reason= a three-digit code |
| On its own | Does not block a message; spoof protection weighs it with everything else |
Check the sending domain
Enter the domain from the From address: we check its SPF, DKIM, DMARC and mail servers together.
What it means
Composite authentication is Microsoft’s answer to domains without strong records: where there is no DMARC to decide, it adds “implicit authentication” from what it knows about the sender. The verdict is evaluated for the From domain. A fail does not block the message by itself, but spoof intelligence acts on it together with other signs — by default moving the message to Junk.
Why it happens
- 000: DMARC failed and the domain’s policy is quarantine or reject.
- 001: the domain has no authentication records, or only weak ones (~all, ?all, p=none), and Microsoft could not vouch for the message.
- 002: the recipient’s organisation blocks this sender from sending as that domain.
- 010 and 601: the message claims to come from one of the recipient organisation’s own domains, but arrived from outside.
How to fix it
- As the sender: publish SPF and DKIM for the domain, aligned with the From address, and a DMARC record — compauth then passes with 100 to 102.
- As the recipient’s admin, for legitimate mail: allow the sender in spoof intelligence or the Tenant Allow/Block List.
- If mail reaches Microsoft 365 through another service first, turn on Enhanced Filtering for Connectors, or add the service as a trusted ARC sealer.
Every reason code
| Code | Result | What it means |
|---|---|---|
| 000 | fail | DMARC failed, and the policy is quarantine or reject |
| 001 | fail | No authentication records, or only weak ones |
| 002 | fail | The organisation prohibits this sender from sending as this domain |
| 010 | fail | DMARC failed on one of the organisation’s own domains |
| 100 | pass | SPF or DKIM passed, aligned with the From domain |
| 101 | pass | Signed with DKIM by the From domain |
| 102 | pass | SPF passed, aligned with the From domain |
| 103, 104 | pass | The sending IP’s reverse DNS matches the From domain |
| 108 | pass | DKIM broken by a legitimate earlier hop |
| 109 | pass | No DMARC record, but it would have passed |
| 111 | pass | DMARC could not be checked, but SPF or DKIM aligned |
| 112 | pass | A DNS timeout on the DMARC lookup |
| 115 | pass | Sent from a Microsoft 365 organisation that owns the From domain |
| 116 | pass | The From domain’s MX matches the sending IP’s reverse DNS |
| 130 | pass | ARC from a trusted sealer overrode the DMARC failure |
| 2xx (201, 202) | softpass | Soft-passed implicit authentication — reverse DNS matches |
| 3xx, 4xx | none | Not checked, or bypassed |
| 501, 502 | — | DMARC not enforced for a valid bounce message |
| 6xx (601) | fail | Failed implicit authentication — 601: sent as your own domain from outside |
| 7xx (701–704) | pass | Passed implicit authentication — known legitimate infrastructure |
| 9xx (905) | none | Bypassed — complex routing through another service first |
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- Anti-spam message headers — learn.microsoft.com
- How email authentication works in Microsoft 365 — learn.microsoft.com
- Anti-phishing policies in Microsoft 365 — learn.microsoft.com
- Troubleshoot email authentication in Microsoft 365 — learn.microsoft.com