Microsoft Postmaster Tools: What It Is and How to Use It

Microsoft's "postmaster tools" are scattered across three different programs that Microsoft does not market under a single name. This is confusing for senders who expect a unified dashboard like Google Postmaster Tools. The functionality exists; it's just split.

This guide covers all three programs, what each tells you, and how to set them up.

The Microsoft sender visibility stack

Program	What it shows	URL
SNDS	Per-IP reputation, complaint rate, trap hits, filter result, color status	sendersupport.olc.protection.outlook.com/snds/
JMRP	Complaint feedback (when recipient marks as junk)	Same portal, separate enrollment
Sender Support / Mitigation	Block diagnostics and removal requests	sendersupport.olc.protection.outlook.com/pm/mitigation.aspx

All three free. All three require registration. Combined, they give sender-side visibility into Microsoft consumer mail (Outlook.com, Hotmail, Live.com).

SNDS: the reputation dashboard

SNDS (Smart Network Data Services) is the closest Microsoft equivalent to Google Postmaster Tools — but limited to IP-level data, not domain-level.

What SNDS shows

Per sending IP, you see daily:

• Traffic data — message count, distinct recipient count
• Complaint rate — % of recipients marking as junk
• Spam trap hits — count of trap-mailed addresses
• Filter result — distribution of inbox vs junk vs blocked
• Color status — green (healthy), yellow (warning), red (critical)

The color status is the headline. If your IP is red, Microsoft is filtering most of your mail to junk or blocking it.

How to set up SNDS

1. Go to sendersupport.olc.protection.outlook.com/snds/
2. Click "Request access"
3. Create or sign in with a Microsoft account
4. Add sending IPs you want to monitor
5. Verify IP ownership via DNS TXT record at the reverse DNS, or via the SOA contact at the IP's WHOIS
6. Wait 24-48 hours for data to populate

If your IPs are managed by your ESP, the ESP may have already claimed them. Verify with the ESP before requesting.

What "color status" means

Color	Filter result	Action
Green	< 1% junk	Healthy
Yellow	1-10% junk	Investigate; trending toward problems
Red	> 10% junk	Active filtering; immediate action required

Color changes lag behind underlying issues by 1-3 days. By the time color goes from green to yellow, the cause has been active for at least a few days.

Practitioner note: SNDS color status changes daily. I track it as a time series, not a snapshot. A single day of yellow after consistent green is usually a transient anomaly. Three consecutive days of yellow means an actual reputation drift starting. I set HetrixTools-style alerts on consecutive-day color changes, not single-day events.

JMRP: the complaint feedback loop

JMRP (Junk Mail Reporting Program) sends you a copy of any message that a recipient marks as junk in Outlook.com or Hotmail. Use this to:

• Suppress the complaining recipient immediately
• Identify which campaigns generate complaints
• Detect unauthorized signups (someone signed up another person)
• Pattern-match complaint sources

How to set up JMRP

1. From SNDS portal: "Junk Mail Reporting Program" link
2. Enroll each sending IP separately
3. Provide a receiving address for complaint reports (typically [email protected] or similar)
4. Microsoft sends complaint copies to that address with redacted recipient info

Implement processing: parse incoming JMRP messages, extract the complained recipient, suppress in your ESP. Most ESPs have JMRP integration that handles this automatically — verify with your ESP.

Mitigation portal: getting unblocked

If your IP is actively blocked by Microsoft (you see 550 5.7.1 OU-002 or similar in bounces), the Mitigation portal is where to request review.

1. Go to sendersupport.olc.protection.outlook.com/pm/mitigation.aspx
2. Submit a mitigation request with:
   • Affected sending IPs
   • Description of root cause and remediation
   • Commitment to prevent recurrence
3. Microsoft reviews within 24-72 hours

Mitigation requests are reviewed by humans. Specific, evidence-backed requests with clear remediation stories are approved faster than vague requests.

Practitioner note: Microsoft is less forgiving than Spamhaus about repeated mitigation requests. Multiple requests within a short window reduce future approval probability. Fix the cause completely before submitting. The format that works: "We identified that on [date] our IP started exceeding complaint threshold due to [specific cause]. We fixed it by [specific action]. Current complaint rate is [actual number from SNDS]. We have implemented [specific monitoring/control] to prevent recurrence."

SNDS vs Google Postmaster Tools

Feature	SNDS	Google Postmaster Tools
IP-level reputation	Yes	Yes
Domain-level reputation	No	Yes
Complaint rate	Yes (per IP)	Yes (per domain)
Spam trap hits	Yes (count)	Aggregated
Authentication pass rates	Limited	Detailed
Delivery error categorization	Limited	Yes
Color-coded status	Yes	Bad/Low/Med/High
API access	Limited	No (web only)
Cost	Free	Free

Google's data is more comprehensive. Microsoft's data is more limited but still essential for senders targeting Outlook.com/Hotmail.

Setting up complete Microsoft visibility

For senders mailing significant Outlook.com/Hotmail volume:

1. Register SNDS for all sending IPs (verify each)
2. Enroll JMRP for complaint feedback on each IP
3. Bookmark mitigation portal for fast access during incidents
4. Implement automated complaint suppression from JMRP
5. Configure daily SNDS color check (via API or manual)
6. Set up alert on color change from green to yellow

Total setup time: 1-2 hours. Ongoing: 5 minutes per day for color check, automated suppression for complaints.

What you still can't see

Even with all three programs set up, Microsoft does not expose:

• Domain-level reputation (only IP)
• Per-mailbox engagement data
• Aggregate filter learning state
• Microsoft 365 tenant-side filtering data (different system)
• Apple Mail-style engagement signals from Outlook clients

For broader Microsoft sender context see Microsoft SNDS guide and Outlook spam checkers.

For corporate Microsoft 365 deliverability, the diagnostic relies more heavily on:

• SMTP response codes in delivery logs
• Microsoft Sender Support tickets for specific delivery issues
• Manual investigation of customer-side blocks

Free monitoring stack for Microsoft mail

Need	Tool	Cost
IP reputation tracking	SNDS	Free
Complaint feedback	JMRP	Free
Block diagnostics	SMTP logs + Sender Support	Free
Block mitigation	Mitigation portal	Free
Blocklist monitoring	HetrixTools	Free tier
Authentication monitoring	Mailhardener	Free tier

For comparison with Google Postmaster Tools and broader monitoring see Google Postmaster Tools guide and deliverability monitoring tools.

If you need help setting up Microsoft sender monitoring, interpreting SNDS data, or recovering from Microsoft blocks, book a consultation. I do Microsoft-side deliverability work for senders dealing with Outlook filtering issues.

Sources

• Microsoft SNDS Documentation
• Microsoft JMRP
• Microsoft Sender Mitigation Portal
• Microsoft SMTP Error Codes Reference
• M3AAWG Sender Best Common Practices
• RFC 7489 — DMARC

---

v1.0 · May 2026