analyst-ng#12518 stop documenting SNDS trap hits Microsoft no longer reports - #869
Merged
Merged
Conversation
…reports Microsoft stopped including spam trap hit counts in the SNDS Data Report on 2026-07-22 and offers no replacement, so SNDS is no longer a spam trap source in the platform. Outlook spam complaints, filter results, volume and IP status are unaffected and stay documented. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for support-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Microsoft stopped including spam trap hit counts in the SNDS Data Report on 2026-07-22 and offers no replacement signal, so SNDS is no longer a spam trap source in the platform. These docs still promised customers that data. Everything else SNDS reports — filter results, send volume, complaint rate and IP status — is unaffected and stays documented.
Refs SparkPost/analyst-ng#12518. Platform change: SparkPost/analyst-ng#12519.
Changes
microsoft-snds-set-up-and-configuration.md: SNDS configuration now unlocks one additional metric (Outlook spam complaints), not two. Adds a note that Microsoft stopped reporting trap hits on July 22, 2026, so a customer who linked the feed for trap visibility can see the capability was withdrawn upstream.spam-trap-types-and-sources.md: removes SNDS from the Trap Sources list.Notes
inbox-tracker-reference-guide.mdalso mentions SNDS, deliberately left unchanged: its content covers spam verdicts and sender reputation, not trap hits.media/microsoft_snds_set_up_and_configuration/were checked and none show SNDS trap data, so no images need replacing.Note
Low Risk
Analyst help content only; no application or data-handling code changes.
Overview
Documentation now matches Microsoft’s July 22, 2026 change: SNDS no longer supplies spam trap hit counts, and the platform no longer surfaces SNDS trap data in Spam Trap Monitor.
In Microsoft SNDS - Set Up and Configuration, SNDS setup is described as unlocking one extra Dashboard metric (Outlook spam complaints), not two. A short note explains that trap hits were dropped from the SNDS Data Report with no replacement, while filter results, volume, complaint rate, and IP status remain documented.
In Spam Trap Types and Sources, SNDS is removed from the Trap Sources list so customers are not told Outlook SNDS is still a trap feed.
Reviewed by Cursor Bugbot for commit 4d6fa47. Bugbot is set up for automated code reviews on this repo. Configure here.