Skip to content
  • There are no suggestions because the search field is empty.

Microsoft and Outlook authentication rules

Outlook.com requires high-volume senders to pass SPF and DKIM and publish a passing DMARC record, and can reject or junk mail that doesn't; Microsoft 365 business mailboxes apply their own anti-spoofing checks and settings. Those are two different receivers. The published microsoft bulk sender requirements cover only the consumer side: outlook.com, hotmail.com, and live.com addresses. A company running on Microsoft 365 filters your mail with its own tenant settings, and there's no published volume rule for it.

This is the deep version for Microsoft. For the short comparison with Gmail and Yahoo, see Google, Yahoo, and Microsoft sender requirements. Gmail and Yahoo detail is in Google and Yahoo sender requirements.

If your mail already passes these checks and still lands in Junk, see Authentication passes, but Outlook still puts mail in Junk.

Outlook.com sender requirements (consumer mailboxes)

Microsoft announced the rule in April 2025 and is explicit about scope: "This applies to Outlook.com - our consumer service, which is supporting hotmail.com live.com and outlook.com consumer domain addresses". Its support page also names MSN among the related consumer services.

Who it covers. Microsoft calls them "high-volume senders," not bulk senders. The threshold is worded two ways: 5,000 or more email messages to Microsoft consumer email services, and domains sending more than 5,000 emails per day. Plan around roughly 5,000 a day to consumer addresses.

What they need:

  • SPF and DKIM, and "Both SPF and DKIM checks must pass." An SPF-only sender doesn't qualify, even with a perfect SPF record.
  • A DMARC record. Microsoft's example is v=DMARC1; p=none at _dmarc. Any of p=none, p=quarantine, or p=reject is valid.
  • A DMARC pass. The SPF or DKIM result (at least one) must align with the domain in the From address, and preferably both. More on alignment: Identifier alignment for SPF and DKIM.

What Microsoft recommends but doesn't require. Additional hygiene recommendations include valid From and Reply-To addresses, functional unsubscribe links, list hygiene, and transparent practices. There's no one-click HTTP POST requirement at Outlook.com, unlike Gmail.

Two FAQ details worth knowing. Adding yourself to recipients' Safe Senders doesn't help: "Safe Sender list won't be honored." And Microsoft sends aggregate (rua) reports but says "We don't have plans to send RUF."

Sending less than 5,000 a day? all senders benefit from these best practices. That's advice, not a published requirement.

Junk or reject? Microsoft's pages disagree

What happens to non-compliant mail depends on which Microsoft page you read. We're not picking one, and you shouldn't plan around only one.

  • When Outlook.com rejects the message, the bounce looks like: 550 5.7.515 Access denied, sending domain <domain> does not meet the required authentication level.
  • Microsoft's published Outlook.com pages don't agree with each other. One version said non-compliant mail would first be routed to Junk and might be rejected later. An April 29, 2025 update then said Microsoft had decided to reject messages that don't pass, with 5.7.515 wording, taking effect on May 5. The same update then said that after May 5, 2025, Outlook would begin routing messages from high-volume non-compliant domains to the Junk folder, and that in the future (date to be announced) non-compliant messages would be rejected. The original junk-first wording is still published alongside that.
  • Outlook.com Postmaster still describes non-compliant messages as going to the junk folder, and says they will shortly be rejected until the DNS records are corrected.

So a non-compliant high-volume sender can see a 5.7.515 bounce, or mail that lands in Junk with no bounce at all. Either way the fix is the same: get SPF and DKIM passing, and get at least one of them aligned with your From domain. If you have a bounce in hand, see our Troubleshooting articles.

Microsoft 365 business mailboxes

When you send to a company on Microsoft 365, the Outlook.com rule isn't what's judging you. We didn't find a published sender-volume requirement for Microsoft 365 tenants, so don't extend the 5,000 rule to them. (That isn't proof Microsoft won't publish one.)

