Deliverability

Outlook Spam Filter: How It Works and What to Do When Emails Get Blocked

By Dean Fiacco

· Published April 27, 2026

Outlook Spam Filter: How It Works and What to Do When Emails Get Blocked

Outlook's spam filter — built on Microsoft Defender for Office 365 — works differently than Gmail's. The filtering logic, the configuration options, and the way reputation is evaluated all have Microsoft-specific mechanics. If your emails are landing in Outlook's junk folder and you're treating it the same as a Gmail deliverability problem, you'll waste time on the wrong fixes.

This guide covers how Outlook's spam filter works, how to manage it as a recipient, and what senders need to know to keep legitimate email out of junk.

How Outlook's Spam Filter Works

Outlook uses a spam confidence level (SCL) system. Every incoming email receives an SCL score from -1 to 9. The higher the score, the more likely it gets filtered as spam:

  • SCL -1: Safe senders — bypasses the spam filter entirely
  • SCL 0–4: Not spam — delivered to inbox
  • SCL 5–6: Probably spam — delivered to Junk Email folder
  • SCL 7–9: High confidence spam — filtered aggressively

The SCL is assigned by Exchange Online Protection (EOP), Microsoft's cloud filtering layer that processes all email before it reaches Outlook. EOP evaluates authentication, sender reputation via Microsoft's own database, content analysis, and message properties.

For enterprise Microsoft 365 organizations, admins can configure SCL thresholds, create custom spam filter policies, and override default behavior at the tenant level. Personal Outlook accounts have less configurability but still allow safe sender lists and junk settings.

Microsoft's Sender Reputation System

Microsoft maintains its own IP and domain reputation databases, separate from Gmail's. A domain with a clean reputation in Google Postmaster Tools can still have poor standing with Microsoft if it has historically sent high complaint volumes to Microsoft 365 users specifically.

Microsoft's reputation signals include:

  • Complaint rates from Microsoft 365 users (Junk button clicks)
  • IP reputation from Microsoft's Smart Network Data Services (SNDS)
  • Domain reputation built from send history to Microsoft addresses
  • Sending volume patterns — sudden spikes are flagged

The SNDS program (sendersupport.microsoft.com) gives senders access to their IP reputation data in Microsoft's system. If you're seeing consistent Outlook deliverability issues and you've verified authentication is correct, checking SNDS for your sending IP is the right diagnostic step.

Outlook Spam Confidence Level (SCL) Scale -1 0 1 2–4 5–6 7–9 Safe sender bypass filter Not spam → Inbox Likely spam → Junk folder High confidence spam → Filtered SCL is assigned by Exchange Online Protection before email reaches Outlook Authentication SPF · DKIM · DMARC Failure → higher SCL Sender Reputation Microsoft SNDS database Complaint history matters Content Analysis URLs · patterns · formatting Evaluated by EOP ML models
Outlook's spam confidence level system — SCL determines inbox vs. junk routing before the email ever reaches you

Managing Outlook's Spam Filter as a User

Mark Junk Email as Not Junk

In Outlook (desktop or web), right-click any email in your Junk folder and select "Mark as not junk" or "Not Junk." This moves the email to your inbox and signals to Outlook that future emails from this sender should not be filtered. In Outlook on the web (OWA), open the email in Junk and click "Not junk" at the top.

Add to Safe Senders List

Go to Settings → Mail → Junk Email in OWA, or in the desktop app: Home → Junk → Junk Email Options → Safe Senders. Add the sender's email address or entire domain (e.g., @companydomain.com) to your Safe Senders list. Emails from safe senders are assigned SCL -1 and bypass the spam filter completely.

Adjust Junk Email Filter Level

In the desktop Outlook app, go to Home → Junk → Junk Email Options. You can set the filter level to: No Automatic Filtering, Low (catch obvious spam), High (catch more but also more false positives), or Safe Lists Only (only trusted senders get through). Most users should stay on Low unless they're getting significant spam volume.

Microsoft 365 Admin Configuration

