Microsoft SNDS limitations: check IP ownership and data scope

Define the decision

SNDS is an infrastructure-oriented diagnostic surface. A mailbox user may not control or have access to the provider’s outbound IP data. Microsoft has also moved the service entry point, so old navigation screenshots may no longer match.

Work through the procedure

1. Identify the actual outbound IP from a failed or received message.
2. Determine which provider controls that infrastructure.
3. Use Microsoft’s current SNDS entry point and its access process where applicable.
4. If access belongs to the provider, submit a focused evidence package instead of guessing an IP reputation result.

Worked example

The following is a synthetic example for this procedure, not a customer result or performance benchmark.

User controls: mailbox credentials and domain DNS
Provider controls: outbound IP pool
Available evidence: receiving error and specific sending IP
Escalation: ask the provider to inspect its infrastructure data for that interval

Read the result

The useful limitation is clear ownership. A lack of SNDS access is not proof of good or bad reputation, and a result for one IP may not describe the entire provider pool.

Check before moving on

1. Confirm the observed IP rather than using the MX address.
2. Keep provider and campaign timestamps aligned.

Limits and next action

This guide does not promise an SNDS integration inside Zintara. Treat external infrastructure diagnostics as additional evidence, with coverage determined by Microsoft and the infrastructure owner.

Source: Microsoft: current SNDS service entry point