Map Extract

550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level is Outlook.com rejecting your mail because a domain sending more than 5,000 messages a day to its consumer addresses does not pass SPF, DKIM and DMARC. Microsoft has enforced these rules since 5 May 2025: SPF must pass, DKIM must pass, and DMARC must be published at p=none or stricter and align with SPF or DKIM. Fix all three, test to an Outlook.com mailbox, and resend.

This guide covers what Microsoft announced, what the bounce means, who it applies to (consumer Outlook.com versus Microsoft 365 business recipients), the setup steps per provider, and how to monitor. For the wider pre-send routine, see the cold email deliverability checklist.

What Microsoft announced and when

On 2 April 2025 Microsoft published Outlook's new requirements for high-volume senders. The key points, from Microsoft's post:

ItemMicrosoft's position
WhoDomains sending "more than 5,000 emails per day"
To whomOutlook.com, "our consumer service", including hotmail.com, live.com and outlook.com addresses
SPFMust pass for the sending domain
DKIMMust pass
DMARC"At least p=none and align with either SPF or DKIM (preferably both)"
EnforcementFrom 5 May 2025
ActionOriginally Junk folder; an update on 29 April 2025 changed it to rejection
Safe SendersMicrosoft's FAQ says Safe Sender lists will not be honoured for this

Microsoft also lists recommended practices for large senders: a valid From or Reply-To address that reflects the true sending domain and accepts replies, a functional unsubscribe link, regular removal of invalid addresses, and "transparent mailing practices", including sending only to recipients who consented. Those are recommendations rather than the conditions for the 5.7.515 rejection, but the policy says Microsoft may take "negative action" against non-compliant senders.

Reading the 5.7.515 bounce

A typical non-delivery report for a fictional sender:

Remote server returned '550 5.7.515 Access denied, sending domain
OUTREACH.OAKLINE-JOINERY.EXAMPLE does not meet the required authentication level.'

What each part tells you:

  • 550: a permanent failure. The message will not be retried. Resending without a fix produces the same bounce.
  • 5.7.515: the 5.7.x class is security and policy. This specific code is Microsoft's authentication requirement.
  • The domain named is the one Microsoft evaluated, normally your From domain. If it is a subdomain you did not expect, your mail provider may be using a different envelope domain.

Common causes, in rough order:

CauseHow to spot itFix
No DMARC recorddig TXT _dmarc.yourdomain.example returns nothingPublish v=DMARC1; p=none; rua=mailto:...
DKIM signed by the provider's domain, not yoursHeaders show d= set to your provider's domainTurn on custom DKIM for your domain
SPF missing the actual sending servicespf=fail or softfail in test headersAdd the service's include
SPF over 10 lookupspermerror in test headersSee SPF too many DNS lookups
From domain not alignedSPF passes for the provider's bounce domain, DKIM for the provider, neither matches your FromCustom DKIM or custom return-path on your domain
Two SPF recordsdig TXT shows two v=spf1 linesMerge into one; RFC 7208 treats two as permerror

Consumer Outlook.com versus Microsoft 365 recipients

This is where B2B senders often misread the rule.

  • Outlook.com consumer addresses (@outlook.com, @hotmail.com, @live.com and their country variants) are covered by the high-volume requirements. If you send over 5,000 a day to them and fail authentication, you get 5.7.515.
  • Microsoft 365 business recipients (@oakline-joinery.example hosted on Exchange Online) are filtered by Exchange Online Protection with each tenant's own settings. Microsoft's announcement is about Outlook.com, not about business tenants.

So a UK B2B sender whose recipients are mostly companies on Microsoft 365 is probably not the main target of this rule, and a sender writing a few dozen messages a day is well under the threshold. That does not make authentication optional. Business tenants also check SPF, DKIM and DMARC, and a domain that fails them is more likely to be filtered or quarantined. The practical rule is simple: meet the high-volume standard regardless of your volume, and the 5.7.515 bounce never becomes your problem.

Also note that sole traders often use consumer addresses (kestrel.plumbing@outlook.example style). Those are individual subscribers under PECR, who need consent or the soft opt-in for marketing email, per the ICO's business-to-business guidance. Your list should already be handling them separately.

Setup steps by provider

Google Workspace as the sender

  1. SPF: one TXT record on your domain, for example v=spf1 include:_spf.google.com ~all, plus includes for any other service that sends as the domain.
  2. DKIM: in the Admin console, open Apps, Google Workspace, Gmail, Authenticate email; generate a key for your domain, publish the TXT record at google._domainkey, then start authentication.
  3. DMARC: _dmarc.yourdomain.example TXT "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.example".
  4. Test: send to an Outlook.com mailbox and read the Authentication-Results header.

Microsoft 365 as the sender

  1. SPF: v=spf1 include:spf.protection.outlook.com ~all for a custom domain.
  2. DKIM: in the Microsoft Defender portal, under email authentication settings, enable DKIM for your custom domain and publish the two CNAME records it gives you (selector1._domainkey and selector2._domainkey).
  3. DMARC: as above.
  4. Test: the same check to an Outlook.com mailbox.

A hosting provider or SMTP relay

  1. Find the provider's SPF include in their help pages and add it to your single SPF record.
  2. Turn on DKIM for your own domain in the control panel. If the provider can only sign with its own domain, DMARC alignment depends on SPF, which means the envelope sender (return-path) must be on your domain too.
  3. Publish DMARC and test.

Checking a test message

In Outlook.com, open the message, choose the three dots, then view message source. Look for:

