What volume qualifies as a bulk sender for Microsoft?

Microsoft applies stricter requirements to senders of 5,000 or more daily messages to Outlook.com, Hotmail.com, and Live.com addresses. Lower volumes still benefit from following these guidelines.

How do I register for SNDS and JMRP?

Visit Microsoft's Smart Network Data Services portal to register your sending IPs. The JMRP signup is available through the same portal. You will need to verify ownership of your IP addresses.

Are Microsoft's requirements the same as Gmail's?

The core requirements (SPF, DKIM, DMARC, unsubscribe) are similar, but implementation details and enforcement differ. Complying with both sets of requirements ensures broad deliverability.

How long does it take to resolve a Microsoft block?

After fixing issues and submitting a delisting request, Microsoft typically responds within 24-48 hours. Full reputation recovery may take weeks of consistent good sending behavior.

Does Microsoft require one-click unsubscribe like Gmail?

Yes. Microsoft now requires List-Unsubscribe headers for bulk senders, and displaying unsubscribe options in the Outlook interface depends on these headers being present. While Microsoft's implementation is slightly different from Gmail's RFC 8058 requirement, implementing one-click unsubscribe for Gmail also satisfies Microsoft's expectations.

What is SNDS and how do I use it?

SNDS (Smart Network Data Services) is Microsoft's IP reputation monitoring tool. Register your sending IP ranges at the SNDS portal, verify ownership, and you can view reputation status (green/yellow/red), complaint rates, and spam trap hits for each IP. Check SNDS regularly to catch reputation problems early.

How do I submit a delisting request to Microsoft?

If Microsoft is blocking your email, submit a delisting request through the Outlook.com sender support form. Provide your sending IP, explain the issue, and describe what you've done to fix it. Microsoft typically responds within 24-48 hours. Note: you must fix the root cause before requesting delisting, or the block will return.

Microsoft & Outlook Bulk Sender Requirements 2026

Authentication Requirements

SPF (Sender Policy Framework)

Microsoft requires SPF to pass for your sending domain. Your SPF record must:

Include all IP addresses and services that send on your behalf
End with a definitive mechanism (-all or ~all)
Stay within the 10 DNS lookup limit
Align with your From domain (at least relaxed alignment)

DKIM (DomainKeys Identified Mail)

DKIM signing is required for bulk senders. Your implementation must:

Use RSA keys of 1024 bits or higher (2048 recommended)
Sign messages with a valid, unexpired key
Include proper selector in DNS
Align the DKIM d= domain with the From domain

DMARC (Domain-based Message Authentication)

Microsoft now requires DMARC for high-volume senders:

Publish a DMARC record for your sending domain
At minimum, use p=none for monitoring
Ensure either SPF or DKIM passes with alignment
Set up aggregate reporting (rua) to monitor authentication

DMARC Policy Progression

While Microsoft accepts p=none, we recommend progressing to p=quarantine and eventually p=reject. Stronger policies demonstrate confidence in your authentication and can improve deliverability.

Message Standards

From Address Requirements

Must be a valid, working email address
Should match the domain you authenticated
Cannot be a no-reply address for marketing emails
Must be able to receive replies and bounces

Reply-To Configuration

Reply-To address should be monitored
Should not differ suspiciously from the From address
Must be a valid, deliverable address

Subject Line Requirements

Must not be deceptive or misleading
Should accurately reflect message content
Cannot use deceptive formatting (Re:, Fwd: when not applicable)

Unsubscribe Requirements

Microsoft requires clear unsubscribe functionality:

Visible unsubscribe link: Must be clear and easy to find in every email
One-click unsubscribe: List-Unsubscribe header with mailto or HTTPS option
Prompt processing: Honor unsubscribe requests within 10 days (best practice: immediately)
Working mechanism: Unsubscribe links must actually function

Header-Based Unsubscribe

Implement List-Unsubscribe and List-Unsubscribe-Post headers. Microsoft uses these to display unsubscribe options in the Outlook interface. Missing headers can increase spam folder placement. This requirement is similar to Gmail's one-click unsubscribe requirement.

Reputation Requirements

Complaint Rates

Microsoft monitors spam complaints through their Junk Email Reporting Program (JMRP). Keeping your spam complaint rate low is critical:

Keep complaint rates as low as possible
High complaints trigger increased filtering
Persistent high rates lead to blocking

Bounce Handling

