Why Are My Emails Going to Junk in Outlook? Causes and Fixes (2026)

Microsoft handles email for over 400 million Outlook.com users plus millions of Microsoft 365 business accounts. When your emails consistently land in the junk folder across these platforms, it signals a problem with how Microsoft views your sending reputation or practices.

Outlook uses different filtering technology than Gmail, which means you can have excellent Gmail delivery while struggling with Microsoft. Understanding how Microsoft evaluates senders is essential for reaching this significant portion of your audience. If you are also seeing issues with Gmail placing your emails in the Promotions tab, the root causes may overlap but require different solutions.

Understanding Microsoft's Email Filtering

Microsoft uses multiple filtering layers depending on the destination:

• Outlook.com / Hotmail / Live: Consumer accounts filtered by SmartScreen technology
• Microsoft 365 (Exchange Online): Business accounts protected by Exchange Online Protection (EOP)
• Microsoft Defender for Office 365: Advanced protection layer for enterprise customers

All three share reputation data and core filtering logic, but business accounts may have additional rules configured by their IT administrators that affect delivery. Starting in May 2025, Microsoft also began enforcing explicit bulk sender requirements for high-volume senders targeting Outlook.com, bringing their approach closer to what Gmail introduced in 2024.

1. SmartScreen Reputation Issues

SmartScreen is Microsoft's proprietary filtering engine that assigns reputation scores to sending IPs and domains. Unlike Gmail's Postmaster Tools, Microsoft provides limited visibility into SmartScreen decisions, making reputation problems harder to diagnose.

Factors that damage your SmartScreen reputation:

• Junk folder reports from Outlook users — even a small number of complaints can degrade your standing quickly. Learn more about what constitutes a good spam complaint rate.
• Spam trap hits on Microsoft-controlled addresses
• High bounce rates to Microsoft domains
• Sending patterns that resemble spam campaigns
• Shared IP reputation if other senders on your IP have problems

Monitoring your Microsoft reputation

Register for Microsoft's Smart Network Data Services (SNDS) at postmaster.live.com. After verifying your sending IPs, SNDS shows:

• Daily email volume to Microsoft
• Spam complaint rates from Microsoft users
• Spam trap hits
• Filter result codes (green, yellow, or red status)

A "red" status in SNDS indicates significant reputation problems requiring immediate attention. Even "yellow" status will cause increased junk folder placement. If you are seeing elevated complaint rates, read our guide on how to reduce email spam complaints for practical steps.

2. Authentication Failures

Microsoft requires proper email authentication and is increasingly strict about enforcement. With the introduction of Microsoft's 2025 bulk sender requirements, SPF, DKIM, and DMARC are now mandatory for high-volume senders. Authentication failures reliably cause junk folder placement even for lower-volume senders.

Verifying authentication for Microsoft

Send a test email to an Outlook.com account and view the message headers. Look for the Authentication-Results header showing:

Authentication-Results: spf=pass ... dkim=pass ... dmarc=pass

If any component shows "fail" or "none," that's likely contributing to junk placement. Pay special attention to DMARC alignment — Microsoft checks whether the From domain aligns with SPF and DKIM domains. If your DMARC reports show failures from sources you do not recognize, investigate immediately as this could indicate spoofing or misconfigured third-party senders.

3. Microsoft Blocklist Inclusion

Microsoft maintains its own blocklist separate from public blacklists like Spamhaus. If your sending IP appears on Microsoft's internal blocklist, your messages may be rejected outright or consistently routed to junk.

Signs your IP is blocklisted by Microsoft:

• Bounce messages containing "550 5.7.1" or referencing blocked senders
• Red status in SNDS with trap hit indicators
• Sudden, complete failure to reach Microsoft domains

Requesting removal from Microsoft blocklist

Use Microsoft's sender support page to submit a delisting request. You'll need to:

1. Identify and fix the issue that caused the listing
2. Submit the IP address and explain the remediation steps taken
3. Wait for Microsoft to review (typically 24-48 hours)

Be honest in your delisting request. Microsoft reviews sending patterns after delisting, and repeated problems will make future delisting requests harder. For a comprehensive walkthrough of the delisting process across all major providers, see our guide on how to get removed from an email blacklist.