Authentication-Results: spf=pass (sender IP is 203.0.113.25)
 smtp.mailfrom=outreach.oakline-joinery.example; dkim=pass (signature was verified)
 header.d=outreach.oakline-joinery.example; dmarc=pass action=none
 header.from=outreach.oakline-joinery.example

All three must say pass, and the header.d (DKIM) or smtp.mailfrom (SPF) domain must match or be a parent of header.from.

Resending after a 5.7.515

The bounce is permanent, so nothing will retry automatically. Once tests pass:

  1. Resend in small batches rather than all at once.
  2. Watch for new bounces; a different code means a different problem (see the SMTP error codes guide).
  3. Do not mark 5.7.515 addresses as invalid. The recipients exist; your domain failed.

Monitoring with SNDS and DMARC reports

Smart Network Data Services (SNDS) is Microsoft's reporting tool for Outlook.com traffic. It works on IP addresses: you register IP ranges you control and see volume, filter results and complaint data for mail from them. According to Postmastery's review of the update, Microsoft moved SNDS to a new portal on 8 June 2026; the old address redirects. The same review notes that trap hit counts were scheduled to be removed from the data report in July 2026 and a new OAuth API replaces the old CSV download approach.

SNDS has a limit for small senders: you must control the IPs. If you send through Google Workspace, Microsoft 365 or shared hosting, the IPs are your provider's and you cannot register them. For those senders the better monitoring sources are:

  • DMARC aggregate reports. Microsoft's FAQ says Outlook.com sends aggregate (rua) reports to the address in your DMARC record. They show which IPs sent as your domain and whether they passed.
  • Your own bounce log. A sudden cluster of 5.7.x codes from Outlook.com is the earliest warning.
  • Reply rates. A drop to zero from Microsoft recipients while others reply suggests filtering.

Microsoft's policies, practices and guidelines page is the reference for Outlook.com's general sending policies and links to the sender support forms. Among other things it asks senders to have valid reverse DNS, avoid dynamic IP addresses, stop retrying recipients after permanent failures and not use namespace mining, and to make their unsubscribe mechanism easy to find and use.

How Map Extract helps

The bulk email sender sends through your own SMTP mailboxes, so the authentication Microsoft checks is whatever your domain and mail provider publish. Map Extract does not check or fix SPF, DKIM or DMARC records; you set those up with your DNS host and provider as described above.

Where it helps is the behaviour around a rejection. Replies and bounces are read back by IMAP, and a campaign pauses itself with an emergency stop when bounces reach the threshold (5% by default), so a domain that starts failing authentication does not keep burning through the list. Ambiguous failures are marked "Uncertain" and not blindly retried. Caps per hour, day and month, a minimum delay and per-route ceilings keep volume well below the 5,000 a day threshold for typical B2B use. The marketing permission gate holds any recipient without a recorded lawful basis and opt-out route, which matters for consumer-domain sole traders in particular.

Key takeaways

  • 5.7.515 means your domain failed Microsoft's authentication standard for high-volume senders to Outlook.com.
  • The fix is SPF pass, DKIM pass on your own domain, and DMARC p=none or stricter with alignment.
  • Enforcement started on 5 May 2025, as rejection rather than Junk.
  • The rule targets consumer Outlook.com addresses; Microsoft 365 business tenants filter by their own settings, but authentication matters there too.
  • SNDS needs IPs you control; small senders should rely on DMARC reports and bounce logs instead.

Frequently asked questions

What does 550 5.7.515 Access denied mean?

It means Outlook.com rejected your message because the sending domain did not meet Microsoft's authentication requirements for high-volume senders. The domain must pass SPF, pass DKIM, and publish a DMARC record of at least p=none that aligns with SPF or DKIM. Fix the failing record, send a test to an Outlook.com address, check the authentication results and resend.

Do Microsoft's high-volume sender rules apply to Microsoft 365 business mailboxes?

Microsoft's announcement applies to Outlook.com, its consumer service, including hotmail.com, live.com and outlook.com addresses. Microsoft 365 business tenants are filtered by their own tenant settings rather than by this rule. In practice a B2B sender should meet the same standard anyway, because authentication failures also hurt delivery to business tenants.

When did Microsoft start enforcing the Outlook.com sender requirements?

Microsoft announced the requirements on 2 April 2025 and enforcement began on 5 May 2025. The original plan was to route non-compliant mail to Junk first; an update at the end of April 2025 changed this to rejection, which is when senders began seeing the 550 5.7.515 bounce.

Can I use SNDS if I send from Google Workspace or Microsoft 365?

Usually not. Smart Network Data Services reports on IP addresses, and you have to show that you control the IPs before Microsoft gives you data. Senders on Google Workspace, Microsoft 365 or shared hosting send from their provider's shared IPs, which they cannot register. SNDS is most useful to senders with their own dedicated sending IPs.

Sources

  1. Microsoft: Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders
  2. Microsoft: Outlook.com policies, practices and guidelines
  3. Microsoft Smart Network Data Services (SNDS)
  4. Postmastery: The first big SNDS update in years
  5. RFC 7208: Sender Policy Framework (SPF)
  6. ICO: Business-to-business marketing
  7. Microsoft Learn: Set up DKIM to sign mail from your Microsoft 365 domain

Written by the Map Extract editorial team. Found an error? Email support@mapextract.uk and we will check and correct it. How we research guides: editorial policy.

See it working on your own searches.

Start with one keyword, one location and a small limit. Review the records, then decide on a licence.

Top