Gmail gets most of the deliverability attention, but Microsoft's email ecosystem — Outlook.com, Hotmail, Live.com, and Microsoft 365 — represents a significant share of inboxes, particularly in enterprise B2B. Many SDR teams and B2B marketers discover that campaigns performing well to Gmail addresses are being blocked or junked at Microsoft inboxes.
Outlook email deliverability operates on a distinct set of signals and filtering infrastructure from Gmail. Understanding the differences is essential for any programme that sends to a significant proportion of Microsoft-managed inboxes.
How Microsoft Filters Inbound Email
Microsoft uses a multi-layer filtering system for email arriving at Outlook.com and Microsoft 365 mailboxes:
Connection Filtering
The first layer checks the sending IP against Microsoft's IP Reputation system and major blacklists. IPs with a poor reputation are throttled or rejected before any content inspection occurs. This is where many deliverability failures start — at the connection level, before the email content is even evaluated.
Anti-Spam and Content Filtering
Microsoft's Exchange Online Protection (EOP) applies content-level filters to incoming email. Spam scoring is based on content patterns, sending behaviour history, and recipient engagement signals.
User-Level Machine Learning
Microsoft 365 applies per-user, per-sender machine learning that adapts to individual user behaviour. If a recipient consistently moves your email from Junk to their inbox, Microsoft learns to route future emails to the inbox for that recipient. The reverse also applies.
Defender for Office 365
Enterprise Microsoft 365 subscriptions include Microsoft Defender, which applies additional threat intelligence filtering. Defender operates on top of EOP and is responsible for many of the false-positive filtering incidents that affect legitimate B2B senders reaching enterprise Outlook users.
Microsoft SNDS: The Postmaster Tool for Outlook
Microsoft's Smart Network Data Services (SNDS) is the equivalent of Gmail Postmaster Tools for Microsoft's email infrastructure. It provides:
IP colour rating: Green (good reputation), Yellow (caution), Red (poor reputation / blocked).
Spam complaint rates for each sending IP.
Spam trap hit counts — Microsoft operates its own spam trap network.
Data volume statistics and delivery rate by IP.
Access: sendersupport.olc.protection.outlook.com. Requires registration and IP ownership verification.
Note: SNDS operates at the IP level, not the domain level like Gmail Postmaster Tools. If you use a shared sending IP through an ESP, your SNDS data reflects all senders on that IP pool, not just your sending behaviour. Dedicated IPs provide cleaner SNDS data.
Authentication Requirements for Outlook
Microsoft's authentication requirements align closely with Google's:
SPF: Required. Microsoft checks the Return-Path domain against SPF records during delivery.
DKIM: Strongly recommended. Microsoft uses DKIM signing status as a trust signal.
DMARC: Required for senders wanting to use Microsoft's DMARC reporting. p=none satisfies the minimum; p=quarantine or p=reject provides stronger protection.
One Outlook-specific consideration: Microsoft 365 enterprise tenants frequently have custom email security policies that override standard authentication signals. A B2B email that passes SPF, DKIM, and DMARC may still be blocked by a recipient's organisation's Microsoft Defender policy if your domain or IP appears in the organisation's custom blocklist.
This is why B2B deliverability to enterprise Outlook users is harder to diagnose than deliverability to consumer inboxes — the filtering layer is partially controlled by the recipient's IT department, not Microsoft's central infrastructure.
Fixing Common Outlook Deliverability Problems
Problem: Email Goes to Junk in Outlook.com
Outlook.com junk filtering is primarily IP reputation-based. Diagnose by checking:
SNDS rating for your sending IP. Yellow or Red ratings directly cause junk folder routing.
Blacklist status at MXToolbox — Outlook.com uses several third-party blacklists in addition to its own reputation data.
Spam complaint rate. Outlook users clicking 'Report Junk' counts against your reputation.
Problem: Email Is Blocked at Microsoft 365 Corporate Inboxes
Corporate Microsoft 365 blocking is more complex. Potential causes:
The recipient organisation's IT team has added your domain or IP to their tenant-level blocklist. In this case, the only resolution is requesting that the recipient's IT administrator whitelist your sending domain.
Microsoft Defender's threat intelligence has flagged your domain based on signals from other recipients in the Microsoft tenant network. Check the NDR (bounce message) for specific error codes.
Your email content contains patterns that Defender's heuristics identify as suspicious — particularly links to domains with low trust scores or content patterns associated with phishing.
Problem: Inconsistent Delivery to Outlook Addresses
Inconsistent delivery — some Outlook recipients receive email, others do not — often reflects the difference between consumer Outlook.com filtering (IP and domain-based) and enterprise Microsoft 365 filtering (which adds tenant-level and per-user filtering layers). Diagnose by testing delivery to Outlook.com addresses specifically, then to Microsoft 365 corporate addresses in different organisations, to isolate which layer is causing the inconsistency.
Microsoft Junk Mail Reporting Program
Microsoft operates a Junk Mail Reporting Program (JMRP) and a Smart Network Data Services program. Registering for these provides:
Complaint feedback loop: Microsoft forwards spam reports (when Outlook users click 'Report Junk') back to a registered email address. This gives visibility into complaint sources and allows you to suppress complainants from future sends.
SNDS access: Required to view your IP reputation data.
Registration: Register at postmaster.live.com. This is the Microsoft equivalent of subscribing to Gmail's Complaint Feedback Loop.
B2B Outlook Deliverability: Specific Considerations
For B2B cold email programmes where many targets use Microsoft 365 corporate email:
Validate email addresses before sending email verification. Microsoft 365 corporate servers reject email to non-existent addresses with 550 errors that count as hard bounces against your domain reputation.
Warm up by sending domains carefully
Email warm-up: Cold domains sending to large volumes of Microsoft 365 corporate addresses see disproportionate junk routing compared to Gmail.
Monitor NDR codes. Microsoft 365 bounce messages contain specific error codes (550 5.7.1, 550 5.7.23, 421 4.7.0) that identify exactly which filter is rejecting your email and why.
Avoid link-heavy emails to cold Outlook contacts. Microsoft Defender checks linked URLs against threat intelligence databases — links to recently registered or low-trust domains are flagged.
Key Takeaways
Outlook email deliverability operates across three distinct layers: IP reputation at the connection level, EOP content filtering, and per-organisation Defender policies for enterprise Microsoft 365 tenants.
Microsoft SNDS is the primary tool for monitoring IP reputation with Microsoft's infrastructure. Register at postmaster.live.com.
SPF, DKIM, and DMARC are required. Enterprise Microsoft 365 filtering adds tenant-level custom policies on top of standard authentication.
Corporate Microsoft 365 deliverability problems often require the recipient's IT administrator to whitelist your sending domain — this is outside your control to fix unilaterally.
Frequently Asked Questions
Why do my emails go to Outlook junk but not Gmail spam?
Outlook.com and Gmail use different reputation scoring systems. A domain or IP can have good reputation with Gmail (which updates signals quickly based on engagement) but poor reputation with Microsoft SNDS (which can be more persistent and IP-focused). Check your SNDS rating specifically for the IPs sending to Outlook addresses.
How do I get removed from Microsoft's blocklist?
Check the bounce message NDR code to identify the specific block. For IP-based blocks, Microsoft provides a delist request portal at sender.office.com. For domain-based blocks or Defender-policy blocks, the resolution process involves contacting Microsoft's Deliverability Support team.
Does Outlook use the same authentication requirements as Gmail?
Yes, broadly — SPF, DKIM, and DMARC are required or strongly recommended for both. The primary difference is that enterprise Microsoft 365 adds an additional tenant-level filtering layer that Google does not have for Gmail accounts.
What is Microsoft 365's complaint threshold?
Microsoft does not publish a specific complaint threshold equivalent to Gmail's 0.10% target. However, monitoring SNDS data for complaint rate trends and keeping complaint rates as low as possible is the practical approach. The JMRP feedback loop provides the data needed to identify and suppress complaining recipients.
Conclusion
Outlook email deliverability requires the same foundational disciplines as Gmail deliverability — authentication, clean lists, engaged recipients, consistent sending — but with a distinct monitoring infrastructure (SNDS instead of Postmaster Tools) and an additional enterprise filtering layer that can only be resolved through recipient IT administrator whitelisting.
Register for SNDS and JMRP now if you have not already. The visibility they provide into Microsoft's view of your sending domain is the starting point for any Outlook deliverability improvement programme.
