Why Cold Emails Land in Outlook Spam but Gmail Inbox (Fix It Step by Step)

Why the Split Happens (It's Not Random)

Gmail and Microsoft aren't running the same filter with different thresholds, they're running different philosophies. Gmail's verdict is dominated by domain reputation and recipient engagement. Microsoft layers SmartScreen content analysis, tenant-level policies, and its Spam Confidence Level (SCL) scoring on top, and it treats unknown senders with far more suspicion, especially mail arriving from Google's servers into Microsoft tenants.

Here's the detail most people miss, and it reframes the whole problem: Microsoft's filters are so aggressive they routinely junk genuine internal emails. Companies find their own HR announcements in the bin. Once you know that, the goal stops being "look like good marketing", Microsoft junks good marketing all day. The goal is to look like the one category Microsoft's models are trained to protect: plain, one-to-one workplace correspondence.

Step 1: Get Microsoft's Actual Verdict From the Headers

Stop guessing. Send a test to an Outlook/Microsoft 365 mailbox you control, open it (junk folder included), then View message source. Two headers tell you everything:

• •Authentication-Results, did SPF, DKIM, and DMARC pass at Microsoft's edge? Gmail passing them proves nothing; Microsoft evaluates alignment itself and is stricter about SPF alignment in particular.
• •X-Forefront-Antispam-Report, find SCL:. 0-1 = clean, 5-6 = spam-filtered, 9 = high-confidence spam. This one number tells you whether you have an authentication problem or a content/reputation problem, full walkthrough in my SCL guide.

Paste the full headers into our free Header Analyzer and it decodes the authentication verdicts and alignment for you, in plain English, without your data leaving the browser.

Step 2: Match the Sender to the Recipient (The Biggest Lever)

This is the fix that moves placement the most in our fleet: Microsoft recipients get emailed from Microsoft 365 inboxes. Google recipients get emailed from Google Workspace inboxes. Cross-provider sending, Google infrastructure into Microsoft tenants, starts every message at a trust deficit that copy can't fully overcome.

Operationally: split every list by recipient provider before the campaign exists. Our free ESP Segmentation tool reads each domain's MX records and tags it Google / Microsoft / gateway-protected in seconds. Then run two campaigns with matched sender pools. Same copy, same offer, routinely a night-and-day placement difference on the Microsoft segment.

Step 3: Strip Tracking and Links

Open-tracking pixels and click-wrapped links are classic marketing fingerprints, and Microsoft's content models weigh them heavily. We run open tracking off across our entire fleet, opens are unreliable post-Apple-MPP anyway, and the pixel costs real Outlook placement. First-touch emails should carry zero links; introduce one plain link only in later touches or after a reply. (More in my open-tracking piece.)

Step 4: Write It Like an Internal Email

Remember: Microsoft's models junk marketing-shaped mail even when it's from colleagues. So remove everything that says "campaign" and keep everything that says "colleague":

• •Plain text only. No HTML templates, no images, no signatures with logos and banners.
• •Short, lowercase-ish subjects, "quick question re: hiring" reads internal; "Boost Your Pipeline 300%!" reads like a target.
• •Under 100 words, one question, written the way you'd email a coworker you haven't met.
• •Real sender name, simple sign-off. Alex, not "Alex from GrowthCo 🚀".

subject: question re: your SDR hiring

Hi Sarah,

Saw the two SDR openings, guessing outbound volume is about to jump.

Quick question: who owns deliverability once that scales? Most teams find out in month two, the hard way.

Happy to share what we see across 200+ teams if useful.

Alex

Run every draft through the Spam Checker first, the trigger words that hurt at Gmail hurt double at Microsoft.

Step 5: Warm Slower, Send Less

Microsoft extends trust more slowly than Gmail. Senders that ramp on a Gmail-appropriate schedule regularly find Gmail fine and Outlook junked. For inboxes that will target Microsoft recipients: longer warmup, roughly half the daily cap you'd run at Gmail (think 15-20/day per inbox, not 30+), and wider spacing. Capacity math for a matched fleet is what our Inbox Planner is for.

If You're Already Junked at Volume

Placement fixes forward-looking sends; it doesn't erase a damaged identity. If a sender pool has been hammering Microsoft junk folders for weeks, rest those inboxes on warmup-only for 2-3 weeks while a fresh matched pool takes over, and re-test placement weekly with header checks. When a whole domain's been burned, the decision tree is its own topic, covered in Recover, Rest or Retire.