- Subject
- Microsoft 365 & SharePoint
- Filed
- Source
- Al Iverson
- Loans
- 518
Microsoft Outlook.com Mail Rejections Resolved After DMARC Checks Disrupted Delivery
Microsoft’s temporary rejection of some mail without DMARC ended November 9, 2026. The incident affected Outlook.com consumer domains, not Microsoft 365 mail.

Microsoft’s temporary rejection of email from domains without DMARC records disrupted delivery to Outlook.com consumer inboxes from November 6 through November 9, 2026. The incident matters to administrators because messages could be rejected even when SPF and DKIM checks passed, and because Microsoft 365 hosted corporate mail did not appear to be affected.
The reported bounce was 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records. The problem was reported for Microsoft consumer email services such as outlook.com, hotmail.com, live.com and msn.com. The available reports described intermittent failures: some messages were rejected, but the issue did not necessarily affect every attempt.
Consumer Outlook and Microsoft 365 behaved differently
Tests on November 7 showed a clear split between consumer and business destinations. A message sent to outlook.com from a domain without a DMARC record was bounced by outlook-com.olc.protection.outlook.com with the 550 5.7.1 response. A separate message to a Microsoft 365 hosted corporate domain was accepted and queued for delivery with a 250 2.6.0 response.
That distinction helps narrow the operational impact. The reports concerned Microsoft Outlook Consumer, often abbreviated as OLC, and did not indicate a broad rejection across Microsoft 365 hosted business mail. Teams investigating a bounce should therefore check the recipient domain and the exact SMTP response instead of assuming every Microsoft destination is affected in the same way.
The incident affected senders described as non-bulk as well as larger senders. Microsoft’s updated sender requirements, last updated in 2025, set requirements for high-volume senders sending more than 5,000 messages per day to Microsoft domains. Those requirements call for SPF, DKIM and DMARC. Senders below that volume were not described as being required to meet the same standard, yet the temporary behavior appeared to reject at least some of their messages when DMARC was absent.
Microsoft’s rollback ended the reported failure
The rejection spike began on Friday night, November 6, US time, with administrators reporting cases on the Mailop mailing list and elsewhere. By Monday, November 9, the issue was reported resolved. The timing suggests Microsoft rolled back a code or filtering change behind the rejections, although the specific technical cause was not established.
A Microsoft support forum response was cited as an indication that the behavior may have been unintended. That points to a possible service defect rather than a clearly announced change to the published sender requirements. The distinction is useful for incident records: the observed rejection was real, but it should not be treated as evidence that Microsoft permanently changed its documented threshold for non-bulk mail.
What administrators should check
Although delivery recovered, the episode exposed a gap that SPF and DKIM alone did not prevent. Domain owners who send mail should verify that their DNS contains a DMARC TXT record at _dmarc.<yourdomain>. The source of the incident recommended starting with the value v=DMARC1; p= and then using a DMARC tool or service to investigate and manage the record. Administrators should confirm the right configuration for their own domain and sending setup before changing DNS.
For organizations that send through a CRM, marketing platform or hosted email provider, the provider may control the sending infrastructure and need to help diagnose authentication and delivery. A bounce report should be matched to the relevant sending domain, the recipient service and the SMTP diagnostic text. That makes it easier to tell whether a message failed authentication, encountered a temporary filtering behavior, or was rejected for another reason.
Administrators who manage multiple brands or mail systems can also compare notes with other operators through the Mailop list, which focuses on operational issues affecting email systems. During a sporadic incident, reports from other senders can help establish whether the failure is isolated or shared across destinations.
DMARC is useful even below the bulk threshold
For smaller senders, the practical lesson is to treat DMARC as part of the domain’s normal email configuration, even when a provider’s documented bulk threshold does not require it. A valid record would have avoided this particular failure mode for the affected senders. It also gives domain owners a clearer basis for monitoring how their domain is used in outgoing mail.
The immediate Outlook.com problem was resolved on November 9, 2026, and the reported tests did not show the same behavior for Microsoft 365 corporate recipients. Teams should still review DMARC coverage across sending domains and retain the exact bounce details when delivery problems occur. That preparation makes the next authentication or filtering change easier to assess, whether it is intentional or an unexpected service behavior.
