# Microsoft SNDS in 2026: setup and Outlook reputation monitoring > Set up Smart Network Data Services for IPs you control, connect JMRP complaints, interpret Outlook.com evidence, and account for Microsoft's 2026 portal and trap-data changes. - **Category:** Deliverability - **Published:** August 4, 2026 - **Reading time:** 16 min read - **Author:** Maya Chen, Deliverability - **Canonical page:** [https://emailbump.com/blog/microsoft-snds-guide](https://emailbump.com/blog/microsoft-snds-guide) Microsoft Smart Network Data Services, or SNDS, gives senders reputation and traffic evidence for IP addresses sending to Outlook.com. It is an IP-owner operations portal, not a universal inbox-placement score. Use it to investigate changes in Microsoft-bound traffic, detect unusual sending, and connect complaint feedback with the applications and audiences behind an IP. > **SNDS is useful only when you control the sending IP** > > A customer on a shared email-provider pool normally cannot request SNDS access for the provider's IPs. Ask the provider to investigate with message IDs, timestamps, Outlook recipient domains, outbound IPs, and complete SMTP diagnostics. Dedicated-IP owners should register and monitor their own ranges. ## What changed in Microsoft SNDS in 2026 Microsoft launched a replacement SNDS portal in 2026. The official page, last updated July 6, says the new site replaces the older sendersupport.olc.protection.outlook.com location and that automated-access URLs using the old path were deprecated. Recreate or verify automation against the new portal rather than assuming an inherited export link still works. Microsoft also announced that trap-hit counts would no longer be included in the Data Report starting July 22, 2026. During the transition, reported trap counts can differ from earlier reports and should not be treated as exact. Do not build a health check whose success depends on a stable numeric trap field that Microsoft has retired. ### 2026 migration checklist ```text PORTAL use the current substrate.office.com SNDS destination ACCESS verify every authorized IP range and responsible account AUTOMATION replace old sendersupport automated-access URLs PROFILE save a profile update if the portal reports a link-save error TRAP DATA do not depend on exact trap-hit counts after July 22, 2026 JMRP confirm complaint destinations and processing still work OWNERSHIP remove former employees and obsolete network ranges ALERTING test stale-data and failed-download detection ``` ## What SNDS measures—and what it does not SNDS is receiver-owned evidence about IP traffic reaching the Outlook.com ecosystem. It can help show volume patterns, reputation-related signals, complaint activity through the associated Junk Email Reporting Program, and unusual behavior on IPs you administer. The exact fields available in the portal and export can change, so treat Microsoft's live labels and documentation as the contract. ### Evidence boundaries ```text SNDS CAN HELP WITH SNDS CANNOT PROVE Microsoft-observed IP traffic Gmail or Yahoo reputation change over time for an IP/range universal sender reputation unusual or unauthorized sending which campaign caused it without your logs JMRP complaint evidence inbox placement for every recipient Microsoft-specific investigation that authentication or consent is healthy Join SNDS to your own message, campaign, tenant, audience, and SMTP evidence. ``` A healthy-looking daily view is not a promise that every message reached the inbox. A negative signal is not a complete root cause. Microsoft evaluates authentication, sending behavior, complaints, recipient interaction, content, infrastructure, and other private signals. SNDS gives an IP owner useful visibility into part of that system. ## SNDS vs JMRP ### SNDS **IP traffic and reputation operations** Use it to monitor IPs you control and investigate Microsoft-specific changes. ### JMRP **Junk Email Reporting Program** Use complaint reports to identify mail Outlook.com users marked as junk and suppress appropriately. ### Your delivery ledger **Message, audience, campaign, and application ownership** Use internal IDs and provider events to connect external signals to the traffic that created them. The current SNDS portal includes JMRP management, but the programs still answer different questions. SNDS is organized around sending IP evidence. JMRP reports user complaints. A complaint should stop applicable mail to that recipient and trigger source analysis; it should not merely lower a dashboard number. ## How to request Microsoft SNDS access - Sign in to the current SNDS portal with a Microsoft account controlled by the organization—not a disposable personal identity. - Request access only to public IP addresses or CIDR ranges your organization operates and uses for outbound email. - Complete Microsoft's authorization process using an eligible contact associated with the network range. - Document the IP owner, mail platform, environment, stream, expected volume, and operational escalation contact. - Use least privilege: grant access to current deliverability and infrastructure owners and review it regularly. - After approval, verify that data appears for the actual IPs delivering to Microsoft recipients. If authorization options do not reach the correct team, first confirm WHOIS or routing ownership and the organization responsible for the IP. Cloud and email providers may own the range even when your domain appears in From. Do not attempt to claim a shared provider range; the provider is the party that can operate it and see cross-customer traffic. ## Shared pool vs dedicated IP responsibilities ### Who owns the investigation ```text SHARED PROVIDER POOL Provider: SNDS access, IP neighbors, PTR, pool routing, Microsoft escalation Customer: consent, audience, domains, authentication, content, complaint source DEDICATED IP MANAGED BY PROVIDER Provider: infrastructure, SNDS access or delegation, routing, escalation Customer: all traffic on the IP, warm-up, segmentation, list and complaint policy SELF-OPERATED IP Your team: access, security, PTR/EHLO, traffic, feedback, reputation, recovery ``` Dedicated does not mean automatically reputable. It means your traffic is primarily responsible for the history. A mostly idle IP followed by a sudden campaign can be harder for receivers to evaluate than a stable, well-managed shared pool. Use a dedicated route only when sustained volume, isolation, or contractual ownership justifies the operational work. ## Keep Microsoft delivery events attributable Separate transactional and campaign traffic, preserve message activity, and connect bounce or complaint patterns to the audience and workflow that produced them. - Message-level delivery activity - Campaign and stream context - Bounce and complaint evidence [Learn more](https://emailbump.com/signup) ## Build a daily SNDS operating view Export or review SNDS on a predictable schedule, but keep the raw Microsoft observation separate from your interpretation. Record the source date, IP, retrieval time, field version, and whether the report was complete. A missing download is not a green reputation signal; it is missing evidence. ### Join external and internal evidence ```text DATE / UTC WINDOW SNDS IP and current Microsoft indicators Microsoft accepted / deferred / rejected volume from provider logs Leading Outlook/Hotmail SMTP codes and diagnostics JMRP complaints and suppression completion Visible From, DKIM, Return-Path, PTR, and sending stream Campaigns, automations, tenants, imports, forms, and volume changes Hard bounce, unsubscribe, complaint, click, reply, and product activity Security events: leaked keys, compromised accounts, open forms, malware Owner, action, decision time, and recovery gate ``` ## How to investigate a negative SNDS change - Confirm the exact IP, UTC date, report freshness, and whether the signal changed or only the portal field changed. - Split Microsoft destinations from Gmail, Yahoo, and private domains; do not hide a receiver-specific incident in account averages. - Find the first change in accepted volume, deferrals, rejections, complaints, and audience mix. - Map every stream and tenant using the IP, including transactional retries, employee systems, and customer-generated mail. - Inspect authentication and infrastructure from real messages: SPF, DKIM, DMARC alignment, PTR, EHLO, TLS, and formatting. - Stop compromised, unsolicited, stale, or unexpectedly high-volume sources before asking Microsoft or a provider for help. - Review queued mail for usefulness and expiry so recovery does not release an obsolete backlog. A complaint or reputation incident is often concentrated in one acquisition source or automation. Account-wide rates can hide that concentration. Segment by signup form, import, partner, customer tenant, campaign, template, message purpose, recipient age, and Microsoft destination family. ## SNDS does not replace SMTP diagnostics When Microsoft rejects or defers mail, preserve the exact reply. A 4xx response normally indicates a temporary failure eligible for provider-managed bounded retry. A 5xx response is permanent for the request and should not be retried unchanged. Enhanced status codes and diagnostic text identify address, relay, policy, authentication, reputation, or configuration scope more precisely than a portal color or label. Use Microsoft's sender-support and delisting paths only after the causal condition is fixed. Delisting does not exempt future mail from normal filtering. Give support the affected IP, timestamps, message IDs, recipient domains, complete errors, traffic purpose, and the corrective action already taken. ## Monitor SNDS without creating noisy automation - Alert when a production IP disappears from expected data, not only when a reputation field worsens. - Compare against a rolling weekday-aware baseline so planned weekly volume does not look anomalous. - Alert on new IPs, new streams, unexpected volume, complaint evidence, and authentication changes together. - Keep raw exports long enough to explain a normal support window, subject to privacy and security policy. - Test portal credentials, automation links, parsing, schema changes, and alert delivery after every migration. - Review access quarterly and when employees, providers, IP ranges, or network ownership change. ## Frequently asked questions ## Is Microsoft SNDS free? Microsoft provides SNDS to eligible senders and network owners without a separate product fee. Access depends on authorization for the IP ranges you are responsible for. ## Does SNDS cover Microsoft 365 business mailboxes? SNDS is presented as Outlook.com sender reputation data. Do not assume it describes every Exchange Online tenant's independent policy. Keep SMTP outcomes segmented by destination and use tenant-specific diagnostics when business domains behave differently. ## Can I use SNDS for a shared SendGrid, SES, or other provider IP? Usually the provider owns and controls a shared range. Give the provider reproducible message and SMTP evidence. Continue using your own domain, stream, audience, bounce, and complaint data because those remain your responsibility. ## Does good SNDS data guarantee Outlook inbox placement? No. SNDS is one receiver-owned evidence source. Placement can vary by recipient and message, and Microsoft uses signals not exposed as a universal public score. ## Complete the Microsoft reputation investigation - [Check sending IP reputation](https://emailbump.com/blog/check-sending-ip-reputation) — Identify the real outbound IP and compare receiver, DNS, blocklist, and traffic evidence. - [ISP email blocking](https://emailbump.com/blog/isp-blocking-email) — Classify SMTP blocks, public listings, placement, user rules, and outbound port restrictions. - [Bounce code decoder](https://emailbump.com/tools/bounce-code-decoder) — Interpret SMTP and enhanced status codes while preserving receiver-specific text. - [Email deliverability test](https://emailbump.com/tools/email-deliverability-score) — Score message evidence, authentication, permission, structure, and operating risk. ## Sources - [Microsoft: Smart Network Data Services](https://substrate.office.com/ip-domain-management-snds/snds) - [Microsoft: Outlook.com Postmaster](https://substrate.office.com/ip-domain-management-snds/postmaster) - [Microsoft: Troubleshoot external senders](https://learn.microsoft.com/en-us/defender-office-365/external-senders-mail-flow-troubleshooting) - [Microsoft: Delist blocked senders](https://learn.microsoft.com/en-us/defender-office-365/external-senders-use-the-delist-portal-to-unblock-yourself)