Outlook emails going to spam: a sender's repair sequence for Microsoft mailboxes

The report usually arrives secondhand. A customer mentions the invoice was in junk, a sales rep notices replies only come from Gmail users, or a campaign's clicks from company domains quietly collapse. Microsoft's filtering is a separate system from Google's, trained on its own users' reactions, and in business tenants each company adds its own settings on top. Fixes that worked for Gmail are necessary but not always sufficient. This is the repair sequence from the sender's side, in the order that avoids wasted work. If you want the mechanics behind each step first, read how the Outlook spam filter works.

Step one: work out which Microsoft is filtering you

Sort the affected recipients before changing anything.

Consumer addresses (outlook.com, hotmail.com, live.com and similar) are filtered under Microsoft's Outlook.com postmaster policies. Problems there tend to be broad and domain-wide.

Business addresses on Microsoft 365 pass through Exchange Online Protection with policies each organization's administrators control. Problems there can be specific to one company. Check a recipient domain with the MX lookup: an MX host under mail.protection.outlook.com means a Microsoft 365 tenant.

If only one company is affected, skip ahead to step six after confirming authentication. If consumer addresses are affected too, work every step.

Step two: read the verdict, not the folder

"It went to junk" doesn't say why. A delivered header does. Ask a cooperative recipient at a Microsoft 365 organization to forward the original headers, or send to a Microsoft 365 mailbox you control, and paste them into the email header analyzer. Microsoft's anti-spam header documentation explains the fields:

• CAT:SPM or CAT:HSPM means spam filtering caught the message; CAT:BULK means it was classified as bulk; CAT:SPOOF or CAT:PHSH points at authentication or impersonation.
• SFV:BLK means the user blocked you; SFV:SFE means a safe sender entry let you through.
• BCL in X-Microsoft-Antispam is your bulk complaint level.
• compauth=fail in Authentication-Results, with its reason code, is Microsoft's authentication verdict.

The category chooses your branch. Spoof or phishing sends you to step three. Bulk sends you to step five. Plain spam with passing authentication usually means reputation, step four. A user block is a relationship problem no DNS record will fix.

Step three: close every authentication gap

For consumer mailboxes, Microsoft's postmaster policies require domains sending more than 5,000 emails a day to Outlook.com to pass SPF and DKIM and publish a DMARC policy of at least p=none aligned with one of them. Since 5 May 2025, the page says, non-compliant mail from those senders has gone to junk, with rejection as 550 5.7.515 possible if issues stay unresolved. Mail in junk at Outlook.com from a high-volume domain with unfinished records is the first thing to rule out.

In business tenants, look at the compauth reason code. Per Microsoft's documentation, 000 is an explicit failure against a DMARC policy of quarantine or reject, while 001 is an implicit failure: no records published, or only weak ones like SPF ~all or DMARC p=none. Publishing records is not the same as passing them.

The usual culprit is alignment. A sending platform that signs DKIM with its own domain and uses its own bounce address passes both checks for itself and neither for you. Configure custom DKIM signing with your domain, the fix Microsoft's DMARC documentation also prescribes, and verify with the email authentication checker. The same documentation recommends putting email services you don't control directly, such as bulk platforms, on a subdomain so their problems don't affect your main domain's reputation; the setup is in email subdomain.

Step four: check the reputation instruments

With authentication clean, junk placement is a reputation question, and Microsoft's reputation data is IP-based.

• If you own your sending IPs, register them in SNDS and read the daily color history and complaint levels, then enroll in JMRP so every junk report becomes a suppression. Both are explained in Microsoft SNDS.
• If you send from a shared pool, your platform holds that access. Ask it what SNDS shows for the IPs your mail uses.
• Check bounces for Microsoft's codes. The postmaster troubleshooting page lists 421 RP-001 to RP-003 as throttling on IP or domain reputation, 550 SC-004 as a block placed because of complaints, and 550 OU-001 as a policy rejection tied to Spamhaus. OU-series codes send you to the blacklist checker.
• Watch for traps and dead addresses. Repeated mail to nonexistent addresses looks like namespace mining (SC-002), and spam trap hits in SNDS mean your acquisition or list hygiene is admitting addresses no person uses.

Recovery is gradual. Cut the segments generating complaints, stop mailing people who never engage, and ramp volume back to Microsoft domains the way you would during IP warming rather than pushing through the throttle.

Step five: if Microsoft 365 is classifying you as bulk

Legitimate newsletters are bulk mail by definition, so a bulk classification is not an accusation. Placement depends on your bulk complaint level against each tenant's threshold. Microsoft documents the default threshold as 7, the Standard preset as 6 and the Strict preset as 5, and Strict quarantines bulk mail instead of junking it. As of July 2026, Microsoft also tags bulk-identified mail as Promotions, and tenants can opt to deliver bulk mail below the threshold to a Promotions folder rather than the inbox.