Composite authentication. Microsoft 365 runs SPF, DKIM, and DMARC, then adds other signals into a single result called composite authentication, stamped as compauth in the Authentication-Results header. A header might read compauth=fail reason=001 or compauth=pass reason=109. Microsoft is clear that "a composite authentication failure doesn't directly result in a message being blocked"; it uses "a holistic evaluation strategy".

Your DMARC policy is a request their admin can tune. In Microsoft 365 anti-phishing policies, each tenant decides whether to "Honor DMARC record policy when the message is detected as spoof." If it's on (Microsoft's recommended setting), the admin picks the action:

Your policy Actions the receiving tenant can choose
p=quarantine Quarantine the message, or move it to Junk Email
p=reject Quarantine the message, or reject it
p=none "No action based on DMARC," though other filters still apply

Those are the actions the receiving tenant can choose. When Honor DMARC is on, Microsoft documents the usual result as: failing p=quarantine mail goes to the Junk Email folder (configurable to quarantine), and failing p=reject mail is rejected during SMTP (DMARC for Microsoft 365). So the same failing message can be rejected at one customer and held in quarantine at another. What happens to failing mail under each policy covers what each policy does to failing mail in more detail.

Gateways in front. If the tenant's MX points to a third-party gateway, the Honor DMARC setting applies only if Enhanced Filtering for Connectors is turned on. Corporate gateways also have rules of their own.

When Microsoft 365 is the sender

If your own domain sends from Microsoft 365, the setup is in DMARC for Microsoft 365. Two outbound behaviors are worth knowing here:

  • If your domain is at p=quarantine or p=reject and your outbound mail fails DMARC at the destination, Microsoft routes it through its high-risk delivery pool, and "There's no override for this behavior".
  • Exchange Online validates recipients' MTA-STS policies on outbound mail automatically (MTA-STS, TLS-RPT, and SMTP TLS).

Monitoring at Microsoft

  • SNDS gives IP-level data for IPs you control, plus the Junk Email Reporting Program. Its home page says "Deliverability to Outlook.com is based on your reputation". See IP and domain reputation.
  • DMARC aggregate reports. Microsoft sends them, so you can see whether your sources pass SPF, DKIM, and aligned DMARC at Outlook.com. BIMI Certifications' DMARC reporting and visual analysis shows that per source. It doesn't change how Outlook.com or a tenant filters your mail.

Common mistakes

  • Treating Outlook.com and Microsoft 365 as one system. The published rule is consumer-only.
  • Sending SPF-only. Outlook.com's high-volume rule needs both SPF and DKIM to pass.
  • Relying on the old junk wording. Plan for a 5.7.515 rejection too.
  • Expecting your p=reject to be applied the same everywhere. Each Microsoft 365 tenant chooses its own action.
  • Moving every domain to p=reject in a hurry after a bounce wave. Microsoft itself advises "moving gradually (none → quarantine → reject) to avoid unintended mail loss" (A safe rollout: p=none to quarantine to reject).

For why DMARC matters beyond these provider rules, see Why DMARC on our main site. Setup problems specific to Microsoft 365 are in Microsoft 365 or Google Workspace setup issues.

Free DMARC account

Not sure which sender is failing?

Connect your domain's DMARC reports and see every service that sends as your domain, and whether each one passes SPF, DKIM and DMARC.

  • Every sending source in one dashboard
  • SPF, DKIM and alignment results per sender
  • No XML files to read

Create a free DMARC accountTalk to an expert

FAQ

Do the Outlook.com rules apply to my customers on Microsoft 365?

The published high-volume rule is for consumer Outlook.com, Hotmail, and Live. Microsoft 365 business mailboxes apply their own anti-spoofing checks and settings.

Is one-click unsubscribe required at Outlook.com?

No. Microsoft recommends functional unsubscribe links. It doesn't require the one-click HTTP POST method.

Is p=none enough for Outlook.com?

For the high-volume rule, yes, as long as SPF and DKIM both pass and at least one aligns with your From domain. It doesn't protect your domain from spoofing.

Will Outlook.com junk or reject our mail if we're not compliant?

Microsoft's published guidance still disagrees: some pages say reject with 5.7.515; another still says junk first. Fix the authentication rather than betting on one outcome.