Outlook.com and Exchange Online have different filtering systems
Why Microsoft/Outlook Blacklisting Is Different
Microsoft handles email blocking differently than other providers. They don't use public blacklists like Spamhaus—instead, they maintain their own internal reputation system.
Microsoft's Email Ecosystem
| Service | Users | Filtering |
|---------|-------|-----------|
| Outlook.com/Hotmail | Consumer accounts | Microsoft SmartScreen |
| Exchange Online (M365) | Business accounts | EOP (Exchange Online Protection) |
| Outlook desktop app | Any account | Uses host server's filtering |
Why This Matters
If you're blocked by Microsoft:
Outlook.com/Hotmail recipients won't receive your emails
Your sending IP has poor reputation with Microsoft
High spam complaint rate from Outlook users
IP was previously used for spam
New IP without established reputation
Sending patterns triggered automated filters
Signs You're Blocked by Microsoft
Bounce Codes
When Microsoft blocks your email, you'll receive specific NDR (Non-Delivery Report) codes:
| Code | Meaning |
|------|---------|
| 550 5.7.1 | Your IP is on Microsoft's blocklist |
| 550 5.7.606 | Access denied, banned sending IP |
| 550 5.7.708 | Access denied, traffic not accepted |
| 421 4.7.0 | Temporary rate limiting |
Example Bounce Message
``
550 5.7.1 Service unavailable, client host [YOUR.IP.ADDRESS]
blocked using Spamhaus. To request removal from this list
see https://sender.office.com/
``
Where to Check
1. Bounce reports from your email service
2. Email logs on your server
3. SNDS dashboard (after registration)
4. Test emails to Outlook.com accounts
Quick Test
Send a test email to a personal Outlook.com or Hotmail address. If it bounces or lands in junk, you likely have a reputation problem.
Microsoft SNDS (Smart Network Data Services)
SNDS is Microsoft's free tool for monitoring your IP reputation with Outlook.com and Hotmail. You should register regardless of whether you're currently blocked.
What SNDS Shows
Spam rate — How often your emails are marked as spam
Trap hits — Emails sent to Microsoft's spam trap addresses
Sample complaints — Examples of reported spam
IP status — Green (good), yellow (caution), red (blocked)
How to Register
1. Go to sendersupport.olc.protection.outlook.com/snds/
2. Sign in with a Microsoft account
3. Click "Request Access"
4. Enter your sending IP range (CIDR notation)
5. Verify ownership via one of:
- Email to abuse@ or postmaster@ on your domain
- WHOIS verification
- Adding a DNS TXT record
6. Wait for approval (usually 24-48 hours)
Reading SNDS Data
| Status | Color | Meaning |
|--------|-------|---------|
| Good | Green | Low spam rate, healthy reputation |
| Caution | Yellow | Elevated spam signals—investigate |
| Blocked | Red | Currently blocked—take action |
IP Ranges
SNDS works per IP address. If you use multiple IPs, you need to request access for each one. Format: 192.0.2.0/24 for a range or 192.0.2.1 for a single IP.
Delisting via sender.office.com
When Microsoft blocks your IP, the official delisting process goes through their Sender Support portal.
Before You Request Removal
Fix the root cause first. Microsoft tracks repeat offenders. If you request removal without fixing the problem, you'll be blocked again—and future removals take longer.
Common causes to fix:
Compromised accounts sending spam
Poor list hygiene (high bounces/complaints)
Missing authentication (SPF, DKIM, DMARC)
Sending to old/purchased lists
Delisting Process
1. Go to sender.office.com
2. Click "Delisting" or "Troubleshoot email delivery"
3. Enter your blocked IP address
4. Complete the CAPTCHA
5. Fill in the required information:
- Your IP address
- Contact email
- Description of what caused the issue
- Steps you've taken to fix it
6. Submit the request
What to Include
Good delisting request:
> "Our IP 192.0.2.1 was sending elevated spam volume due to a compromised user account. We've:
> 1. Disabled the account and reset credentials
> 2. Enabled MFA for all users
> 3. Implemented rate limiting
> 4. Set up DMARC with p=quarantine
> We're committed to maintaining sender best practices."
Timeline
Standard requests: 24-48 hours
Repeat offenders: 1-2 weeks
Severe violations: May require extended review
If Delisting Is Denied
Wait the specified time before resubmitting
Provide more detail about remediation steps
Consider using a new IP with proper warmup
Junk Email Reporting Program (JMRP)
JMRP sends you copies of spam complaints from Outlook.com users. This helps you identify problematic emails before your reputation tanks.
How JMRP Works
When an Outlook.com user clicks "Mark as Junk" on your email:
1. Microsoft records the complaint
2. A copy of the complaint is sent to your registered email
3. You can see exactly which email and recipient triggered it
4. You can remove complainers from your list
Setting Up JMRP
1. Ensure you're registered in SNDS first
2. Go to sendersupport.olc.protection.outlook.com/snds/JMRP.aspx
3. Enter the IP addresses you want to monitor
4. Specify an email address to receive complaints
5. Submit your request
Processing JMRP Reports
Complaint emails contain:
The original email (as attachment)
Recipient who complained
Time of complaint
Your sending IP
Best practices:
Immediately unsubscribe complainers from all lists
Analyze patterns — Are complaints clustered around specific content?
Keep complaint rate under 0.3% — Microsoft's threshold
Why JMRP Matters
Without JMRP, complaints are invisible to you. By the time you notice deliverability drops, your reputation is already damaged. JMRP provides early warning.
Outlook.com vs Exchange Online
Microsoft has two email filtering systems. Understanding which one is blocking you determines your remediation approach.
Outlook.com (Consumer)
Who uses it: Personal Hotmail, Outlook.com, Live.com accounts
Filtering: SmartScreen filtering + sender reputation
Delisting: sender.office.com
Monitoring: SNDS
Exchange Online (Business/Enterprise)
Who uses it: Microsoft 365 business customers
Filtering: Exchange Online Protection (EOP) + optional Defender
Delisting: Often customer-controlled (IT admin can whitelist)
Monitoring: Admin portal (recipient's IT controls)
Key Differences
| Aspect | Outlook.com | Exchange Online |
|--------|-------------|-----------------|
| Who controls filtering | Microsoft | Microsoft + Customer IT |
| Sender can delist | Yes (sender.office.com) | Limited (Microsoft-level only) |
| Recipient can whitelist | Yes (Safe Senders) | Yes (IT admin or user) |
| Authentication requirements | SPF, DKIM, DMARC | Same + organization policies |
When Exchange Online Blocks You
If a specific company's M365 users aren't receiving your email:
1. Check if it's Microsoft-wide (test Outlook.com)
2. If only that company, their IT may have additional filters
3. Contact their IT admin to whitelist your domain
4. Provide your SPF, DKIM, and DMARC records as proof of legitimacy
Hybrid Environments
Many organizations run hybrid Exchange (on-premises + cloud). Issues might be:
Their on-prem server blocking you
Cloud filtering blocking you
Connector misconfiguration on their end
Ask the recipient to check with their IT team.
Preventing Future Microsoft Blocks
Once you're delisted, focus on maintaining good reputation with Microsoft.
Authentication (Non-Negotiable)
Microsoft now requires authentication for bulk senders. Ensure:
| Protocol | Requirement |
|----------|-------------|
| SPF | Valid record including all sending servers |
| DKIM | Enabled and aligned with From domain |
| DMARC | p=none minimum, ideally p=quarantine |
List Hygiene
Microsoft is particularly aggressive about:
Spam traps — Old recycled addresses Microsoft uses to catch spammers
Unknown users — Sending to addresses that don't exist
Complaint rates — Keep under 0.1% with Outlook users
Clean your list:
1. Remove hard bounces immediately
2. Re-engage or remove inactive subscribers (6+ months)
3. Use double opt-in for new subscribers
4. Never purchase email lists
Sending Patterns
Avoid patterns that trigger automated filters:
Sudden volume spikes — Ramp up gradually
Inconsistent sending — Maintain regular schedule
High-risk content — Avoid spam trigger words
Ongoing Monitoring
| What | Tool | Frequency |
|------|------|-----------|
| IP reputation | SNDS | Weekly |
| Spam complaints | JMRP | Daily |
| Authentication | MailRisk | Weekly |
| Bounce rates | Your ESP | Per send |
Dedicated IP vs Shared
If you send high volume (50,000+/month to Microsoft users), consider a dedicated IP:
You control your own reputation
One bad actor can't hurt you
Easier to diagnose issues
Requires proper warmup
Frequently Asked Questions
How long does Microsoft delisting take?
First-time: Usually 24-48 hours
Repeat offender: 1-2 weeks
Severe violations: Extended review, possibly weeks
I'm delisted but still going to Junk. Why?
Delisting removes the block. Reputation takes time to rebuild. Continue good practices for 2-4 weeks and your inbox placement should improve.
Can I bypass Microsoft's filters with a new IP?
Technically yes, but:
New IPs have no reputation (cold start)
You need to warm up properly
If your practices don't change, you'll be blocked again
Microsoft tracks sender patterns beyond just IP
My ESP says my IP is fine. Why is Microsoft blocking me?
Microsoft maintains their own reputation data separate from other blacklists. You can be blocked by Microsoft but not by Spamhaus, for example.
Does Microsoft use Spamhaus?
Microsoft references Spamhaus in bounce messages, but they also maintain internal blacklists. Being delisted from Spamhaus doesn't automatically delist you from Microsoft.
How do I contact Microsoft support directly?
There's no direct support line for sender issues. The process is:
1. sender.office.com for delisting
2. SNDS for reputation data
3. JMRP for complaint monitoring
For enterprise M365 issues, the recipient's IT admin can open a support ticket.
I'm using Microsoft 365 to send. Can I still get blocked?
Yes. Microsoft separates outbound filtering (your sending) from inbound reputation (how recipients see you). You can be a Microsoft customer and still have your IP blocked for sending.