4. Content Triggering Spam Filters

SmartScreen analyzes email content differently than Gmail. Content that delivers fine to Gmail may trigger Microsoft's filters:

• Excessive links especially to unfamiliar or new domains
• Large images with minimal text content
• Attachment types Microsoft considers risky (.zip, .exe, macros)
• Formatting commonly associated with spam (all caps, excessive colors)
• URL shorteners which hide the true destination

Testing content before sending

Send test emails to Outlook.com accounts before large campaigns. If test messages land in junk, systematically remove content elements to identify the trigger. Start with links, then images, then text blocks. Pay close attention to any third-party tracking domains in your email — if the tracking domain has a poor reputation with Microsoft, it can drag your entire message into junk even if your sending domain is clean.

5. Low Engagement History

Microsoft tracks recipient engagement signals:

• Do users open your emails?
• Do users click links?
• Do users move your emails from junk to inbox?
• Do users mark your emails as junk?
• Do users reply to your emails?

Low positive engagement combined with any negative signals (junk reports, deletes without reading) pushes future messages toward junk. This creates a cycle where junk placement leads to lower engagement which leads to more junk placement.

Breaking the engagement cycle

Segment your Microsoft recipients by engagement. Send first to users who have recently opened or clicked, letting their positive signals improve your reputation. Gradually expand to less engaged segments as delivery improves.

Consider re-permission campaigns for Outlook subscribers who haven't engaged in months. A subscriber who explicitly confirms interest provides a strong positive signal to Microsoft. Removing chronically unengaged addresses also helps reduce your complaint rate because disengaged users are more likely to mark messages as junk when they do eventually notice them.

6. New or Low-Reputation Domain

Newly registered domains have no reputation with Microsoft. SmartScreen treats unknown senders with suspicion, often routing messages to junk until the domain builds history.

Domain age matters:

• Domains under 30 days old face significant filtering
• Domains with no sending history start at neutral reputation
• Building positive reputation takes consistent, low-volume sending over weeks

Warming a new domain for Microsoft

Start with small volumes (hundreds per day) to engaged recipients likely to open and interact with your email. Gradually increase over 4-6 weeks while monitoring SNDS status. Avoid sending to old or unengaged lists during warmup — the negative signals will outweigh any volume benefits. During this period, ensure your SPF, DKIM, and DMARC are all configured correctly before sending your first message.

Microsoft's 2025 Bulk Sender Requirements

In April 2025, Microsoft announced formal bulk sender requirements for domains sending more than 5,000 emails per day to Outlook.com consumer addresses (outlook.com, hotmail.com, live.com). These requirements mirror the approach Gmail took in 2024 and represent a fundamental shift in how Microsoft manages inbound email at scale.

The core requirements for high-volume Outlook.com senders include:

• SPF must pass for your sending domain, and your DNS records must accurately list your authorized sending IPs.
• DKIM must pass to verify message integrity and domain ownership.
• DMARC must be published at a minimum of p=none, with alignment to either SPF or DKIM.
• A functional unsubscribe mechanism must be present in marketing and bulk messages, ideally supporting one-click unsubscribe via the List-Unsubscribe header.
• Transparent sending practices including valid From and Reply-To addresses, accurate subject lines, and proper list management.
• Maintain low complaint rates by sending only to recipients who have opted in and by honoring unsubscribe requests promptly.

The practical effect of these requirements is that compliance is no longer optional for anyone sending email at scale. Senders who already comply with Gmail's bulk sender requirements will meet most of Microsoft's expectations, but you should still verify that your authentication passes when checked by Microsoft's infrastructure specifically, as filtering decisions and header evaluation can differ between providers.

Outlook.com vs Gmail: Why Filtering Differs

Senders frequently report strong inbox placement with Gmail but persistent junk issues with Outlook, or vice versa. This happens because Microsoft and Google evaluate senders through fundamentally different lenses, despite sharing a commitment to authentication and complaint-rate monitoring.

Reputation systems are independent

Gmail builds sender reputation primarily around domain reputation tracked in Google Postmaster Tools, weighting engagement heavily. Microsoft's SmartScreen system places more emphasis on IP reputation alongside domain reputation, and its reputation data is largely opaque — SNDS provides only high-level IP status (green, yellow, red), not the granular domain-level metrics Gmail offers.

