What Microsoft 365 does with inbound mail that gets spf=softfail or spf=permerror, how to read Authentication-Results, and how to fix a missing sender, a broken SPF record, a gateway or a forwarder.
Home › Guides › Microsoft 365 inbound SPF softfail
Last updated 17 November 2026
On mail received by your Microsoft 365 tenant, open the message headers (or Message trace) and find Authentication-Results. Microsoft records the SPF result in this form:
spf=softfail (reason) smtp.mailfrom=example.com spf=permerror smtp.mailfrom=example.com
softfail (and fail) means the connecting IP is not listed in the envelope-sender domain's SPF record. That is common after a new vendor, an on-premises relay or a forwarder is added, and it is also what you see on a lot of spoofed mail. permerror means the published SPF record could not be evaluated: Microsoft's troubleshooting guide names a record over the 10 DNS lookup limit, or more than one SPF TXT record for the same domain. In both cases Microsoft 365 still runs DKIM, DMARC and composite authentication (compauth). A softfail or permerror does not, by itself, always reject the message; delivery then depends on DKIM, DMARC, compauth, spoof intelligence and your anti-phishing policy.
If you send to someone else's Microsoft 365 tenant and their headers show these results, the same record problems are on your domain: fix them with the SPF Record Checker and the SPF Record Builder.
spf=, smtp.mailfrom, dkim=, dmarc=, header.from, compauth= and the three-digit reason.Microsoft's Authentication-Results SPF syntax is spf= followed by pass (with the IP), fail (with the IP), softfail (with a reason), neutral, none, temperror or permerror, then smtp.mailfrom= and the envelope domain. The IP in parentheses is the client Microsoft evaluated, which matters when mail arrived through a gateway.
RFC 7208 defines the results. This is how they typically show up on inbound Microsoft 365 mail:
| Result | What it means (RFC 7208) | Typical cause on inbound mail |
|---|---|---|
pass | The client is authorized to use that envelope-sender domain. | The sending IP is in the domain's SPF record (including via include). |
fail | The client is not authorized (-all matched). | Missing vendor or relay IP; or a forwarder, whose IP is not in the original domain's record (expected). |
softfail | A weak statement that the host is probably not authorized (~all matched). | Same causes as fail, on a domain that still uses ~all. |
neutral | The domain makes no assertion (?all, or no terminating all). | An incomplete record. |
none | No usable SPF record was found. | The envelope-sender domain publishes no v=spf1 TXT record. |
temperror | A temporary DNS error; a later retry might work. | The authoritative DNS server timed out or was unreachable. |
permerror | The published records could not be correctly interpreted and need operator action. | Two SPF TXT records; more than 10 DNS lookups; a syntax error; a missing include or redirect target (see include not found and void lookups). |
Microsoft's troubleshooting table matches this for the common cases: none is no record; permerror is the 10-lookup limit or multiple records; temperror is a temporary DNS failure; softfail or fail means the sending IP is not in the record, often after adding a new email service or a non-Microsoft relay; forwarded mail failing SPF is expected because the forwarding server's IP is not in the original sender's record.
SPF is only one input. Microsoft 365 also checks DKIM and DMARC, then stamps composite authentication (compauth) on the From domain. From Microsoft's authentication and anti-spoofing docs:
compauth passes, the message is delivered normally (other filters still apply).compauth fails, spoof intelligence evaluates the sender. A sender it already treats as legitimate can still be delivered. A sender it treats as suspicious gets the action in your anti-phishing policy (Junk Email or quarantine).compauth and still be allowed if other assessments do not indicate a suspicious nature.For ~all (softfail), Microsoft's SPF setup page says sources not in the record probably are not authorized, so messages should be accepted but marked, and that what actually happens depends on the destination system (quarantine, Junk Email, or Inbox with a tag). Do not assume every inbound softfail is rejected, and do not assume every one is delivered.
Reason codes such as 000 (explicit DMARC fail at quarantine or reject) and 001 (implicit authentication fail) are covered in the compauth=fail reason-code guide.
Decide whether the sender is a service you expect.
If other Microsoft 365 tenants (or your own test mailbox) show spf=softfail, spf=fail or spf=permerror on mail from your domain:
v=spf1 records into one, add the missing sending IP or vendor include, and stay under 10 lookups.include:spf.protection.outlook.com (see SPF for Microsoft 365).spf=pass with the expected IP, or, when SPF cannot pass (a forwarder), dkim=pass and dmarc=pass with a good compauth.Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Read the header with the Email Header Analyzer, then check the sending domain with the SPF Record Checker, SPF Record Builder, Email Deliverability Checker, DNS Lookup and DNS Propagation Checker. Related guides: Microsoft 365 compauth=fail, SPF for Microsoft 365, SPF too many DNS lookups, SPF include not found and void lookups, DMARC fail with SPF pass and DMARC fail after forwarding.
Both mean the connecting IP is not authorized by the envelope-sender domain's SPF record. fail is a hard fail (the record ended in -all); softfail is the weaker ~all result. Microsoft 365 records either value in Authentication-Results and then still evaluates DKIM, DMARC and compauth rather than treating softfail as an automatic reject.
Not automatically, and Microsoft does not publish a single bounce string for this case. permerror means the SPF record could not be evaluated (Microsoft highlights more than 10 DNS lookups or more than one SPF record). The message still gets DKIM, DMARC and composite authentication, and spoof intelligence plus your anti-phishing policy decide whether it is delivered, junked or quarantined.
The IP that connected to Microsoft 365 is not in that domain's SPF record. Typical causes are a new sending service, an on-premises relay, an inbound gateway in front of your tenant, or a forwarder. Ask the sender to update SPF or sign aligned DKIM, and use Enhanced Filtering for Connectors if the mail arrives through your own gateway.
Yes. DMARC passes when either aligned SPF or aligned DKIM passes, and Microsoft composite authentication uses those results plus other signals. That is why DKIM matters for forwarded mail, where SPF almost always fails, and why a softfail alone should not be read as "this message is spoofed".
In the Authentication-Results header of the delivered or quarantined message, and in Message trace. Paste the headers into the Email Header Analyzer. The SPF check is against smtp.mailfrom (the envelope sender), not the From address people see.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.