Remove hard bouncing addresses immediately
Implement proper bounce processing
Do not repeatedly send to invalid addresses

Engagement Signals

Microsoft considers recipient engagement. If you notice declining engagement, your messages may be landing in Outlook's junk folder:

Opens and clicks indicate wanted mail
Deletes without opening suggest unwanted mail
Moves to Junk are strong negative signals
Moves from Junk to Inbox are positive signals

Infrastructure Requirements

IP Address Standards

Use consistent sending IPs
Maintain valid PTR (reverse DNS) records
Warm up new IPs gradually
Monitor IP reputation through SNDS

Sending Patterns

Maintain consistent sending volumes
Avoid sudden volume spikes
Do not send in rapid bursts
Spread sending across the day

Microsoft Tools for Senders

Smart Network Data Services (SNDS)

SNDS provides insight into your sending reputation:

View IP reputation status
Monitor complaint rates
See spam trap hits
Identify problematic sending patterns

Junk Email Reporting Program (JMRP)

Get notified when users mark your email as spam
Identify which messages generate complaints
Suppress complaining addresses from your list

Consequences of Non-Compliance

Junk folder: Emails routed to spam instead of inbox
Throttling: Sending rate limited or deferred
Blocking: Connection refused or messages rejected
Permanent blocks: Repeated violations may result in permanent IP or domain blocks

If you find yourself on a blocklist, see our guide on how to get removed from an email blacklist.

Microsoft vs Gmail vs Yahoo: Requirements Comparison

All three major mailbox providers now enforce authentication and sender quality standards for bulk senders. The following table shows how Gmail, Yahoo, and Microsoft compare across key requirements:

Requirement	Microsoft	Gmail	Yahoo
SPF	Required (must pass)	Required (must pass)	Required (must pass)
DKIM	Required (must pass)	Required (must pass)	Required (must pass)
DMARC	Required (p=none minimum)	Required (p=none minimum)	Required (p=none minimum)
Bulk Sender Threshold	5,000 messages/day	5,000 messages/day	5,000 messages/day
Spam Rate Limit	Not publicly specified (keep as low as possible)	Below 0.3% (target under 0.1%)	Below 0.3%
One-Click Unsubscribe	Required (List-Unsubscribe header)	Required (RFC 8058)	Required (RFC 8058)
Monitoring Tool	SNDS & JMRP	Google Postmaster Tools	Complaint Feedback Loop
PTR Records	Required	Required	Required
TLS	Required (opportunistic TLS)	Required (TLS connection)	Required (TLS connection)
Enforcement	Junk folder, then reject	Junk folder, then reject	Junk folder, then reject

The three providers now align on core authentication requirements: SPF, DKIM, and DMARC are non-negotiable for any sender delivering 5,000 or more messages per day. If you meet the requirements for one provider, you are most of the way to meeting them for all three. The key differences are in monitoring tools and the specifics of spam rate thresholds.

Outlook.com vs Microsoft 365: Key Differences

When people talk about "Microsoft email delivery," they are usually referring to two very different systems. Understanding the distinction is essential for troubleshooting deliverability issues.

Outlook.com (Consumer)

Outlook.com covers consumer email addresses including Hotmail.com, Live.com, and Outlook.com domains. These accounts are managed by Microsoft's consumer mail team. The bulk sender requirements described in this article apply directly to Outlook.com. SNDS and JMRP are the monitoring tools for this platform, and Microsoft's enforcement actions (junk foldering, throttling, blocking) happen here. If your emails are going to junk in Outlook, you are likely dealing with Outlook.com consumer filtering.

Microsoft 365 (Business)

Microsoft 365 (formerly Office 365) is used by businesses and organizations. Each organization manages its own email security policies through Exchange Online and Microsoft Defender for Office 365. Microsoft's consumer bulk sender rules do not apply the same way to Microsoft 365 accounts because delivery decisions depend on the recipient organization's own Exchange and Defender configuration. Administrators at each organization can set their own spam filtering thresholds, allowed sender lists, and authentication requirements.

Key Takeaway

Most "Microsoft delivery problems" that bulk senders encounter involve Outlook.com consumer accounts. If you are having trouble reaching Microsoft 365 business accounts, the issue is likely the recipient organization's email security policies rather than Microsoft's global bulk sender requirements. Contact the recipient organization's IT team if you suspect their policies are blocking your messages.

Microsoft & Outlook Bulk Sender Requirements for 2026