Microsoft 365 Cold Emails Going to Spam Even with SPF, DKIM, DMARC
Authentication is green. But Outlook is still burying your cold emails in Junk. Here's why Microsoft filters differently — and what to fix.
Your SPF, DKIM, and DMARC all pass. You verified it in message headers. But your cold emails are landing in the Junk folder on Outlook.com and Microsoft 365 accounts. Gmail might be fine. Yahoo might be fine. But Microsoft is filtering you to spam and you can't figure out why.
Why This Happens
Microsoft uses SmartScreen filtering and their own sender reputation system that weighs factors differently than Gmail. Microsoft puts more emphasis on sender reputation at the IP level, and their filters are known for being more aggressive with cold outreach patterns.
Here's why authentication alone doesn't solve Microsoft deliverability:
- Microsoft's filtering gives heavy weight to IP reputation. If your sending IP has a poor reputation in Microsoft's system, authentication won't override that.
- Outlook applies more aggressive content-based filtering for cold outreach patterns. Messages that look like unsolicited commercial email face higher scrutiny even from authenticated senders.
- Microsoft tracks sender behavior patterns independently from Gmail and Yahoo. Your reputation with Microsoft is built separately — many cold email operators monitor Gmail but completely ignore Microsoft, letting Outlook deliverability degrade unnoticed.
Step-by-Step Diagnosis
Check message headers on a test email sent to an Outlook.com account. Confirm SPF, DKIM, and DMARC all pass. If any fail, fix that first using the SPF checker, DKIM checker, and DMARC lookup.
Check your sending IP reputation with Microsoft's SNDS tool (sendersupport.olc.protection.outlook.com). Register your IPs — this will tell you how Microsoft views your sending IP.
Check for Outlook-specific blocklists. Microsoft maintains its own blocklist separate from common third-party lists. If your IP is on Microsoft's blocklist, you need to submit a delist request through their support page.
Run a placement test from each inbox to Outlook.com accounts you control. Check if some inboxes perform better than others — if they're on different IPs, this will help isolate IP-specific issues.
Check your DMARC alignment with the DMARC lookup. Microsoft's enforcement requires that the From domain aligns with either the SPF domain or the DKIM domain. If you pass SPF and DKIM individually but alignment fails, DMARC effectively fails from Microsoft's perspective.
The Fix Path
If IP reputation is the issue, you need to either improve it or change IPs. Reducing volume, increasing engagement rates, and avoiding complaints can improve IP reputation over time. If you're on a shared IP with poor reputation, you may need to request a different IP from your sending provider.
If content is triggering Outlook filters, simplify. Plain text performs better on Microsoft than HTML templates. Minimize links. Avoid URL shorteners. Run your links through the link reputation checker to confirm nothing is flagged.
Register with SNDS and JMRP (Junk Mail Reporting Program) to get feedback from Microsoft about how your emails are being received — this is the Outlook equivalent of Gmail Postmaster Tools and is essential for monitoring.
When to Replace Instead of Repair
If IP reputation is persistently poor on a shared IP, the fastest fix is moving to a different IP — this might mean changing outreach tools, requesting a dedicated IP, or switching sending infrastructure.
If the issue is domain reputation with Microsoft specifically, the same recovery principles apply as with Gmail: reduce volume, generate positive engagement, and wait 2–4 weeks. For agencies managing client campaigns that target companies using Microsoft 365, rotating in prewarmed inboxes from WarmInboxes that have established positive sending patterns to Outlook recipients can bridge the gap while you diagnose and fix the underlying issue.
Mistakes That Make This Worse
- Only monitoring Gmail Postmaster Tools and ignoring Microsoft SNDS
- Assuming that passing authentication is enough for Outlook
- Not testing separately against Outlook.com accounts before launching campaigns
- Using HTML-heavy templates to Microsoft recipients
- Not registering for JMRP to receive Microsoft complaint feedback
Run the checks first
Before replacing anything, run a free inbox placement test. You might find the issue is DNS, not the domain — and save yourself a week of unnecessary work.