UPDATE – November 10, 2026: Official Microsoft confirmation
Microsoft has now confirmed that this was an issue on their side, caused by a faulty update to their spam filtering rules.
Official Microsoft 365 Service Health report:
- Incident: EX1545193
- Status: Service restored
- Affected services: Exchange Online
- Start: November 6, 2026, 7:00 PM (GMT+1)
- Resolved: November 9, 2026, 12:02 PM (GMT+1)
Root cause (Microsoft's own words):
"A recent update to the spam enforcement rules caused email messages to be incorrectly marked and blocked, which led to impact."
Final status – November 10, 2026:
"We've fully rolled back this update and confirmed that mail flow has been restored and impact is resolved."
Microsoft also states that they are reviewing their update procedures and improving their mail detection logic to prevent similar false positives.
What this means for affected users:
The issue was caused by Microsoft's filtering system, not necessarily by incorrectly configured sending domains.
My original workaround of adding a missing DMARC record successfully restored delivery, but Microsoft has now confirmed that the underlying incident was on their side.
Emails previously rejected with an NDR will need to be resent.
Source: Microsoft 365 Admin Center → Health → Service Health → EX1545193 (final incident report, November 10, 2026).
Also, see the November 10 update from Daniel-Vo (Microsoft External Staff), referencing incident EX1545193.
https://learn.microsoft.com/en-us/answers/questions/6063210/spf-validation-error?page=1
Original post – November 8, 2026
The information below documents my original investigation and the workaround that resolved the issue at the time. It is preserved for reference, but the incident has now been resolved by Microsoft.
Possible fix for AS9031519 – simple check for anyone missing emails in Hotmail, Live or Outlook
I've experienced this exact issue and managed to resolve it.
Emails from my Microsoft 365 account to a Outlook/Live address were rejected with:
550 5.7.1 Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)
The interesting part was that Microsoft's own message headers reported SPF, DKIM and DMARC as passing.
However, when I checked the sender domain's public DNS, the DMARC record was actually missing.
After adding v=DMARC1; p=none, I sent another test email to the same recipient, and it was successfully delivered.
You can check this yourself, even if you're just a regular Hotmail, Live or Outlook user. No administrator access or technical knowledge is required.
- Find the email address of someone whose emails aren't reaching you.
- Look at the domain after the @ sign. For example,
******@company.com means the domain is company.com.
- Open https://lookup.mxtoolbox.com/dmarc.aspx
- Enter the sender's domain and run the check.
- If it says DMARC Record Not Found, you have identified why their emails are being rejected.
You can also check using Windows PowerShell:
Resolve-DnsName _dmarc.company.com -Type TXT -Server 1.1.1.1
Replace company.com with the sender's domain.
If no DMARC record exists, contact the sender and ask them to have their email provider or IT administrator check the domain's DMARC configuration.
Important: Even if the email headers report dmarc=pass, don't assume a public DMARC record exists. My Microsoft 365 message showed this result despite the record being missing.
This issue has also been investigated by email provider MailRoute, which reports that Microsoft started rejecting some emails from domains without DMARC on November 5, including smaller senders:
https://mailroute.net/blog/outlook-rejecting-email-without-dmarc
MailRoute also reports that the rejection is intermittent. Some emails from the same domain may get through while others bounce, so successful delivery doesn't necessarily mean the domain is correctly configured.
Microsoft appears to have introduced stricter authentication checks, although I haven't seen an official announcement confirming the change.
A missing DMARC record is not proof of the cause in every case, but it's a simple and useful first check that anyone can perform.
Hopefully this helps others identify the problem without spending unnecessary time changing settings in their own Outlook accounts.