Skip to content

Outlook.com's sender rules, and how to check your domain against them

If email from your company to Outlook.com, Hotmail or Live addresses is bouncing with "550 5.7.515 Access denied, sending domain yourdomain.com does not meet the required authentication level", Microsoft's sender rules are the reason. Here is what they ask for, and how to check your domain.

Results in about ten seconds. No sign-up; we only read public records.

This check reads public records. The full checkup reads Microsoft 365 or Google Workspace too, where most break-ins start: run it free, read-only, in about four minutes.

northwind-dental.com

Example report

Score 58 out of 100

Some real gaps: 3 to fix and 1 to review.

Email 45
Domain 60
Website 80
  • Critical Nothing stops criminals sending email as this domain
  • High Microsoft 365 isn't signing your email (DKIM)
  • High Your domain isn't locked against transfers
  • Medium Your website's certificate expires in 12 days

6 checks passing

This is what the internet can see. Most break-ins start inside.

A free account connects Microsoft 365 or Google Workspace read-only and checks the inside in about four minutes:

  • Does every admin have a second sign-in step?
  • Is a mailbox forwarding email outside the company?
  • Which outside apps can read email or files?
  • Can guests re-share your files?
Run the full checkup, free

Nothing changes without you. No card.

What Microsoft asks for

The rules apply to a domain that sends more than 5,000 messages a day to Microsoft's consumer email services (Outlook.com, Hotmail, Live), counted by the domain in the From address. Once a domain is over that line, its mail has to meet three requirements:

  • SPF: the domain publishes an SPF record listing who may send for it, and messages pass the SPF check.
  • DKIM: the domain publishes DKIM keys and messages carry a valid signature. Microsoft says both SPF and DKIM must pass.
  • DMARC: the domain publishes a DMARC record at _dmarc.yourdomain.com, at least v=DMARC1; p=none, and messages pass DMARC: SPF or DKIM (at least one) passes and lines up with the domain in the From address.

Since when

Microsoft announced the rules in April 2025 and has applied them since 5 May 2025. Mail that fails them is rejected with error 550 5.7.515; it isn't sent to Junk.

Who this catches

Small companies rarely send 5,000 messages a day to Outlook.com, Hotmail and Live addresses by hand, but the count includes everything sent with your domain in the From address: newsletters, invoices from your accounting system, booking reminders, a CRM's automated email. Each of those services needs its own SPF entry or its own DKIM signing for your domain.

Google and Yahoo have similar rules for bulk senders. They ask for the same SPF, DKIM and DMARC setup, and also require a one-click unsubscribe link in marketing email and a low spam complaint rate.

Fix what's missing

  1. 1

    No DMARC record

    Publish v=DMARC1; p=none; rua=mailto: plus an address that collects reports. p=none changes nothing about delivery; it meets Microsoft's minimum and starts the reports. Our DMARC guide walks through moving to quarantine and reject later.

  2. 2

    SPF missing a sender

    Add the service's include to your one SPF record. Two SPF records on one domain is an error, and SPF allows at most 10 DNS lookups.

  3. 3

    No DKIM for Microsoft 365

    Turn on DKIM signing for your custom domain in Microsoft Defender. Our DKIM guide has the steps.

  4. 4

    A service that sends as you without either

    Set up DKIM signing in that service for your domain, which also makes DMARC line up.

How TenantWard helps

The free domain check needs no account for the score and the most serious issue; a free account shows the rest. It reads your SPF, DKIM, DMARC and MTA-STS records and gives a plain-English line for each: whether SPF exists and stays within its lookup limit, whether DKIM keys are published for the common selectors, and what your DMARC policy does and where its reports go.

A free account rechecks one domain every week. Paid plans check more often, can collect your DMARC reports to show which services send as you and whether they pass, and can publish SPF, DKIM and DMARC records for you when your DNS is at Cloudflare, GoDaddy, Amazon Route 53, Azure DNS or IONOS, with the previous records saved first.

Sources

  • Microsoft Support, Fix NDR error 550 5.7.515 in Outlook.com: support.microsoft.com/en-au/topic/fix-ndr-error-550-5-7-515-in-outlook-com-34cfe8f8-6fbf-457e-9e8b-9e4dbaf4e0ef
  • Microsoft Tech Community, Strengthening the email ecosystem: Outlook's new requirements for high-volume senders: techcommunity.microsoft.com/blog/outlook/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730
  • Outlook.com Postmaster, Policies, practices and guidelines: substrate.office.com/ip-domain-management-snds/postmaster/Policies
  • Google, Email sender guidelines FAQ: support.google.com/a/answer/14229414
  • Yahoo, Sender FAQs: senders.yahooinc.com/faqs

Questions

We send far fewer than 5,000 a day. Do we need to do anything?
Microsoft's rule only applies above that line, but SPF, DKIM and DMARC are what every mail provider uses to decide whether to trust you, and DMARC stops other people sending as your domain. They're worth having at any size.
Is p=none enough?
For Microsoft's rule, yes. To stop others sending as your domain, move to quarantine and then reject once your reports show every real sender passing.

See where your company stands

Check a domain for free. A free account also connects Microsoft 365 or Google Workspace read-only and shows every issue it finds; a plan shows who's affected and fixes it.