If you're a Microsoft 365 admin managing a tenant, spam filter policies live in the Microsoft Defender portal (security.microsoft.com) under Email & Collaboration → Policies & Rules → Threat Policies → Anti-spam. You can create custom policies for specific user groups, adjust SCL thresholds, configure quarantine behavior, and whitelist entire sending domains at the organizational level.

What Senders Need to Know

Authentication Is Non-Negotiable

Just like Gmail, Microsoft requires proper SPF, DKIM, and DMARC setup for reliable inbox delivery. Unlike Gmail, Microsoft has historically been slightly more lenient with authentication failures, but this is changing. DMARC compliance is increasingly expected, and the trend is toward stricter enforcement.

Outlook Inboxes Are More Common in B2B

In B2B cold outreach, you'll hit more Microsoft 365 addresses than Gmail addresses. The ratio varies by industry and company size, but for SMB-to-enterprise outreach, Microsoft 365 is often the dominant inbox provider. Getting your deliverability right for Outlook is at least as important as Gmail — often more so.

The core discipline is the same: warmed sending domains, proper DNS setup, clean list hygiene, and complaint rate monitoring. The specific signals Microsoft watches differ from Google, but the foundational work is identical. See the full deliverability guide for how to set this up correctly across both providers.

Microsoft's Complaint Rate Threshold

Microsoft watches complaint rates per sending IP. If your IP or domain is generating high complaint volumes from Microsoft 365 users — measured by Junk button clicks — your reputation in SNDS will degrade. Microsoft's threshold for flagging is similar to Google's: sustained rates above 0.3% will trigger active filtering.

Outlook Spam Diagnostic Checklist SPF record exists and passes for sending domain DKIM signature is valid and aligned with domain DMARC policy set — at minimum p=none, ideally p=quarantine or p=reject Sending IP checked in Microsoft SNDS — no red/yellow status Sending domain is warmed — not newly registered and cold
Outlook spam diagnostic — run through this before changing copy or templates

Outlook vs. Gmail Spam Filtering: Key Differences

The practical differences for senders:

Factor Gmail Outlook / M365
Reputation tool Google Postmaster Tools Microsoft SNDS
Filter system ML-based, personalized SCL-based via EOP
Auth enforcement Strict (2024 mandate) Strict, tightening
Admin control Limited for admins Extensive via Defender
B2B prevalence Moderate High (dominant in enterprise)

Frequently Asked Questions

How do I stop emails from going to Outlook's junk folder?

As a recipient: add the sender to your Safe Senders list (Settings → Mail → Junk Email → Safe Senders). As a sender: verify SPF, DKIM, and DMARC all pass, check your IP status in Microsoft SNDS, and ensure your sending domain is properly warmed before scaling volume.

What is Outlook's junk email filter level?

There are four levels in desktop Outlook: No Automatic Filtering, Low, High, and Safe Lists Only. "Low" is the default and catches obvious spam. "High" catches more but produces more false positives. Most users don't need to change from Low unless they're experiencing significant spam volume.

How does Microsoft 365 anti-spam work for businesses?

Microsoft 365 routes all inbound email through Exchange Online Protection (EOP), which assigns an SCL score to every message. Admins can configure custom anti-spam policies in the Microsoft Defender portal to adjust SCL thresholds, whitelist senders, and set quarantine behavior per user group or domain.

Why are my emails going to Outlook junk even though Gmail delivers them fine?

Gmail and Microsoft maintain separate reputation databases. A domain can have good standing with Google and poor standing with Microsoft. Check your IP and domain status in Microsoft SNDS specifically. Authentication failures, complaint history from Microsoft 365 users, or a sending IP shared with known spammers can all cause Outlook-specific deliverability issues that don't show up in Google Postmaster Tools.

Share

Get cold email tips that actually work

Join our newsletter for deliverability insights, infrastructure tips, and outreach strategies. No spam, just signal.

No spam. Unsubscribe anytime.

Ready to Scale Your Cold Email?

Get started with ScaledMail's done-for-you infrastructure

Book a Call