Microsoft SNDS

SNDS keys data to sending IP ranges. Operators who send only through shared pools see aggregate signals for those pools, not just their own mail.

Microsoft publishes color-coded filter results and complaint rates per enrolled IP. Operators use those trends to decide whether reputation or authentication needs attention first.

Microsoft Learn still requires SPF and DKIM configuration for domains that send through Microsoft 365. SNDS does not remove that requirement; it shows how Microsoft treated mail from enrolled IPs.

SNDS can show trap hits when mail hits spam-trap addresses Microsoft operates. Sudden trap growth often correlates with list hygiene problems rather than DNS authentication alone.

Microsoft's SNDS FAQ describes how to request access for IP ranges you control. Shared pool senders see pool-level data rather than per-customer isolation.

Filter results in SNDS reflect Microsoft's handling of mail from enrolled IPs. A green filter result does not override a failing SPF or DKIM check at the message layer.

SNDS keys data to sending IP addresses. Mail sent only through shared pools appears under those pools' reputation, which operators must correlate with their own sending practices.

Microsoft Learn documents SPF and DKIM setup for Microsoft 365 tenants. SNDS complements that DNS configuration with delivery telemetry, not replacement records.

Complaint rates and trap hits in SNDS are one input when deciding whether a campaign or IP range needs throttling or list hygiene changes.