550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records

Collect complete bounce reports from several affected senders and escalate them through Outlook.com Help → Still need help?, because multiple unrelated domains are failing but Microsoft has not listed this exact AS9031519 rejection as a confirmed Outlook.com incident.

What the error means

• Your personal @outlook.com mailbox does not need DNS records that you configure. Microsoft controls SPF, DKIM, and DMARC for the outlook.com domain.
• The rejection normally refers to the external sender’s domain authentication, even though the Microsoft server shown in the error performed the rejection.
• Adding affected clients to Safe senders will not fix it: the message is rejected during the SMTP transaction before it reaches your mailbox.^1^

Microsoft documents that authentication failures can reject legitimate messages. For 550 5.7.1, possible causes include an incomplete SPF record, connector configuration, or destination security policy.^2^

AS9031519 is not defined in the available Microsoft documentation, so it does not by itself establish whether this is an enforcement change or a Microsoft service fault.

What to do now

1. Ask at least three affected clients using unrelated email providers to send you their complete non-delivery report (NDR), not just the one-line error.
2. Preserve these fields:
   • Full SMTP response
   • Sender domain and provider
   • UTC timestamp
   • Rejecting Microsoft server
   • Message or correlation identifiers
   • Any Authentication-Results details
3. Ask each sender to give the NDR to their email administrator or provider and request checks for:
   • SPF authorizing the actual sending server
   • A valid DKIM signature
   • A published DMARC record
   • SPF or DKIM alignment with the domain displayed in the message’s From address

If only one sender or domain fails, that sender’s provider needs to correct its authentication. If several unrelated providers fail—as reported here—submit the collected NDRs to Outlook.com Support:

1. Sign in to Outlook.com.
2. Select Help on the menu bar.
3. Enter the complete error text, including AS9031519.
4. Scroll to Still need help?
5. Select Yes, then attach or paste redacted NDRs from multiple unrelated senders.^3^

Microsoft’s current Outlook.com known-issues page does not identify this exact rejection signature as a confirmed incident.^3^ Therefore, the widespread pattern is valid evidence for escalation, but it is not yet confirmation of a Microsoft outage.

Conditional sender requirement

If an affected sender sends 5,000 or more messages per day to Microsoft consumer mailboxes using the same From domain, Microsoft’s high-volume sender rules apply. SPF and DKIM must both pass, DMARC must be published, and DMARC must pass through aligned SPF or DKIM.[^4^](https://support.microsoft.com/en-us/outlook/fix-ndr-error-550-5-7-515-in-outlook-com "Fix NDR error "550 5.7.515" in Outlook.com | Microsoft Support")

That threshold should not be assumed for every client; each sender’s administrator must determine whether it applies.

References

1. Incoming emails being blocked due to lack of SPF/DKIM/DMARC records on ...
2. Troubleshoot email authentication in Microsoft 365
3. Fixes or workarounds for recent issues on Outlook.com | Microsoft Support
4. Fix NDR error "550 5.7.515" in Outlook.com | Microsoft Support