Suped

What is the new Microsoft SNDS URL?

Published 30 Jun 2026
Updated 2 Nov 2026
10 min read
Summarize with
Microsoft SNDS URL migration with the Microsoft logo and sender reputation icons.
Updated on 2 Nov 2026: We added network renewal guidance and clarified the SNDS migration notices and automated access checks.
The new Microsoft SNDS URL is https://substrate.office.com/ip-domain-management-snds/SNDS. The old sender support SNDS path redirects to Microsoft's Substrate-based portal, which replaced the previous sender support site.
Current Microsoft SNDS URL
https://substrate.office.com/ip-domain-management-snds/SNDS
Update bookmarks, runbooks, scripts, and internal support docs to use the new address. If your team manages sender reputation for Microsoft consumer mailboxes, keep SNDS in operational checks, but do not treat it as the only signal. It reports Microsoft's view of sending IPs; domain authentication needs a separate check.
The main risk is stale automation. A person clicking a bookmark sees the redirect and adapts. A script, saved approval link, internal wiki, or support macro can keep pointing at old infrastructure. Treat the URL change as a small migration project for every team that touches deliverability.

The new SNDS URL

Use the Substrate URL for Microsoft Smart Network Data Services access. SNDS is free and covers Microsoft consumer mailboxes, including Outlook.com, Hotmail, Live, and MSN. Microsoft's page names the service as Outlook.com Smart Network Data Services and says deliverability to Outlook.com depends on sender reputation. SNDS gives IP owners data about IP reputation, mail volume, complaint signals, recipient data, and access to the Junk Mail Reporting Program.
Keep the exact canonical URL in documentation and avoid storing redirected variants. That makes access reviews easier because analysts and automation point to the same place. It also helps when an approval email or automated access workflow behaves differently than the visible portal.

Item

Use now

Notes

Portal
Substrate SNDS
microsoft.com logoPrimary login path
Old site
Redirect only
Do not bookmark
Access
Microsoft account
IP owner approval
Data
IP level
Microsoft mailbox view
Compact reference for the SNDS migration.
Do not rely on old automated links
Microsoft's migration announcement set June 22, 2026 as the deprecation deadline for automated access URLs beginning with the old sender support SNDS path. Any workflow that still stores one of those links needs a controlled replacement through Automated Data Access in the new portal.
  1. Bookmark: Save the new Substrate URL in browser profiles and team docs.
  2. Scripts: Replace old automated access URLs instead of relying on redirects.
  3. Approvals: Recheck pending IP authorization requests after migration.

What changed in the migration

The new portal changes more than the address. The interface has a different navigation model, a search function, Microsoft account sign-in, and separate pages for data, IP status, access requests, access control, profile editing, FAQs, JMRP, and Automated Data Access. The cleaner separation helps with routine work, but migration-period data still needs context because reputation data is useful only when the account and IP scope are stable.
Check the field definition before interpreting a domain value. A P1 sender is the envelope sender (SMTP MAIL FROM), which can differ from the visible From header. Do not assume every domain field identifies the same sender.
Old portal behavior
  1. Address: The older sender support SNDS path was the common entry point.
  2. Automation: Stored access links often lived in scripts and analyst runbooks.
  3. Approval: IP authorization links were often handled through email workflows.
New portal behavior
  1. Address: The Substrate SNDS path is the current portal location.
  2. Login: Microsoft account authentication is part of the main flow.
  3. Access: Use Access Control to review network access and renewal dates.
Illustration of Microsoft SNDS portal navigation and an IP reputation data table.
Illustration of Microsoft SNDS portal navigation and an IP reputation data table.
A new URL does not make old data comparisons automatically clean. If a metric changes sharply around the migration date, separate migration effects from sending effects before changing mail strategy. A sudden color change, a larger recipient data gap, or duplicated IP ranges can be a portal artifact rather than a sending event.
Trap hit counts are no longer current data
Microsoft stopped including trap hit counts in Data Report on July 22, 2026. Treat their absence after that cutoff as expected portal behavior, not a drop to zero, and do not compare post-cutoff reports directly with earlier trap-count values.

