Suped

How to get Microsoft SNDS access when using an Email Service Provider?

Summary

Gaining direct access to Microsoft Smart Network Data Services (SNDS) when using an Email Service Provider (ESP) is generally not possible for individual customers, especially those on shared IP addresses. This is because SNDS access is fundamentally linked to the ownership and management of IP addresses, which reside with the ESP. ESPs proactively manage their IP pools within SNDS, handling registration, monitoring, and reputation maintenance to ensure optimal deliverability for all their users. Therefore, end-users typically rely on their ESP's deliverability team for SNDS-related insights and reputation management, as the data belongs to the IP owner. However, for clients utilizing a dedicated IP address from their ESP, direct SNDS access might be achievable, but it necessitates direct coordination and approval from the ESP to verify control over that specific IP. If direct access is not an option, customers should inquire if their ESP can provide relevant reports or data insights derived from their SNDS monitoring.

Key findings

  • IP Ownership Determines Access: Microsoft SNDS access is fundamentally tied to the ownership and management of IP addresses. Since Email Service Providers (ESPs) own and manage their sending IP pools, they are the primary entities granted direct access to SNDS data for those IPs, not individual customers.
  • No Direct Access for Shared IPs: Customers utilizing an ESP's shared IP addresses typically cannot gain direct SNDS access. The ESP's deliverability team is responsible for managing, monitoring, and maintaining the reputation of these shared IPs within the SNDS program.
  • ESPs Manage Reputation Proactively: Most ESPs, including major providers like Mailchimp, SendGrid, SparkPost, ActiveCampaign, HubSpot, and Postmark, proactively manage their IP reputation with services like Microsoft SNDS. This centralized management ensures optimal deliverability for their entire client base, eliminating the need for individual users to register.
  • Dedicated IP Access Is Possible: For clients using a dedicated IP address through their ESP, direct SNDS access might be possible but requires coordination and approval from the ESP. The ESP would need to verify control over the IP for the SNDS enrollment process to proceed.
  • Reliance on ESP Deliverability Teams: As an ESP customer, your deliverability depends heavily on your provider's expertise in managing their IP reputation. You rely on their internal teams to interact with SNDS and other postmaster tools, rather than gaining direct access yourself.

Key considerations

  • Consult Your ESP First: Before attempting to gain direct SNDS access, contact your Email Service Provider to understand their specific policies and capabilities regarding SNDS data and access for their clients, especially concerning shared versus dedicated IP addresses.
  • Request Reports or Insights: If direct SNDS access is not provided, ask your ESP if they can furnish deliverability reports or specific insights derived from their SNDS data to help you monitor your sending reputation and identify potential issues.
  • Distinguish IP Types: Understand that the possibility of direct SNDS access heavily depends on whether you are using your ESP's shared IP addresses or a dedicated IP. Dedicated IPs may offer a pathway to direct access, while shared IPs generally do not.
  • Understand Access Control: For instances where direct SNDS access might be granted, such as with a dedicated IP, be aware that access can be revoked by initiating a 'request reauthorization' or may expire automatically after seven days if the authorization link is not clicked.

What email marketers say

13 marketer opinions

For marketers leveraging an Email Service Provider (ESP) for their email campaigns, obtaining direct access to Microsoft's Smart Network Data Services (SNDS) is typically not an option, particularly when utilizing shared IP addresses. This limitation stems from the fact that SNDS access is inherently tied to the ownership and active management of sending IP addresses, a responsibility that lies firmly with the ESP. These providers proactively oversee their IP pools within SNDS, handling all aspects of registration, ongoing monitoring, and reputation maintenance to ensure optimal deliverability for their entire client base. Consequently, individual users generally rely on their ESP's dedicated deliverability teams for any SNDS-related insights or reputation management data. While direct access is largely unavailable for shared IP users, clients on dedicated IP addresses might have a pathway to obtaining SNDS access, though this always requires specific coordination and approval from their ESP to verify control over the allocated IP. If direct access is unfeasible, customers should inquire about receiving relevant reports or data insights that their ESP can generate from their own SNDS monitoring.

Key opinions

  • IP Ownership Governs SNDS Access: Access to Microsoft SNDS is inherently tied to the ownership and management of IP addresses. Since Email Service Providers (ESPs) own and operate their sending IP pools, they are the primary entities with direct SNDS access for those IPs, not individual customers.
  • No Direct Access for Shared IPs: For most customers using an ESP's shared IP addresses, gaining direct Microsoft SNDS access is generally not possible. The ESP's deliverability team is responsible for managing, monitoring, and maintaining the reputation of these shared IPs through SNDS.
  • ESPs Proactively Manage Deliverability: Leading ESPs, including Mailchimp, SparkPost, ActiveCampaign, HubSpot, and Postmark, proactively manage their IP reputation with services like Microsoft SNDS. This centralized management ensures optimal deliverability for their entire client base, negating the need for individual user registration.
  • Dedicated IP Access Requires ESP Collaboration: Clients with a dedicated IP address through their ESP might be able to secure direct SNDS access for that specific IP. However, this always requires direct coordination and approval from the ESP to verify ownership or control over the IP address.
  • Customer Reliance on ESP Expertise: As an ESP customer, your email deliverability heavily relies on your provider's specialized deliverability team, who handle interactions with SNDS and other postmaster tools on your behalf, rather than you gaining direct access.
  • SNDS Authorization Linked to PTR Records: The SNDS authorization process is linked to the IP's PTR (reverse-DNS) record. If using an ESP, they must identify and approve the relevant authorization email address to grant any form of SNDS access.

Key considerations

  • Engage Your ESP Directly: Before pursuing any form of Microsoft SNDS access, it is crucial to communicate with your Email Service Provider to understand their specific policies regarding SNDS data sharing and client access, especially given the distinction between shared and dedicated IP addresses.
  • Seek Reports, Not Just Access: If direct SNDS access is not feasible, request if your ESP can provide specific deliverability reports or insights derived from their own SNDS monitoring. This can still offer valuable information on your sending reputation and potential issues.
  • Differentiate IP Types: Recognize that your ability to potentially gain direct SNDS access is heavily contingent on whether you are using your ESP's shared IP addresses, which typically do not allow direct client access, or a dedicated IP, where a pathway might exist with ESP collaboration.
  • Understand the Authorization Flow: For instances where direct SNDS access might be granted, particularly with a dedicated IP, be aware that the authorization process involves your ESP confirming control over the IP via a PTR-related email address, and that access can be revoked or expires after seven days if the link is not clicked.

Marketer view

Marketer from Email Geeks explains that the SNDS authorization email addresses are related to the IP's PTR (reverse-DNS) record. He clarifies that if you use an ESP, you typically cannot gain direct SNDS access this way and should request it from your ESP, as it depends on who manages the IP space.

31 Mar 2022 - Email Geeks

Marketer view

Marketer from Email Geeks shares a four-step algorithm for gaining SNDS access through an ESP: talk to your ESP, submit the form, ESP confirms, then access. He also clarifies that SNDS access can be revoked by initiating a "request reauthorization" in the Access Control section, or it expires automatically after 7 days if the link isn't clicked.

12 Oct 2023 - Email Geeks

What the experts say

1 expert opinions

Access to Microsoft Smart Network Data Services (SNDS) when using an Email Service Provider (ESP) is primarily managed by the ESP themselves, as SNDS data is inherently linked to the IP addresses they control. For users on shared IP addresses, direct SNDS access is typically unavailable, but the ESP may offer reports or insights derived from their data. Conversely, clients utilizing dedicated IPs with their ESP might have a possibility of gaining direct SNDS access or receiving specific data for those IPs. The most effective step for any user is to directly consult their ESP regarding their policies and capabilities concerning SNDS data.

Key opinions

  • SNDS Access Managed by ESP: Microsoft SNDS access is predominantly controlled by your Email Service Provider (ESP) because the data is directly tied to the IP addresses they manage.
  • Shared IP Limitations: Customers utilizing shared IP addresses through an ESP typically cannot obtain direct SNDS access, as the ESP handles this data centrally, though they may provide summary reports or insights.
  • Dedicated IP Possibilities: For users with dedicated IP addresses provided by their ESP, there is a potential for direct SNDS access or for the ESP to supply relevant data specific to those IPs.

Key considerations

  • Direct ESP Consultation: The most effective way to understand your options for Microsoft SNDS data is to directly contact your Email Service Provider (ESP) and inquire about their specific policies and capabilities.
  • IP Type Impacts Access: Recognize that your ability to gain any form of SNDS access, whether direct or via reports, significantly depends on whether you are using shared or dedicated IP addresses with your ESP.
  • Request Data Insights: If direct SNDS access is not an option, ask your ESP if they can provide specific reports or insights derived from their SNDS data to help you monitor your sending reputation.

Expert view

Expert from Spam Resource explains that Microsoft SNDS access is typically controlled by the Email Service Provider (ESP) because SNDS data is tied to IP addresses. If you are using shared IPs, your ESP will manage this data and will likely not grant direct access, but might provide reports or insights based on the data. If you have dedicated IPs with your ESP, it may be possible for them to grant you direct SNDS access or provide you with the relevant data for those IPs. The best approach is to contact your ESP directly to inquire about their policy and capabilities regarding SNDS data.

14 Jan 2024 - Spam Resource

What the documentation says

4 technical articles

When an organization leverages an Email Service Provider (ESP) for email campaigns, direct access to Microsoft's Smart Network Data Services (SNDS) for their sending IPs is typically not granted to the end-user. This is because SNDS access is inherently tied to the ownership and active management of IP addresses, which remains with the ESP. For customers utilizing shared IP pools, the ESP's deliverability team takes full responsibility for registering, monitoring, and maintaining the reputation of these IPs within SNDS, ensuring optimal deliverability across their client base. While this centralized management benefits all users, it means individual customers on shared IPs usually cannot view raw SNDS data. However, for clients operating with a dedicated IP address through their ESP, there may be a pathway to secure direct SNDS access, although this requires explicit coordination and approval from the ESP to verify control over that specific IP. Ultimately, end-users should consult their ESP regarding their policies on SNDS data access or for any relevant reports.

Key findings

  • SNDS Access Tied to IP Ownership: Microsoft Smart Network Data Services (SNDS) access is intrinsically linked to the entity that owns and controls the sending IP addresses. For ESP customers, this means the ESP holds the primary access, not the individual user.
  • No Direct Access for Shared IPs: Users sending emails via an ESP's shared IP addresses typically cannot obtain direct access to SNDS data. The ESP's deliverability team is solely responsible for managing and monitoring these shared IPs within the SNDS program.
  • ESPs Handle IP Reputation: Email Service Providers proactively manage and maintain the reputation of their IP addresses, including their shared pools, through services like SNDS. This centralized management benefits all clients but negates the need for individual user access.
  • Dedicated IPs Offer Potential Access: Customers utilizing a dedicated IP address through their ESP may have the opportunity to secure direct SNDS access for that specific IP. This always requires explicit collaboration and approval from the ESP.
  • Reliance on ESP Deliverability Teams: As an ESP client, you depend on your provider's specialized deliverability teams to interact with SNDS and other postmaster tools, as direct user access to shared IP data is not provided.

Key considerations

  • Direct Communication with Your ESP: The most crucial step is to engage directly with your Email Service Provider to understand their specific policies regarding Microsoft SNDS access and data sharing, especially concerning shared versus dedicated IP setups.
  • Distinguish IP Types: Your ability to obtain any form of SNDS access, whether direct or via reports, heavily relies on whether you are using your ESP's shared IP addresses or a dedicated IP.
  • Inquire About Data Insights: If direct SNDS access is not feasible, ask your ESP if they can furnish specific deliverability reports or insights derived from their internal SNDS monitoring, which can still be valuable.

Technical article

Documentation from Microsoft Learn explains that users of Email Service Providers (ESPs) who send email from shared IP addresses do not typically need to register for SNDS directly. Instead, the ESP is responsible for managing their IPs in SNDS. End users will not be granted access to the shared IPs in SNDS, as the data belongs to the IP owner, which is the ESP. Access for specific IPs is granted only to the IP owner.

25 Dec 2022 - Microsoft Learn

Technical article

Documentation from Microsoft Postmaster Tools clarifies that the Smart Network Data Services (SNDS) program is primarily designed for Mailbox Providers and Internet Service Providers (ISPs) that own the IP addresses used for sending email. If you are an end-user of an Email Service Provider, the ESP itself is responsible for registering and managing their IP addresses within the SNDS program. Direct access for individual ESP customers to their ESP's shared IPs in SNDS is not provided.

8 Jul 2024 - Microsoft Postmaster Tools

Start improving your email deliverability today

Sign up