Microsoft’s postmaster tooling covers Outlook.com, Hotmail, Live.com, and MSN inboxes through two paired programs: SNDS (Smart Network Data Services) for IP reputation and volume data, and JMRP (Junk Mail Reporting Program) for feedback loop complaints. Both migrated to a new Substrate-based portal on June 8, 2026 with substantial operational changes: a REST API with OAuth 2.0, 30-day expiry on automated access URLs, and privacy-trimmed JMRP reports (headers only, no full message body). This guide covers the post-migration setup, what changed, what stayed, and how SNDS fits alongside Google Postmaster and Yahoo Sender Hub in a full monitoring stack.
What is new in 2026
- June 8, 2026: SNDS migrated from sendersupport.olc.protection.outlook.com/snds/ to a Substrate-based portal. The old URL redirects temporarily.
- June 22, 2026: automated access URLs beginning with the old path are deprecated. Any scheduled CSV download referencing the old host will fail.
- July 22, 2026: spam trap hit counts removed from the Data Report as part of anti-abuse hardening.
- REST API with OAuth 2.0 is now the recommended programmatic access, with optional date and IPv4 filtering.
- JMRP is now ARF-standardized and privacy-trimmed: headers only, no full message body; sample downloads discontinued.
- JMRP feeds not linked to an SNDS account with current network access were removed at migration.
The June 2026 migration and what it changed
Microsoft moved SNDS and JMRP out of the legacy sendersupport portal on June 8, 2026, after roughly two decades on that address. The change is not cosmetic. Four things moved at once: the portal URL, the report access model (now REST API-first), the JMRP data format (ARF-standardized, header-only), and the account link requirement (JMRP feeds must be tied to an SNDS account).
| Area | Before June 8, 2026 | After June 8, 2026 |
|---|---|---|
| Portal URL | sendersupport.olc.protection.outlook.com/snds/ | Substrate-based portal (redirect active during transition) |
| Login | Microsoft Account (classic) | Microsoft Account with OAuth-based session behavior |
| Automated report access | Rotating CSV link, long-lived | Automated URLs expire after 30 days; REST API is the long-term path |
| Programmatic access | Not officially supported | REST API with OAuth 2.0, optional date and IPv4 filters |
| JMRP report format | Full message body sometimes included | ARF-standardized, header-only, sample downloads discontinued |
| JMRP feed linkage | Standalone feeds allowed | Must be linked to an SNDS account with current network access |
| Spam trap counts | Included in Data Report | Removed July 22, 2026 as anti-abuse hardening |
Migration action needed: replace any automated access URL that begins with the old SNDS path before June 22, 2026 (the deprecation deadline). Confirm each SNDS account still has approved network access to its responsible IP ranges. Confirm JMRP feeds are linked and not from the pre-migration standalone-feed era. Re-create any JMRP feed that went silent at migration.
What SNDS shows: IP reputation data
SNDS is IP-focused. Unlike Google Postmaster (domain-focused) or Yahoo Sender Hub (DKIM-domain focused), Microsoft attributes reputation to the sending IP. If you send from a dedicated IP or a small pool you control, SNDS is where you monitor how Microsoft sees each IP.
Per authorized IP, the current SNDS Data Report exposes:
- Message volume delivered to Microsoft consumer inboxes.
- Complaint activity (percentage of users marking as junk).
- Traffic patterns and RCPT counts.
- Filter result distribution: green (good), yellow (caution), red (poor).
- Trap activity, until July 22, 2026, when trap hits are removed from the report.
The IP Status Report is a separate view that summarizes the current filter color per IP without the daily breakdown. It is what most senders check first when Outlook.com placement drops.
SNDS red or yellow is not always a block: filter results are inputs, not verdicts. An IP flagged yellow can still deliver acceptably to inbox depending on other signals (authentication, complaint rate, engagement patterns). Treat the color as a trigger to investigate, not a diagnosis.
The Junk Mail Reporting Program (JMRP)
JMRP is Microsoft’s feedback loop: when an Outlook.com, Hotmail, Live.com, or MSN user marks your mail as junk, Microsoft sends you an ARF-formatted report. Post-migration, the format is standardized and stripped: header portions of the original message plus the ARF metadata, no full body, no sample downloads.
How JMRP delivery works in 2026
- Reports arrive as ARF (RFC 5965) at the address you configure per network in SNDS.
- One report per user complaint, delivered in near real time.
- Only complaints from mail sent by an IP authorized under your SNDS account trigger reports for that account.
- Any JMRP feed that was not linked to an active SNDS account with current network access was removed at migration; re-create it from your SNDS profile.
What to do with each report
Immediately suppress the complainant from your program, tag the campaign or IP for review, and pipe the ARF into the same complaint pipeline you use for Yahoo CFL and Google Feedback-ID data. See the FBL and ARF parsing guide for cross-provider ARF handling and Python parsing code.
JMRP silence is not a good sign: if reports stop after the migration, the most likely cause is that the feed lost its SNDS account link. Re-verify network access, confirm the reporting address is deliverable, and re-create the feed from the SNDS Feedback Loop settings if needed.
The new REST API with OAuth 2.0
The June migration added a REST API for SNDS data, with OAuth 2.0 authentication. It is the recommended path for anyone pulling reports programmatically because it is stable (no 30-day link rotation), auditable (OAuth token lifecycle), and structured (JSON responses, not CSV parsing).
What the API exposes:
- SNDS Data Report: the daily per-IP reputation data, filterable by date and IPv4 address.
- IP Status Report: the current filter color per IP.
- Batch access across your authorized network ranges.
What it does not expose:
- JMRP complaint reports (still ARF over email delivery).
- Sample messages or full complaint content (discontinued in the privacy trim).
- Domain-level reputation (SNDS is IP-scoped by design).
Post-migration checklist
If your last SNDS check was before June 8, 2026, run through this checklist before you trust any dashboard reading Microsoft data.
How SNDS compares to Google and Yahoo
Each receiver has a different attribution model, and reading them together is the only way to get a full picture.
| Feature | Google Postmaster v2 | Yahoo Sender Hub | Microsoft SNDS and JMRP |
|---|---|---|---|
| Attribution model | Domain-based | DKIM domain-based | IP-based |
| Aggregate reputation view | Compliance Status plus Deliverability Analysis | Insights (aggregate rate) | SNDS Data Report per IP |
| Per-message complaint reports | No (aggregate Feedback-ID) | Yes (CFL ARF) | Yes (JMRP ARF, header-only since 2026) |
| Reputation grade or verdict | Deliverability Analysis (7 verdicts) | None | Filter color (green / yellow / red) |
| Public API | v2 GA February 2026 | None | REST API with OAuth 2.0 (June 2026) |
| Setup gate | DNS TXT verification | DKIM domain verification | IP network authorization |
| Best for | Domain-level reputation trends and user-intent verdict | Per-recipient complaint attribution | Per-IP filter color and volume monitoring |
Cross-receiver reading: a domain sending from a shared IP pool can hit USERS_WANT_MAIL at Google, low complaint rate at Yahoo, and yellow SNDS filter for a specific IP in the pool. All three can be true at once because they attribute at different levels. Combine them; do not pick one.
How to set up SNDS and JMRP (post-migration)
Setup is IP-first. You need to prove ownership of the sending IPs before Microsoft shows you anything.
1. Sign in at the new SNDS portal
Use a Microsoft Account (personal or work) that will own the network ranges. Note the URL of the new Substrate portal from the current documentation; do not rely on old bookmarks.
2. Request access to your IP ranges
Submit each IP range you are responsible for. Microsoft sends an authorization link to the abuse contact for that range (or the RIR-listed technical contact). Someone at that address must approve.
3. Wait for authorization
Approvals can take hours to days depending on how quickly the abuse contact processes them. Once approved, the IPs appear in your SNDS Data Report within about 24 hours if there is volume.
4. Configure the JMRP feed
From your SNDS profile, open Feedback Loop settings, add your reporting address, and enable JMRP for the authorized networks. Reports flow within a day of the first complaint.
5. Wire up the REST API (optional but recommended)
For programmatic access, register an app for OAuth 2.0, request the appropriate scope, and pull the Data Report and IP Status Report on your schedule. The API replaces the fragile 30-day CSV link workflow.
6. Renew network access before the 10-month window
Microsoft asks for periodic reattestation of network ownership. Miss the renewal and the network access expires, which silently drops your SNDS visibility and any JMRP feeds tied to it.
Microsoft and the bulk sender rules
Microsoft did not sign onto the February 2024 unified Google and Yahoo bulk sender rules with the same public announcement, but the underlying requirements (SPF, DKIM, DMARC, low complaint rate, working unsubscribe) apply operationally at Outlook.com. Complaints above roughly 0.3 percent will trigger filter downgrades regardless of which receiver you send to.
What is different at Microsoft:
- No public compliance dashboard equivalent to Google’s Compliance Status. Enforcement surfaces as filter color changes and delivery deferrals.
- Authentication failure typically produces harder rejections than Google’s flexible handling of borderline cases.
- Complaint attribution is per IP, so a bad-actor tenant in a shared pool can drag down otherwise clean sending.
Complementary tools and cross-receiver monitoring
For cross-receiver complaint reporting including ARF parsing code, see the Feedback Loops and ARF guide.
Common issues and how to fix them
JMRP feed went silent after June 8
Most common post-migration issue. The feed was standalone and lost its SNDS account link at cutover. Log in to the new SNDS portal, open Feedback Loop settings, and re-create the feed with the reporting address linked to your SNDS account and current network access.
Automated CSV link returns 404
Links expire after 30 days now. Regenerate the automated access URL from your SNDS profile. Better long-term: switch to the REST API which does not rotate.
“There was a problem saving your changes” error
Documented Microsoft-side quirk during the migration transition. Workaround: open Edit Profile, make a trivial change (any field), save, then retry creating the automated link. Microsoft has said a permanent fix is in progress.
Network access lost silently
The reattestation window runs about 10 months. If you missed a renewal reminder, your network access dropped and all JMRP feeds tied to it went dark. Re-request access from the SNDS portal; expect the same abuse-contact authorization loop as initial setup.
SNDS shows no data for an authorized IP
Either the IP is not sending volume to Microsoft consumer domains yet (volume threshold applies as at Google and Yahoo), or the network authorization has expired. Confirm with a test send and check the network access status in your profile.
JMRP report body is empty
Expected post-migration. JMRP is now ARF header-only for privacy. Parsers that expected the full message body must switch to using the header data (which still identifies the recipient and campaign via Feedback-ID or ARF metadata).
IPv6 sending not showing in the API filter
The current REST API supports IPv4 filtering. If you send from IPv6, the data is there but you cannot narrow the query by IP the same way. Pull the full dataset and filter client-side, or split queries by network range.
Five common mistakes with Microsoft SNDS and JMRP
Frequently asked questions
Is SNDS still free?
Yes. SNDS, JMRP, and the new REST API are all free. You need a Microsoft Account and proven ownership (or authorized delegation) of the sending IP ranges you want to monitor.
What does SNDS cover?
Outlook.com, Hotmail, Live.com, and MSN consumer inboxes. Microsoft 365 business tenants are handled through separate admin tooling and are not in scope for SNDS.
What is the difference between SNDS and JMRP?
SNDS is the reputation dashboard: per-IP data on volume, complaints, and filter color. JMRP is the feedback loop: individual ARF-formatted reports when a user marks a message as junk. They are paired; JMRP feeds must be linked to an SNDS account since the June 2026 migration.
Why is Microsoft IP-based when everyone else is domain-based?
Historical and infrastructural. Microsoft’s anti-abuse systems key on IP behavior for consumer mail filtering, which predates the industry shift toward domain-based reputation. Domain signals are used elsewhere in the filter but SNDS surfaces the IP view.
Can I use the REST API with a service account?
Yes, via OAuth 2.0 client credentials or delegated access depending on your setup. The API is the recommended replacement for the old CSV link workflow because it is stable, auditable, and does not require rotation.
Do I need SNDS if I already use Google Postmaster and Yahoo Sender Hub?
Yes, if you send to Microsoft consumer inboxes at any scale. Google and Yahoo tell you nothing about Outlook.com placement. SNDS is the only direct signal on how Microsoft treats your IPs.
What happens if my IP moves color from green to yellow?
Investigate immediately. Yellow does not mean blocked but it means Microsoft has seen enough complaint or trap activity to flag the IP. Correlate with JMRP complaint volume for the same window, check authentication pass rates, review any recent sending pattern change.
Where to go next
SNDS and JMRP give you a receiver-side view of Outlook.com sending health that no other receiver replicates. Combine them with Google Postmaster and Yahoo Sender Hub for a full monitoring picture.
- Google Postmaster Tools in 2026: v2 dashboards, Compliance Status, Deliverability Analysis
- Yahoo Sender Hub: CFL, Insights, and DKIM domain setup
- Feedback Loops (FBL) and ARF: signup, parsing, and suppression
- Domain reputation vs IP reputation in 2026
- IP warmup schedule that works in 2026
- Cold IP recovery playbook
Historical timeline of Microsoft SNDS and JMRP updates
- July 22, 2026: Spam trap hit counts removed from the SNDS Data Report as part of anti-abuse hardening. Trap-based alerting must move to independent signals (blocklist checks, ESP complaint metrics).
- June 22, 2026: Deprecation deadline for automated access URLs beginning with the legacy sendersupport.olc.protection.outlook.com/snds/ path. Scheduled CSV pulls referencing the old host fail after this date.
- June 8, 2026: SNDS and JMRP migrate to the new Substrate-based portal. Four operational changes ship together: REST API with OAuth 2.0 for programmatic access (optional date and IPv4 filtering), 30-day expiry on automated CSV access URLs, JMRP report format standardized to ARF header-only (no full message body, sample downloads discontinued), and mandatory linkage of JMRP feeds to an SNDS account with current network access (standalone feeds removed at cutover).
- December 2, 2025: v2beta REST API developer preview announced ahead of the June 2026 cutover, giving integrators time to migrate away from the CSV link workflow.
- February 1, 2024: Google and Yahoo unified bulk sender requirements take effect. Microsoft did not sign the joint announcement but operational alignment on SPF, DKIM, DMARC, low complaint rate, and one-click unsubscribe remained expected at Outlook.com.
- Circa 2005: Smart Network Data Services (SNDS) portal launched at sendersupport.olc.protection.outlook.com. Provides per-IP data on volume, complaints, filter color (green, yellow, red), and traffic patterns. Paired with the Junk Mail Reporting Program (JMRP), Microsoft’s ARF feedback loop for junked messages.
Pre-flight validation with SMTPing: catch disposables, role addresses, catch-alls, and spam traps before they hit Outlook.com and trigger a filter color change or JMRP complaint. Thirteen validation types, twenty-five free checks daily, no card required. Try SMTPing free.
About the Author
Alaa · LinkedIn
Email infrastructure specialist with 8+ years of hands-on experience in SMTP, deliverability, and email verification. I’ve configured and troubleshot mail systems across Postfix, Exchange, and cloud relays, managed IP reputation and warmup campaigns, and built verification pipelines processing millions of addresses. My work spans DNS authentication (SPF, DKIM, DMARC, BIMI), bounce handling, blocklist monitoring, and compliance frameworks including CAN-SPAM and GDPR. I write every article on SMTPedia to give email professionals, developers, and marketers the accurate, RFC-grounded reference they need.
About SMTPedia
SMTPedia is an independent email industry reference covering SMTP, IMAP, POP3, email deliverability, marketing platforms, DNS authentication, and email verification. Every article is researched from official provider documentation, IETF RFCs, and industry best practices. Settings and configurations are verified quarterly.
We are cited as a source by ChatGPT, Microsoft Copilot, and thousands of email professionals worldwide. Learn more about our editorial process.