How to use the new portal

A practical workflow is to confirm access first, verify what the portal shows for each IP range, then compare SNDS signals against bounce logs, complaint feeds, campaign volume, and authentication data. SNDS is useful because it gives Microsoft's view of your IP reputation. It does not explain every filtering decision or replace domain-level monitoring. Filter-result colors are spam-filter verdicts, not inbox placement percentages.
  1. Open: Go to the new Substrate SNDS URL and sign in with the Microsoft account used for sender reputation work.
  2. Request: Request an IP address, IP range, or ASN you control. Select an authorization address Microsoft identifies through reverse DNS or RDAP and complete email verification.
  3. Verify: Check View Data and View IP Status for the same ranges before making a reputation decision.
  4. Compare: Match SNDS changes against Microsoft bounce codes, volume, complaint rate, and authentication results.
  5. Document: Record which account owns access, which ranges are approved, and when links were refreshed.
For shared IPs, coordinate access with the provider; IP-level results include other senders using that IP.
Microsoft SNDS access steps: open the portal, sign in, request IPs, confirm ownership, and review data.
Microsoft SNDS access steps: open the portal, sign in, request IPs, confirm ownership, and review data.
What to check before trusting SNDS data
Before treating a new SNDS screen as evidence of a reputation change, check for account-level migration issues, missing ranges, duplicate ranges, stale authorization, and mismatched dates. That small check prevents noisy portal data from becoming a false incident.
  1. Dates: Confirm the newest rows cover the expected delivery window.
  2. Ranges: Confirm the account shows only IP ranges that belong in scope.
  3. Columns: Check whether the field identifies the P1 sender or another domain value.

Network access renewal and incorrect deadline emails

Network access expires 10 months after approval or migration. Renewal requires approval by an authorized network owner; submitting a request alone does not extend access.
Check the deadline inside SNDS
Microsoft warns that the first network reattestation reminder email shows an incorrect deadline. Check Access Control for the expiration date and complete renewal before it. See Microsoft's current announcement.
  1. Record the expiration date and assign someone to complete renewal before access lapses.
  2. Confirm that the network owner approved the request and that Access Control shows the renewed access.

Automated data access after the migration

Manual SNDS use and automated data access are separate workflows. Manual use starts with Microsoft account sign-in. Scripts and reporting integrations need a current link generated inside Automated Data Access. Legacy links under the old sender support path were deprecated, so a browser redirect does not prove that an automated pull still works.
  1. Open: Type the current SNDS portal URL into the browser instead of following a link in an expiry email.
  2. Verify: Sign in with the expected Microsoft account and open Automated Data Access.
  3. Replace: Generate or verify the current access link, then replace the stored secret in each authorized integration.
  4. Test: Run a controlled data pull and confirm dates and IP-range coverage before restoring the schedule.
If link creation fails
During the migration, Microsoft documented the error "There was a problem saving your changes. Please try again." when creating an automated link. The published workaround was to open Edit Profile, make a change, save the profile, and then create the link again. If the same error occurs, try that workaround before escalating.
  1. Do not retry old links: Replace them through the signed-in portal.
  2. Do not expose the link: Store it as a secret because it grants automated access to SNDS data.
  3. Do not trust email alone: Confirm any expiry notice inside the portal before changing credentials.
Record which account generated the link, which job uses it, and when the replacement was tested. Check its expiry in Automated Data Access and schedule a refresh before it expires. Alert when a scheduled pull fails or stops returning fresh data.

What to do if SNDS looks wrong