You can't change a tenant's threshold. You can change the complaints behind your BCL: send only to people who asked, make unsubscribing easier than reporting (a working one-click unsubscribe header plus a visible link), honor opt-outs quickly, and keep frequency within what subscribers signed up for. The stream-level diagnosis for campaign mail is in marketing emails going to spam.

Step six: causes specific to one organization

When only one company junks or quarantines you, its own configuration is the likely cause: a Strict preset policy, a block entry an administrator created, or an earlier message from your domain that users reported. Those settings are theirs, not Microsoft's.

The workable path runs through a contact at that company. Their administrators can check message trace, see which policy acted, and report your mail to Microsoft as a false positive through the Defender portal's submissions process, the route Microsoft documents for legitimate mail that was filtered. For mail recipients expect, such as receipts, account notices and replies to their own requests, asking them to add your address to Safe Senders is legitimate, because Microsoft says Safe Senders entries are never treated as junk. Don't ask for broader allow entries as a long-term fix; Microsoft warns that allowed-sender entries bypass most protection and are best kept temporary.

What will not help

Outlook.com's troubleshooting page states that it does not operate an allow list that lets senders bypass junk filters, and that submitting a sender support request does not guarantee delivery. The request is worth making when you have fixed the causes and are still blocked; it is not a substitute for fixing them.

Neither is disguise. Rotating sending domains, rewriting content to dodge filters, or splitting volume across mailboxes treats the symptom Microsoft's systems are built to spot, and we don't publish evasion techniques. If your mail originates in Microsoft 365 itself, note that Exchange Online documents recipient and message rate limits and says it isn't suited to bulk mailing; the alternatives are in sending email through Microsoft 365. Our Outlook placement ranking is where measured Outlook placement for sending platforms is published as test cycles complete.

Related guides

• How the Outlook spam filter works — the filtering layers this sequence repairs
• Outlook sender requirements — Microsoft's rules, the 5.7.515 mandate and error codes
• Microsoft SNDS — per-IP filter verdicts and the JMRP feedback loop
• Why emails go to spam — the provider-neutral evidence hierarchy
• Email header analyzer — read Microsoft's verdict fields from a delivered message
• Deliverability troubleshooter — a structured walk through the same diagnosis

About this guide

Written by InboxRatio Editorial. Consumer-side requirements, the 5 May 2025 enforcement and error codes follow Microsoft's Outlook.com postmaster policies and troubleshooting pages; header fields, composite authentication reason codes, bulk complaint levels, the Promotions behavior, allow-entry cautions and DMARC handling follow Microsoft Defender for Office 365 documentation; Safe Senders behavior follows Microsoft Support; Exchange Online limits follow Microsoft's service description. Documentation was checked in September 2026 and governs if details change. No vendor sponsorship influences it.

Methodology

InboxRatio's benchmark sends real campaigns through the platforms we review to a controlled seed list and records where each message lands. This guide draws on Microsoft's documentation rather than our measurements; the protocol is in how we test and our source rules in sources.

Last updated

22 October 2026. Microsoft sender and Defender documentation reviewed quarterly.

Frequently asked questions

Why are my emails going to spam in Outlook but not Gmail? Microsoft filters on its own users' junk reports and its own policies, and each Microsoft 365 organization sets its own thresholds. A domain can have good standing at Google and weak standing at Microsoft. Read a delivered header to see Microsoft's specific verdict.

How do I stop my emails going to junk in Outlook? Confirm aligned SPF, DKIM and DMARC, check SNDS and bounce codes for reputation problems, lower complaints by mailing only engaged subscribers with easy unsubscribes, and for single-company problems work with that company's administrators.

What does CAT:BULK mean in an Outlook header? Microsoft 365 classified the message as bulk mail. Whether it lands in the inbox, junk or quarantine depends on its bulk complaint level against that organization's threshold, 7 by default and lower in the preset policies.

Can Microsoft whitelist my domain? Outlook.com says it does not operate an allow list for bypassing junk filters. Individual recipients can add you to Safe Senders, and organizations can create temporary allow entries, but lasting placement comes from authentication and reputation.

Why do emails to one company go to junk when others arrive? That organization's Microsoft 365 policies are likely stricter or contain an entry affecting you. Ask a contact there to have an administrator check message trace and, if the mail is legitimate, report it to Microsoft as a false positive.

Does error 550 5.7.515 mean my email is spam? No. It means a high-volume sending domain doesn't meet Outlook.com's authentication requirement. The fix is DNS and platform configuration, not content: aligned SPF or DKIM plus a DMARC record.

Outlook junk placement always leaves evidence: a header category, a compauth code, an SNDS color. Collect it before changing anything, fix the layer it names, and start with the email authentication checker.