Microsoft 365 Cold Emails Going to Spam Even With SPF DKIM DMARC
SPF, DKIM, and DMARC all pass. But Outlook is putting your emails in Junk. Here's why Microsoft filters differently — and what actually fixes it.
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 cannot figure out why.
Why authentication alone doesn't solve Microsoft deliverability
Microsoft joined the bulk sender enforcement game in May 2025 — Outlook.com now requires SPF, DKIM, and DMARC for senders sending 5,000 or more messages per day, with non-compliant senders moved to Junk. But even below that threshold, Microsoft has its own filtering logic that differs significantly from Gmail's.
Microsoft uses SmartScreen filtering and its own sender reputation system. This system weighs factors differently than Gmail:
- IP reputation carries more weight. If your sending IP — whether shared through an outreach tool or dedicated — has poor reputation in Microsoft's system, authentication will not 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 independently from Gmail and Yahoo. Your reputation with Microsoft is built separately. Many cold email operators monitor Gmail Postmaster Tools but completely ignore Microsoft SNDS, letting Outlook deliverability degrade unnoticed.
Step-by-step diagnosis
Step 1: Verify authentication headers
Check message headers on a test email sent to an Outlook.com account. Confirm SPF, DKIM, and DMARC all pass. Use the SPF checker, DKIM checker, and DMARC lookup.
Step 2: Check your sending IP reputation with Microsoft SNDS
Sign up at sendersupport.olc.protection.outlook.com and register your IPs. This tells you how Microsoft views your sending IP. A red or yellow status there is often the primary cause of Outlook-specific Junk placement.
Step 3: Check for Microsoft-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. Also run the blacklist checker to cover the major third-party RBLs.
Step 4: Test content separately
Send a plain text email with no links or tracking to an Outlook.com account. If it lands in inbox, your content or tracking is the trigger. If plain text also hits Junk, the problem is IP or domain reputation.
The fix path
If IP reputation is the issue, you need to either improve it or change IPs. Reducing volume to that IP, increasing engagement rates, and avoiding complaints can improve IP reputation over time. If you are on a shared IP with poor reputation, you may need to request a different IP from your sending provider or switch to a dedicated IP.
If content is triggering Outlook filters, simplify. Plain text performs better on Microsoft than HTML templates. Minimize links. Avoid URL shorteners. Keep formatting clean and simple.
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 Microsoft deliverability.
Repair or replace?
If IP reputation is the issue, the fastest fix is moving to a different IP. If domain reputation with Microsoft specifically is the issue, reduce volume, generate positive engagement, and wait for reputation to improve over 2–4 weeks.
For agencies managing client campaigns that target companies using Microsoft 365 — which is a huge percentage of B2B targets — Outlook deliverability is not optional. If your current inboxes are performing poorly on Microsoft, rotating in prewarmed inboxes from WarmInboxes that have already established positive sending patterns to Outlook recipients can bridge the gap while you diagnose and fix the underlying IP or reputation issue.
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.