What are the recent changes to Microsoft SNDS 'View Data' page and API?
Matthew Whittaker
Co-founder & CTO, Suped
Published 7 Jul 2025
Updated 25 Sep 2025
6 min read
Microsoft's Smart Network Data Services (SNDS) has always been a critical tool for email senders to monitor their IP reputation and deliverability to Outlook.com users. Recently, many in the email deliverability community have noticed significant, unannounced changes to the SNDS 'View Data' page and its underlying API.
These updates have introduced both cosmetic and functional shifts, impacting how email professionals access and interpret their sending data. From altered URLs for specific IP details to the removal of essential sorting capabilities, these changes have created a ripple effect for those relying on SNDS for their daily deliverability insights.
This article delves into the specifics of what has changed, the potential implications for email marketers and system administrators, and how to navigate these new complexities to maintain optimal email performance. Understanding these adjustments is crucial for ensuring your emails continue to reach the inbox effectively.
User interface modifications and navigation challenges
One of the most immediate changes users observed was a refreshed user interface for the SNDS 'View Data' page. While some appreciated a more modern aesthetic, this visual update came with significant functional drawbacks. The previous ability to sort data by various columns, a feature critical for quick analysis, appears to have been removed.
This lack of sorting capability means that data is now displayed in an arbitrary order, often not by date, making it much harder to identify recent trends or pinpoint specific issues quickly. For senders managing multiple IP addresses, manually sifting through unsorted data can become a time-consuming and frustrating task, hindering efficient email deliverability troubleshooting.
Old SNDS 'View Data' Page
Sorting: Columns were sortable, allowing for quick analysis of data by date or other metrics.
URL structure: Consistent and often included '.aspx' extensions, which automated tools relied upon.
Data order: Typically ordered logically, often by date, for easier tracking of reputation changes.
New SNDS 'View Data' Page
Sorting: Ability to sort columns has been removed, complicating data review and analysis.
URL structure: URLs have changed, potentially breaking existing bookmarks and API integrations.
Data order: Data is often out of chronological order, leading to confusion and misinterpretation.
Another common observation is that while direct access to individual IP data via old bookmarks might still work for some, others have reported seeing data that is either not displaying or is significantly delayed. This inconsistency compounds the challenge for senders attempting to get a clear picture of their standing with Microsoft.
API and URL structure shifts
Beyond the user interface, the API endpoints for SNDS data have also undergone alterations. Specifically, the old URL format, often ending in data.aspx?key=, has been replaced by data/?key=. This change has proven particularly disruptive for those who rely on automated scripts or integrations to pull SNDS data into their own systems for reporting or analysis.
SNDS API URL changestext
Old URL: https://sendersupport.olc.protection.outlook.com/SNDS/data.aspx?key=YOUR_KEY
New URL: https://sendersupport.olc.protection.outlook.com/snds/data/?key=YOUR_KEY
The immediate consequence was a wave of 404 'Not Found' errors for tools configured to use the legacy URLs. While some IP status URLs eventually began redirecting with a 302 status, the lack of a permanent 301 redirect for the API endpoint signals a less graceful transition, requiring manual updates to existing integrations. This is a common pain point discussed in the SNDS FAQ and related support forums, underscoring the need for senders to constantly monitor such changes.
Such unannounced API changes highlight the fragility of relying solely on third-party postmaster tools. For email service providers (ESPs) or large senders with complex setups, these shifts necessitate immediate attention to avoid disruptions in deliverability reporting. It also raises questions about how Microsoft's inconsistent deliverability data impacts accurate analysis.
Inconsistencies and data display anomalies
Perhaps the most puzzling aspect of these changes has been the widespread report of inconsistencies and data display anomalies. Users have reported seeing different versions of the SNDS interface at various times, with some experiencing the new design only to find it reverted to the old one later. This A/B testing or rollback behavior suggests an ongoing, fluid deployment process at Microsoft's end.
The data itself has also been affected. Several users noted that the 'View Data' page now displays dates out of order, making it extremely difficult to track trends or diagnose recent deliverability issues. This can lead to senders struggling to understand why SNDS data is not displaying or accessible reliably.
Aspect
Observed issue
Impact
UI Version
Inconsistent display, alternating between old and new designs.
Unpredictable user experience; difficulty in consistent monitoring.
Data Ordering
Dates and other metrics are displayed out of chronological order.
Hinders timely identification of deliverability issues and trend analysis.
API access
URL changes from '.aspx' to '/', causing 404 errors for automated tools.
Requires manual updates to integrations; disrupts automated reporting workflows.
These issues collectively raise concerns about the accuracy of SNDS data and its reliability for comprehensive deliverability monitoring. When the data presented is inconsistent or poorly organized, it complicates the task of maintaining a healthy sender reputation, making it difficult to understand why Microsoft is making negative changes to sender reputation.
Implications for email deliverability monitoring
The shifting landscape of SNDS emphasizes the need for a multi-faceted approach to email deliverability. While SNDS remains an important signal, its recent instability underscores the value of combining its insights with other critical monitoring tools. Implementing and actively monitoring DMARC is paramount, as it offers a more comprehensive view of email authentication and delivery across all mailbox providers.
Enhance your deliverability strategy
While SNDS provides valuable insights for Microsoft Outlook.com recipients, a broader strategy is essential. Suped offers robust DMARC reporting with the most generous free plan, helping you gain comprehensive visibility into your email ecosystem and ensure compliance with sender requirements. This includes monitoring all your sending sources and identifying potential issues that could affect your sender reputation across all mailbox providers.
As Microsoft and other major mailbox providers like Google and Yahoo continue to evolve their policies and tools, staying informed and proactive is key. Regular checks of official documentation and community discussions are essential for adapting to changes and maintaining high deliverability rates. Relying on accurate and timely data is fundamental for managing your email program effectively in 2025 and beyond.
While SNDS can provide some insights, its recent volatility highlights the benefits of robust DMARC monitoring and reporting. A comprehensive DMARC solution like Suped gives you clear, actionable data on your email authentication results, helping you troubleshoot issues faster and protect your brand from spoofing and phishing attacks.
Views from the trenches
Best practices
Actively monitor official Microsoft channels and community forums for real-time updates on SNDS changes.
Implement a comprehensive DMARC monitoring solution like Suped to gain independent deliverability insights.
Regularly test your email delivery to various mailbox providers, including Outlook.com, using an email deliverability tester.
Maintain backups or records of critical SNDS data points if automated access becomes unreliable.
Common pitfalls
Assuming old API endpoints will continue to function without interruption, leading to broken integrations.
Relying solely on SNDS data for a complete picture of deliverability without cross-referencing other tools.
Ignoring the lack of sorting or inconsistent data ordering, which can lead to misinterpretation of trends.
Failing to update internal documentation or scripts that rely on specific SNDS URL structures.
Expert tips
Look into building a simple script to pull SNDS data periodically if manual sorting becomes too cumbersome. This can help with basic trend analysis even without advanced features.
Consider engaging with Microsoft's support channels directly regarding API stability issues, as collective feedback can help drive improvements.
Utilize internal logging of email sending metrics and recipient responses to compare against SNDS data for anomaly detection.
When encountering issues, check if the SNDS page itself is undergoing A/B testing or rollbacks, as this can explain inconsistent experiences.
Marketer view
Marketer from Email Geeks says: The SNDS 'View Data' page underwent significant changes, notably the removal of column sorting and alterations to the URLs for individual IP data.
2025-09-14 - Email Geeks
Marketer view
Marketer from Email Geeks says: Old shortcuts and bookmarks often continued to work, but the removal of the '.aspx' extension from URLs was a noticeable technical change.
2025-09-15 - Email Geeks
Navigating the evolving SNDS landscape
The recent changes to Microsoft SNDS 'View Data' page and its API underscore the dynamic nature of email deliverability monitoring. While the modernized UI is aesthetically pleasing, the removal of essential functionalities like column sorting and the instability of API endpoints present significant challenges for senders. These shifts necessitate vigilance, adaptability, and a proactive approach to managing email programs.
. This inconsistency compounds the challenge for senders attempting to get a clear picture of their standing with Microsoft.
