You passed every spam test. Gmail delivers fine. But Outlook? Junk. Every time.<\/p>\n\n\n\n
You’re not imagining it. Outlook.com inbox placement dropped to 26.77% in Q1 2025.<\/em><\/strong><\/p>\n\n\n\n That means nearly three out of four emails landed in spam or disappeared entirely.<\/p>\n\n\n\n I saw this pattern across hundreds of accounts on TrulyInbox.<\/p>\n\n\n\n After some extensive research, I found that Outlook deliverability isn’t one problem. It’s actually three.<\/p>\n\n\n\n In this Outlook deliverability guide, I’ll walk you through all three scenarios, the exact fixes for each, and the error codes you’ll hit along the way.<\/p>\n\n\n\n Disclosure:<\/strong> I built TrulyInbox<\/a>, an email warm-up platform. I’ll flag where that matters. But this guide applies regardless of which tools you use.<\/p>\n\n\n\n Here’s what we’ll cover:<\/p>\n\n\n\n Outlook deliverability depends on your scenario. Are you sending FROM M365, sending TO Outlook inboxes, or both?<\/p>\n\n\n\n Each one has different friction points.<\/p>\n\n\n\n Every scenario shares one non-negotiable baseline.<\/strong> You need SPF, DKIM, and DMARC with proper domain alignment.<\/p>\n\n\n\n Microsoft rejects non-compliant mail with 550 5.7.515 errors.<\/em><\/strong><\/p>\n\n\n\n If you’re sending FROM M365, you share IPs with thousands of other tenants.<\/p>\n\n\n\n Exchange Online caps you at 10,000 messages per day, but throttles new senders much lower.<\/p>\n\n\n\n Domain reputation carries the weight here, not IP reputation.<\/em><\/strong><\/p>\n<\/blockquote>\n\n\n\n If you’re sending TO Outlook, Microsoft runs two separate filters:<\/p>\n\n\n\n SNDS only monitors consumer domains. You’re completely blind to M365 business delivery without third-party testing tools.<\/p>\n\n\n\n Warm-up matters, but only if your network includes Microsoft inboxes. In my experience, M365 accounts take 3 to 4 weeks to reach stable inbox placement.<\/p>\n\n\n\n That’s roughly a week longer than Gmail accounts under similar conditions.<\/em><\/strong><\/p>\n\n\n\n Don’t rush reputation building with Microsoft.<\/em> Budget 4 to 8 weeks minimum.<\/p>\n\n\n\n Before diving into fixes, figure out which scenario matches your setup. This determines which sections matter most to you.<\/p>\n\n\n\n Both sides run Microsoft. That sounds like an advantage, but EOP still filters inbound mail from other M365 tenants.<\/p>\n\n\n\n You’ll deal with:<\/p>\n\n\n\n You’re on Google Workspace, custom SMTP, or another provider. You’re targeting Outlook recipients from outside the Microsoft ecosystem.<\/p>\n\n\n\n You’ll deal with:<\/p>\n\n\n\n M365 is your sending infrastructure, but your recipients use Gmail or Yahoo. Those providers evaluate mail from M365 shared IPs with varying trust levels.<\/p>\n\n\n\n You’ll deal with:<\/p>\n\n\n\n Most of what follows applies to all three scenarios. I’ll flag where a section is scenario-specific.<\/p>\n\n\n\n Authentication is the foundation.<\/p>\n\n\n\n Get this wrong, and nothing else matters.<\/p>\n\n\n\n One more thing. Your sending IP’s reverse DNS must match the HELO\/EHLO hostname.<\/p>\n\n\n\n A mismatch triggers Outlook.com rejection instantly.<\/p>\n\n\n\n Here’s the quick checklist:<\/p>\n\n\n\n For a full walkthrough, check out this guide on how to set up SPF, DKIM, and DMARC<\/a>.<\/p>\n\n\n\n Even when SPF, DKIM, and DMARC all pass individually, Microsoft reduces trust without proper alignment. Your From domain, DKIM d= domain, and Return-Path must match.<\/p>\n\n\n\n This is the number one authentication issue I see when diagnosing warm-up stalls on M365 accounts.<\/em><\/p>\n<\/blockquote>\n\n\n\n Roughly 1 in 5 senders using third-party cold email platforms have alignment mismatches they don’t know about.<\/p>\n\n\n\n When I connect a new M365 account to TrulyInbox, the platform auto-checks all three records on connection.<\/p>\n\n\n\n Roughly 20% of accounts I onboard have at least one misconfiguration. Alignment mismatches top the list every time.<\/p>\n\n\n\n This section applies to Scenarios 1 and 3.<\/p>\n\n\n\n If M365 is your sending infrastructure, these constraints shape your entire deliverability strategy.<\/p>\n\n\n\n Exchange Online caps you at 10,000 recipients per day. That sounds generous, but new senders get throttled much lower.<\/p>\n\n\n\n Expect RP-001, RP-002, and RP-003 throttle codes during your first 1 to 2 weeks. Microsoft also enforces a 30-message-per-minute rate limit on each mailbox.<\/p>\n\n\n\n For cold email, here’s what’s safe:<\/p>\n\n\n\n M365 wasn’t built for high-volume cold outreach. If you need to scale, use secondary domains and multiple mailboxes instead of pushing a single account.<\/p>\n\n\n\n Every M365 tenant sends through Microsoft’s shared IP pools. You don’t control the IP, so your domain reputation matters far more than IP reputation.<\/p>\n\n\n\n Here’s the problem. If other tenants on your IP pool are spamming, your deliverability suffers.<\/p>\n\n\n\n Your authentication passes, your content is clean, and your volume is safe. But placement stalls because the IP pool is dirty.<\/p>\n\n\n\n From what I’ve seen across hundreds of M365 warm-up campaigns, roughly 10 to 15% of warm-up stalls trace back to shared IP contamination<\/em> rather than the sender’s own behavior.<\/p>\n<\/blockquote>\n\n\n\n Before blaming your content or warm-up strategy, check your sending IP against blocklists using MXToolbox or Spamhaus.<\/p>\n\n\n\n This applies whether you’re sending to Outlook recipients or Gmail.<\/p>\n\n\n\n Start warm-up before any cold outreach. Here’s the phased protocol I follow for M365 accounts:<\/p>\n\n\n\n Safe ramp rate is a 20% increase per day, or 2 to 3 additional emails daily.<\/p>\n\n\n\n I’ve run warm-up on M365 accounts continuously since 2022. The pattern is consistent. M365 accounts take 3 to 4 weeks to stabilize, about a week longer than Google Workspace.<\/p>\n\n\n\n The shared IP variable is the main reason.<\/p>\n\n\n\n Domain reputation persists even when Microsoft rotates your shared IP. Invest in the domain, not IP workarounds.<\/p>\n\n\n\n For more detail on the ramp process, read this guide on how to warm up your email domain<\/a>.<\/p>\n\n\n\n This section applies to Scenarios 1 and 2.<\/p>\n\n\n\n Whether you send from M365 or another provider, these filters decide if your email reaches the inbox.<\/p>\n\n\n\n SmartScreen handles all consumer Microsoft addresses. That includes outlook.com, hotmail.com, and live.com.<\/p>\n\n\n\n It runs content analysis, behavioral signals, and ML models. But the real wildcard is the SRD (Sender Reputation Data) panel<\/strong>.<\/p>\n\n\n\n Microsoft selects Outlook users who vote on whether your email is spam. Those votes can override clean technical signals.<\/p>\n\n\n\n The complaint threshold sits at 0.5%. Cross it, and penalties kick in. But SRD votes amplify even lower complaint rates.<\/p>\n\n\n\n Content fingerprinting also plays a role. If your email looks like every other cold email template, SmartScreen flags it.<\/p>\n\n\n\n What works consistently:<\/p>\n\n\n\n EOP handles professional M365 domains. That’s your prospects’ company email.<\/p>\n\n\n\n It shares core technology with SmartScreen but adds tenant-level admin controls.<\/p>\n\n\n\n Each company’s M365 admin can configure custom blocklists, ATP scanning, and connection filtering policies.<\/p>\n\n\n\n This is why the same email can inbox at one company and land in junk at another. Each M365 tenant runs a different filter configuration.<\/em> There’s no single “Outlook filter” to beat.<\/p>\n\n\n\n Watch out for these EOP-specific triggers:<\/p>\n\n\n\n SNDS is Microsoft’s free reputation monitoring tool. It only covers consumer Outlook.com addresses.<\/p>\n\n\n\n Green status on SNDS does not mean you’re reaching M365 business inboxes.<\/p>\n\n\n\n I’ve seen accounts with clean green SNDS status that still landed in junk at specific M365 tenants because of organization-level EOP policies.<\/em><\/p>\n<\/blockquote>\n\n\n\n For M365 business visibility, you need third-party inbox placement testing with M365 seed inboxes.<\/strong> SNDS alone gives you an incomplete picture.<\/p>\n\n\n\n Warm-up works for Outlook.<\/p>\n\n\n\n But only when you do it right.<\/p>\n\n\n\n If your warm-up tool’s network is mostly Gmail inboxes, you’re building Gmail reputation. Not Microsoft reputation.<\/p>\n\n\n\n Reddit’s r\/coldemail threads flag this constantly.<\/p>\n\n\n\n Senders run warm-up for weeks, Gmail placement looks perfect, and Outlook still junks everything. The network composition is the problem.<\/p>\n\n\n\n Microsoft’s own guidance says maximum deliverability takes 4 to 8 weeks. From running warm-up across thousands of accounts on TrulyInbox, accounts warmed up with Microsoft inboxes in the network reach stable Outlook placement faster.<\/p>\n\n\n\n The difference isn’t subtle. It’s the gap between inbox and junk on Microsoft domains.<\/p>\n\n\n\n M365 sender (Scenarios 1 and 3):<\/strong> Use automated warm-up with both Microsoft AND Gmail inboxes in the network. Follow the phased protocol from the “Sending FROM M365” section above. Start slow, ramp to 50 warm-up emails per day by week 4, then begin cold at 20 per day.<\/p>\n\n\n\n Non-M365 sender targeting Outlook (Scenario 2):<\/strong> Same principles apply. Ensure your warm-up tool includes Microsoft-domain inboxes. If you’re on dedicated IPs, start at 2,000 per day to Microsoft recipients. Double daily until you hit throttling (RP-001\/002\/003 codes), then back off.<\/p>\n\n\n\n Transactional or onboarding senders:<\/strong> Organic volume ramp is usually sufficient if authentication is clean. New domains still need 2 to 4 weeks of gradual increase.<\/p>\n\n\n\n Peer-to-peer warm-up generates real engagement signals from actual Microsoft inboxes.<\/p>\n\n\n\n Opens, replies, and important-marks all feed Microsoft’s reputation scoring directly.<\/p>\n\n\n\n Engagement signals account for roughly 30% of your reputation score with Microsoft.<\/em> Seed list models send to controlled addresses, but they don’t generate the same signals that Microsoft’s SRD panel and reputation system weight.<\/p>\n\n\n\n TrulyInbox’s network includes both Microsoft and Gmail inboxes and connects to any SMTP provider, including M365. The platform auto-checks blocklist status and authentication on connection.<\/p>\n\n\n\n Unlimited inboxes on any paid plan means you’re not penalized for scaling.<\/p>\n\n\n\n That said, warm-up can’t fix everything. It won’t help with:<\/p>\n\n\n\n For more on the warm-up process, check out our email warm-up process<\/a> guide and the email warm-up services<\/a> roundup.<\/p>\n\n\n\n You can’t fix what you can’t measure. Microsoft gives you two free tools, and both have limitations.<\/p>\n\n\n\n SNDS (Smart Network Data Services)<\/strong> is essential for consumer Outlook.com monitoring. It shows traffic volume, complaint rate, spam trap hits, and reputation status.<\/p>\n\n\n\n Here’s how to read the status:<\/p>\n\n\n\n To set up SNDS, visit sendersupport.olc.protection.outlook.com\/snds\/, register your sending IPs, and wait 24 to 48 hours. Data appears after you send 100+ messages per day. Check it weekly.<\/p>\n\n\n\n\n
\n
TL;DR \u2014 The Outlook Deliverability Fix in 60 Seconds<\/h2>\n\n\n\n
\n
\n
Three Outlook Deliverability Scenarios (Figure Out Yours)<\/h2>\n\n\n\n
Scenario 1: M365 sender \u2192 Outlook\/M365 recipient (same ecosystem)<\/h3>\n\n\n\n
\n
Scenario 2: Non-M365 sender \u2192 Outlook\/M365 recipient (landing in Outlook from outside)<\/h3>\n\n\n\n
\n
Scenario 3: M365 sender \u2192 Non-Outlook recipient (Gmail, Yahoo, etc.)<\/h3>\n\n\n\n
\n
The Authentication Baseline<\/h2>\n\n\n\n
SPF, DKIM, and DMARC \u2014 The Microsoft-Specific Nuances<\/h3>\n\n\n\n
\n
\n
Domain Alignment \u2014 The Check Most Senders Fail<\/h3>\n\n\n\n
\n
Sending FROM M365: Limits, Shared IPs, and Reputation<\/h2>\n\n\n\n
M365 Sending Limits You’ll Hit<\/h3>\n\n\n\n
\n
The Shared IP Problem<\/h3>\n\n\n\n
\n
Building Domain Reputation on M365<\/h3>\n\n\n\n
\n
Sending TO Outlook: SmartScreen, EOP, and Why You Get Junked<\/h2>\n\n\n\n
SmartScreen (Consumer Outlook.com)<\/h3>\n\n\n\n
\n
EOP \/ Exchange Online Protection (M365 Business)<\/h3>\n\n\n\n
\n
The SNDS Blind Spot<\/h3>\n\n\n\n
\n
Warming Up for Outlook Deliverability<\/h2>\n\n\n\n
Why Gmail-Optimized Warm-Up Fails on Microsoft<\/h3>\n\n\n\n
Warm-Up by Scenario<\/h3>\n\n\n\n
How Peer-to-Peer Warm-Up Helps Microsoft Specifically<\/h3>\n\n\n\n
\n
Monitoring Your Microsoft Reputation<\/h2>\n\n\n\n
\n