Content evaluation priorities

Gmail tends to categorize rather than block: messages that Gmail considers promotional are often routed to the Promotions tab rather than spam. Microsoft's approach is more binary — messages either reach the inbox or land in junk, with less emphasis on categorization and more on outright blocking of anything it considers unwanted.

Microsoft is also notably stricter about link reputation. A single URL pointing to a domain with a poor SafeLinks score can push the entire message to junk, whereas Gmail typically weighs link reputation as one factor among many.

User interaction signals

Both providers use engagement data, but they weigh it differently. Gmail aggregates engagement signals broadly across all Gmail users, meaning a sender's overall engagement rate matters most. Microsoft applies engagement data more granularly at the individual mailbox level — if a specific recipient has not opened your emails recently, Microsoft is more likely to junk your messages to that individual, even if other Outlook recipients engage positively.

Factor	Gmail	Outlook / Microsoft
Primary reputation signal	Domain reputation	IP + domain reputation
Reputation visibility	Postmaster Tools (detailed)	SNDS (limited)
Low-quality mail handling	Categorization (Promotions tab)	Binary (inbox or junk)
Link sensitivity	Moderate	High (SafeLinks evaluation)
Engagement scope	Aggregate across users	Per-recipient granularity
Bulk sender threshold	5,000 messages/day	5,000 messages/day
Complaint rate limit	0.3% hard limit	Not publicly specified

Because of these differences, you should monitor your deliverability to Microsoft and Gmail separately. A clean bill of health with one provider does not guarantee good standing with the other.

Microsoft 365 Admin: Troubleshooting Junk Mail for Your Organization

If you are a Microsoft 365 administrator and external emails from legitimate senders are being marked as junk within your organization, the problem may lie in your Exchange Online Protection (EOP) configuration rather than the sender's reputation. This section covers the key admin-side checks to diagnose and resolve internal junk mail issues.

EOP (Exchange Online Protection) configuration checklist

EOP is the filtering engine for all inbound mail in Microsoft 365. Misconfigured policies are a common reason legitimate mail ends up in junk. Review the following:

• Anti-spam policy thresholds: In the Microsoft 365 Defender portal, navigate to Email & collaboration > Policies & rules > Threat policies > Anti-spam. Check that the Bulk Complaint Level (BCL) threshold is not set too aggressively. The default is 7; lowering it to 4 or 5 will catch more mail as bulk spam.
• Spam Confidence Level (SCL): Messages with SCL 5 or 6 are delivered to junk by default. SCL 7-9 are high confidence spam. Verify that your policies are not overriding these defaults in ways that catch legitimate senders.
• Connection filter policy: Confirm that known partner or vendor IPs are added to the IP Allow List if they are being incorrectly filtered. This overrides most other spam filtering for those IPs.
• Outbound spam filter: If your own organization's outbound mail is being flagged, review the outbound spam policy for sending limits and alerting thresholds.

How to check message trace in Microsoft 365 admin center

Message trace is the single most useful diagnostic tool for understanding why a specific email was junked or quarantined. To run a message trace:

1. Open the Exchange admin center (admin.exchange.microsoft.com).
2. Navigate to Mail flow > Message trace.
3. Enter the sender address, recipient address, or both. Select a date range (up to 90 days for detailed traces, or 10 days for real-time results).
4. Click Search and review the results.
5. For each message, expand the details to see transport rules matched, SCL score assigned, EOP filtering verdict, and delivery location (inbox, junk, quarantine, or blocked).

The message trace output will tell you exactly which filtering layer (spam filter, transport rule, Safe Attachments, or user-level rule) made the junk decision, allowing you to target your fix precisely.

Safe senders list and transport rules

If a legitimate external sender's mail is consistently junked despite clean authentication, you have several options:

• Organization-wide safe sender list: In the anti-spam inbound policy, add the sender's domain or email address to the "Allowed senders" list. This applies to all users in the organization.
• Mail flow rules (transport rules): Create a rule in Exchange admin center under Mail flow > Rules. Set the condition to match the sender's domain or IP, and set the action to "Set the SCL to -1" (bypass spam filtering) or "Modify the message properties > Set the spam confidence level to Bypass spam filtering." Transport rules take precedence over anti-spam policies.
• User-level safe senders: Individual users can add senders to their personal safe senders list in Outlook. This only affects that user's mailbox and does not help at the organizational level.