If SNDS looks wrong after the move, slow down before changing warmup, throttling, suppression, or campaign routing. Check for failed IP authorization, unexpected IP ranges, and account loading problems before treating the screen as evidence of a reputation change. Record the affected account and report dates so access problems can be investigated separately.
How to classify SNDS migration signals
Use this operational triage model before making sender reputation changes.
Normal
Act on data
Portal loads, ranges are correct, and data matches expected dates.
Review
Compare logs
Data changed sharply, but mail volume or bounces did not move.
Hold
Fix access
Approvals, ranges, or pages are clearly broken for the account.
Use evidence from more than one source. Check whether the same IPs also show Microsoft deferrals, S3150-style rejections, elevated complaint rate, bad URL reputation, or a broader blocklist (blacklist) problem. A delivery rejection still needs investigation when SNDS is green or complaint rates look normal.
SNDS data is aggregated daily, not in real time. Low-volume IPs, including those sending fewer than 100 messages in a day, sometimes have no traffic data. Check report dates before treating an empty view as a clean reputation result.
  1. Access issue: Refresh the portal session, check the approval account, and retry from the new URL.
  2. Data issue: Export or record visible rows, then compare against prior SNDS data by date.
  3. Reputation issue: Compare SNDS with complaint, bounce, authentication, and blacklist data.
  4. Microsoft issue: Use sender support when Outlook.com delivery is actively affected.
For a wider checklist, keep a separate Microsoft SNDS troubleshooting note for SNDS issues and another note for whether SNDS covers Office 365 domains. Those distinctions matter because SNDS is primarily an IP reputation view for Outlook.com consumer infrastructure, not a complete view of every Microsoft-hosted domain.

How Suped fits next to SNDS

SNDS and Suped cover different parts of the same operational problem. SNDS shows what Microsoft exposes about IP reputation for Outlook.com. Suped's email authentication platform combines DMARC reporting with blocklist monitoring to help teams investigate domain authentication alongside IP reputation. That wider view helps teams connect Microsoft-specific IP evidence with domain authentication and ongoing alerts.
Blocklist monitoring page showing domain and IP checks across blocklists with importance and status
Blocklist monitoring page showing domain and IP checks across blocklists with importance and status
Use SNDS for Microsoft-specific IP evidence. Use Suped's DMARC reports to identify sending sources with SPF or DKIM failures, then investigate those sources alongside the affected IPs in SNDS.
?

What's your domain score?

Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.

If you are investigating a Microsoft delivery issue, start with the new SNDS portal, then widen the check. Suped's domain health check helps identify authentication configuration problems during the investigation. For reputation operations across multiple IPs or domains, blocklist monitoring checks for broader blocklist (blacklist) listings that SNDS does not cover.

Views from the trenches

Best practices
Update stored SNDS URLs in runbooks, scripts, alerts, and browser bookmarks in one pass.
Compare new portal data with bounce logs before changing throttles or sender routing.
Keep IP approval ownership documented, including who can renew or remove access.
Common pitfalls
Treating a sudden color change as reputation loss without checking migration timing.
Leaving legacy automated access links in scripts after the sender support migration.
Using SNDS alone to diagnose Microsoft delivery without DMARC and blocklist evidence.
Expert tips
Capture a daily snapshot during portal changes so later comparisons have context.
Test access with a small account scope before loading very large IP inventories.
Store automated links as secrets and test replacements before restoring scheduled pulls.

Marketer view

Marketer from Email Geeks says the new SNDS URL is live, but teams should verify whether approval links and access pages work for their account before relying on the data.
2026-06-09 - Email Geeks

Marketer view

Marketer from Email Geeks says the redirected sender support URL confirms the move, but the June 2026 update was easy to miss if teams relied on old bookmarks.
2026-06-09 - Email Geeks

Frequently asked questions

The new Microsoft SNDS URL is https://substrate.office.com/ip-domain-management-snds/SNDS. Use it for current SNDS access.

The old sender support SNDS path redirects to the new Substrate portal. Update stored links instead of relying on the redirect, especially for automated data access.

Yes. The portal navigation and automated access workflow changed. Microsoft also stopped including trap hit counts in Data Report on July 22, 2026. Network access also needs periodic reattestation.

Open the current portal manually, sign in, go to Automated Data Access, generate or verify the current link, replace the stored secret, and test a controlled data pull. Check the link expiry and assign a refresh owner.

No. SNDS gives Microsoft-specific IP reputation data, but diagnosis still needs bounce logs, authentication checks, complaint data, and blocklist evidence.

Suped's product combines DMARC reporting and blocklist monitoring so teams can investigate authentication failures alongside Microsoft-specific IP data in SNDS.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing