Summary
To grant someone access to your SNDS account, the consensus is that the individual needs to create their own Microsoft account and register for a separate SNDS account. They then submit a request for access, specifying the relevant IP ranges. The account administrator receives a notification and approves the request within the SNDS interface. If Sendgrid or another provider owns the IP addresses, they might need to approve the access as well. Sharing login credentials is strongly discouraged for security and auditability reasons. As an alternative, sharing SNDS reports might be considered when direct access is problematic.
Key findings
- Individual accounts required: Every user accessing SNDS must have their own Microsoft account and SNDS account.
- Access request initiated by user: The individual requiring access is responsible for requesting it through the SNDS interface.
- IP address specification: The request must include the specific IP ranges that the user needs to monitor.
- Administrator approval needed: The SNDS account administrator must approve the access request.
- Third-party approval may be necessary: If Sendgrid or another provider owns the IPs, they may need to approve the request as well.
- Sharing accounts is discouraged: Sharing login credentials is not a secure practice and complicates tracking and accountability.
- Reports are an alternative: Sharing reports provides data access without granting full account access.
Key considerations
- Valid Microsoft Account: Ensure the requesting user has a valid Microsoft account associated with a legitimate email address (e.g., abuse@ or postmaster@domain.com).
- Accurate IP addresses: Verify the IP addresses specified in the access request are correct.
- Third-party notification: If Sendgrid or another provider owns the IPs, notify them of the pending access request to expedite approval.
- Approval timeframe: Approve or deny access requests promptly, as delayed responses might require the user to re-submit their request.
- Alternative access option: Explore the use of reports for those who don't require full access to the SNDS.
- Linking to Infrastructure: Setting up SNDS initially requires linking it to your sending infrastructure, before users request access.
What email marketers say
13 marketer opinions
To grant someone access to your SNDS account, the recommended approach is for the individual to create their own Microsoft account and register for an SNDS account. They then request access to specific IP ranges. The account owner receives a notification and must approve the request within the SNDS interface. If the IP is managed by a third party like Sendgrid, they might need to approve the request. Sharing account credentials is discouraged for security reasons. As an alternative, you could share reports generated from your SNDS data.
Key opinions
- Individual Accounts: Each user should create their own SNDS account with their Microsoft account.
- Request Access: The user requests access to specific IP ranges they need to monitor.
- Approval Process: The account owner approves the access request within the SNDS interface.
- Third-Party Approval: If a third party manages the IP, they might also need to approve the request (e.g., Sendgrid).
- Security: Sharing account credentials is not recommended due to security risks.
- Alternative Data Sharing: Consider sharing reports generated from SNDS data if direct access is not feasible.
Key considerations
- Microsoft Account: Ensure the requesting user has a valid Microsoft account.
- IP Address Accuracy: Verify the IP addresses being requested are correct.
- Abuse/Postmaster Address: The Microsoft account's email address should ideally match the abuse or postmaster address associated with the sending domain.
- Sendgrid Approval: If Sendgrid manages the IP, inform your account manager to expect the access request.
- Timely Approval: Approve access requests promptly, as there might be a limited time window.
- Reporting as an Alternative: If you are sharing reports, ensure it's done in a secure manner.
Marketer view
Email marketer from Reddit shares that setting up SNDS initially requires linking it to your sending infrastructure. Then each user who requires access has to request it.
19 Feb 2024 - Reddit
Marketer view
Email marketer from Quora advises that the most secure method is for each individual to have their own SNDS account, tied to their own Microsoft account, requesting access as needed. Sharing login credentials introduces unnecessary security risks.
17 Nov 2021 - Quora
What the experts say
2 expert opinions
Experts emphasize that individuals should request SNDS access on their own, rather than sharing accounts. This approach is crucial for maintaining security, ensuring proper audit trails, and tracking accountability effectively. Sharing accounts can lead to confusion and potential issues regarding future use and access management.
Key opinions
- Individual Requests: Users needing access should request it themselves.
- Account Sharing Risks: Sharing accounts compromises security and auditability.
- Accountability: Individual accounts are important to track account usage and accountability.
Key considerations
- Security Best Practices: Follow security best practices by avoiding account sharing.
- Audit Trail: Maintain a clear audit trail for SNDS access and usage.
- Access Control: Implement proper access control by granting permissions only to those who need it.
Expert view
Expert from Word to the Wise explains that granting access requires the user to request access on their own. Sharing accounts causes confusion on who is using the account and can lead to issues for future use.
29 Mar 2025 - Word to the Wise
Expert view
Expert from Spam Resource highlights the importance of individual accounts for security and audit trails. Sharing accounts introduces risks and makes tracking accountability difficult. Therefore, the best approach is for each person to set up their own SNDS account and request permissions.
10 Jan 2024 - Spam Resource
What the documentation says
3 technical articles
Microsoft documentation outlines that granting SNDS access involves individual accounts, where users create their own account and request access to specific IP ranges. The account administrator must then approve the request via the SNDS interface. A valid Microsoft account is required, ideally using an email address matching the abuse/postmaster address of the sending domain. The administrator receives an email notification of the access request and the approval is IP-specific.
Key findings
- Individual SNDS Accounts: Each user must create their own SNDS account.
- Request Specific IPs: Users request access to specific IP ranges.
- Administrator Approval: The account administrator must approve the access request in the SNDS interface.
- Email Notification: Administrators receive an email notification for access requests.
Key considerations
- Valid Microsoft Account: The user needs a valid Microsoft account.
- Matching Email Address: The Microsoft account email should match the abuse/postmaster address of the sending domain for easier verification.
- IP Address Verification: Ensure the requested IP address is correct before approving the access request.
Technical article
Documentation from Microsoft explains that after a user requests access, the SNDS account administrator receives an email notification. The administrator must then log into their SNDS account and approve the request. The approval is tied to the IP address being requested, so ensure the IP is correct.
27 Dec 2023 - Microsoft
Technical article
Documentation from Microsoft explains that SNDS accounts are individual. Users need to create their own account and request access to the specific IP ranges they want to monitor. The account owner then needs to grant access within the SNDS interface.
12 Mar 2022 - Microsoft
Can multiple users access Google Postmaster Tools for a single domain?
How accurate are SNDS colors in reflecting email delivery performance?
How accurate is Microsoft SNDS data for deliverability monitoring?
How accurate is SNDS and Google Postmaster Tools reputation data?
How accurate is the spam data shown in the new Google Postmaster Tools and how can I get data to appear?
How do I resolve SNDS issues with IPs already added to another account?
How to update or change the complaint address for JMRP FBLs in SNDS?
Why is Microsoft SNDS data not displaying or delayed?
