Skip to content

The publication for web craftspeople Sunday, 22 November 2026

Email & deliverability

Microsoft SNDS: Monitoring Sending Reputation to Outlook and Hotmail

Microsoft SNDS gives free access to the data Microsoft collects on IP addresses sending to Outlook.com and Hotmail. A walkthrough of sign-up, reading the metrics, and the tool's real limits.

Microsoft SNDS : surveiller sa réputation d'envoi vers Outlook et Hotmail
Photo : panumas nikhomkhai / Pexels

As part of a serious approach to email deliverability, Google Postmaster Tools has a Microsoft counterpart: Smart Network Data Services (SNDS). The tool gives senders free access to the data Microsoft collects on their sending IP addresses to Outlook.com, Hotmail, and Live.com. Less known than its Google counterpart, it remains the only official window into what Microsoft actually thinks of a given mail flow, at a time when a significant share of B2B inboxes still sit on Outlook or Microsoft 365.

What SNDS measures, and what it doesn’t

SNDS returns, per IP address, a SmartScreen filtering indicator (the IP status), a junk-mail complaint rate from the Junk Email Reporting Program, information on messages caught by spam traps, and raw data on processed message volume. According to Microsoft’s own documentation, the tool also helps detect compromised servers, malware, or botnets sending mail without the legitimate sender noticing.

The point most third-party guides stress, and worth keeping in mind before steering deliverability on this indicator alone: SNDS status reflects Microsoft’s view of a given IP, not a guaranteed verdict on inbox placement. Two senders with the same status can see different junk-placement rates, and a green status doesn’t stop low volume from producing unreliable data, for lack of enough history to establish a reputation.

Signing up: the process in practice

Sign-up requires a Microsoft account (an Outlook.com address is enough if the company doesn’t already have one). The request is filed from the SNDS home page: list the IP ranges to monitor, add a comment for the Microsoft team if needed, then submit. Authorization is then required for each requested range, with processing taking anywhere from a few hours to several days depending on the team’s workload. Once access is granted, it stays active with no periodic reattestation to renew.

A practical habit worth adopting from the start: a dedicated address for technical monitoring, separate from day-to-day business email, makes it far easier to hand off access to another team member later without sharing a personal account.

Reading the IP status without trusting the colors alone

The dashboard assigns each IP a color. Precise definitions vary slightly from one source to another, since Microsoft doesn’t publish an official numeric threshold, but the order of magnitude commonly cited by third-party monitoring tools gives a reasonable sense of how to read it.

StatusUsual readingAction
GreenShare of mail filtered as junk by SmartScreen judged lowKeep up sending discipline, watch for complaint spikes
YellowIntermediate filtered share; some messages land in the junk folderCheck recipient engagement, tighten list targeting
RedShare of mail filtered judged high by SmartScreenPause campaigns on the affected IP, audit traffic origin before resuming

A brand-new IP almost always starts red or with no data displayed, simply because Microsoft has no history yet to base a judgment on. That’s an expected situation, not an alarm, and it’s exactly the scenario covered in the article on warming up a sending domain and IP.

Automating collection instead of checking the dashboard by hand

For a team sending from several IPs, or wanting to archive history beyond what the web interface shows, SNDS offers token-based automated access, placed in the authentication header of requests to the data feed.

GET /abuse-reports/vi.asmx/GetSendersData HTTP/1.1
Host: sendersupport.olc.protection.outlook.com
Authorization: Bearer <snds-token>
Accept: text/csv

The token is retrieved from the “Automated Data Access” page of the SNDS dashboard and entered as-is into the chosen monitoring tool, whether a dedicated deliverability service or an internal script archiving daily exports into a data warehouse. The main advantage over manual checking: keeping a usable history to correlate a status drop with a recent change in content, list, or sending provider.

A green status on SNDS doesn’t guarantee inbox placement: it’s Microsoft’s view of an IP at a given moment, not a deliverability verdict.

SNDS only covers domains managed by Microsoft (Outlook.com, Hotmail, Live.com). For enterprise Microsoft 365 inboxes, filtering also depends on rules specific to the customer’s tenant, invisible from SNDS. A green status on the tool therefore doesn’t rule out complaints targeted at a specific 365 tenant.

SNDS versus Google Postmaster Tools: complementary, not interchangeable

Both tools answer the same question, but with different data and different granularity, which is why it makes sense to keep both running rather than pick one over the other.

CriterionMicrosoft SNDSGoogle Postmaster Tools
Domains coveredOutlook.com, Hotmail, Live.comGmail and domains hosted on Google Workspace
GranularityPer IP addressPer authenticated domain (requires aligned DKIM)
Spam indicatorColor status (green/yellow/red) from SmartScreenNumeric complaint rate, by bracket
History keptVaries by data type, needs archiving for the long termUp to 30 days in the interface
Automated accessToken + CSV feedREST API with OAuth authentication

A sender watching only one of the two tools keeps a full blind spot on the other provider, which matters for an audience where Microsoft 365 remains very present alongside Google Workspace.

Diagnosing an alert with SNDS: a practical case

The most common scenario in client work: a campaign sent from a shared or dedicated IP starts generating junk-folder returns on Outlook, with nothing having changed in the SPF or DKIM configuration. The diagnostic approach generally follows three steps.

First, check the IP status over the period covering the send in question rather than today’s status, to see whether the degradation predates the campaign or was caused by it. Next, cross-reference that status with the Junk Email Reporting Program complaint rate over the same window: a simultaneous rise in both indicators points to a targeting or content issue rather than a purely technical one. Finally, if the IP is shared with other senders (common with some transactional-sending providers), check whether the degradation affects the whole pool or only the domain’s own traffic, which points toward a provider issue rather than an internal fix.

SNDS is worth cross-referencing with the other monitoring signals already in place: domain authentication via SPF, DKIM, and DMARC, and the usual causes of landing in the junk folder detailed in the article on causes of spam placement. Neither is sufficient on its own: a simultaneous drop across both signals carries more weight than a single indicator, and keeping a written record of these diagnoses, even a brief one, avoids repeating the same investigation six months later for an identical symptom.

Key takeaways

SNDS remains free, underused by small sending teams, and is the only data source Microsoft itself provides on IP reputation toward Outlook and Hotmail. Its realistic use is to watch a trend over time, not to react to a single color, and to always cross-reference it with domain authentication and actual deliverability results.

SNDS is the tool my clients usually discover after the fact, once a campaign has already landed in bulk in Outlook’s junk folder with no obvious explanation on the SPF or DKIM side. I now set it up as soon as a new sending domain goes live, alongside Google Postmaster Tools, precisely to have the history available the day something degrades — Simon Janvier.

Further reading: the official page for Microsoft Smart Network Data Services.

Read next