Anti-spam policy settings

Microsoft 365 Defender provides granular anti-spam policies. The key settings to review when diagnosing junk placement:

• Standard vs. Strict preset policies: Microsoft offers preset "Standard" and "Strict" protection policies. Strict mode uses lower thresholds and catches more mail as spam. If you recently enabled Strict mode, it may explain a sudden increase in legitimate mail going to junk.
• Safety tips: Microsoft adds safety tip banners to messages. If users see frequent "This message was identified as spam" tips on legitimate mail, your policy may need adjustment.
• Advanced spam filter (ASF) settings: ASF includes additional flags such as "SPF record: hard fail," "Conditional sender ID filtering: hard fail," and "Contains specific languages." Review each ASF setting to ensure none are overly broad.
• ZAP (Zero-hour Auto Purge): ZAP retroactively moves delivered messages to junk or quarantine if Microsoft reclassifies them after delivery. If users report that messages appear in their inbox briefly then vanish, ZAP is likely the cause.

Quarantine management

Quarantined messages never reach the user's junk folder — they are held in a separate quarantine store. Admins can manage quarantine in Microsoft 365 Defender under Email & collaboration > Review > Quarantine.

• Release quarantined messages: Select the message and click "Release" to deliver it to the intended recipient. You can also "Release and allow sender" to prevent future quarantining from that sender.
• Review quarantine policies: Determine whether end users can self-release quarantined mail, or whether admin release is required. Overly restrictive quarantine policies lead to missed legitimate emails.
• Quarantine notifications: Enable quarantine notifications so end users are alerted when messages are held. Without notifications, users may never know a legitimate email was quarantined.

Microsoft 365 vs. Outlook.com Filtering

While both use SmartScreen, there are important differences:

Microsoft 365 (Business)

• Administrators can create safe sender lists and transport rules
• Organization-wide spam policies may override SmartScreen
• Quarantine settings vary by organization
• Advanced Threat Protection may add additional filtering

If you're having issues reaching a specific company using Microsoft 365, their IT team may be able to whitelist your sending domain or adjust filtering rules. This doesn't help with broad Microsoft deliverability, but can solve targeted business communication problems.

Outlook.com (Consumer)

• Individual users can mark senders as safe, but this only affects their mailbox
• No administrative overrides available
• More reliant on SmartScreen automated decisions
• User behavior heavily influences filtering for similar senders

Troubleshooting Steps for Outlook Junk Issues

1. Check SNDS status for your sending IPs. Red or yellow status indicates reputation problems.
2. Verify authentication by examining message headers in Outlook.com. All three (SPF, DKIM, DMARC) should pass.
3. Review recent content changes to identify potential spam triggers.
4. Check for blocklist inclusion using Microsoft's tools and third-party checkers. Our guide on blacklist removal covers the process for all major lists.
5. Analyze engagement data specifically for Microsoft recipients.
6. Confirm compliance with Microsoft's bulk sender requirements if you send over 5,000 messages per day.
7. Submit a support request if issues persist after addressing obvious problems.

Microsoft's sender support team can sometimes provide specific feedback about filtering decisions, though response times vary and they don't always share detailed diagnostic information.

Long-term Microsoft Deliverability

Maintaining good standing with Microsoft requires ongoing attention:

• Monitor SNDS weekly to catch reputation changes early
• Maintain low complaint rates by making unsubscribe easy and prominent. For specific tactics, see how to reduce email spam complaints.
• Segment by engagement to send most frequently to active subscribers
• Use consistent sending patterns rather than irregular spikes
• Keep authentication current and monitor DMARC reports for failures
• Stay compliant with bulk sender rules from both Microsoft and Gmail

With Microsoft now enforcing explicit sender requirements alongside Gmail and Yahoo, the principles of good email hygiene are universal: authenticate properly, send wanted mail, maintain your list, and respond quickly when problems emerge. Senders who adopt a compliance-first mindset across all providers will spend far less time troubleshooting junk placement.