If your domain sends more than 5,000 emails a day to Outlook.com, Hotmail or Live addresses, the Outlook sender requirements come down to three checks: SPF must pass, DKIM must pass, and you need a DMARC record of at least p=none that aligns with one of them. Microsoft announced the change in April 2025 and started enforcing it that May. Mail that fails goes to the Junk folder, with rejection promised for a date Microsoft has not named. Here is each requirement in Microsoft’s words, and how to tell whether you pass.
Who has to care
Microsoft is specific about the mailboxes this covers: “This applies to Outlook.com – our consumer service, which is supporting hotmail.com live.com and outlook.com consumer domain addresses.” Work mailboxes hosted on Microsoft 365 are a different product and are not covered, though that helps less than you would hope: consumer Outlook addresses turn up in every B2C list and plenty of B2B ones.
The line is drawn at “domains sending more than 5,000 emails per day”. Notice the unit: domains, not IP addresses, so if a newsletter tool, a CRM and a support desk all send as yourcompany.com, the totals are yours together.
The jargon, briefly
- SPF (Sender Policy Framework): a DNS record naming the servers allowed to send mail using your domain.
- DKIM (DomainKeys Identified Mail): a signature on every message, so the receiver can confirm it came from you untampered.
- DMARC: a DNS record telling receivers what to do when those two fail, and where to send reports.
The term that catches people out is alignment. Microsoft’s definition: “Alignment ensures the ‘From’ domain matches (or sub domain) the domain used by SPF and/or DKIM.” If your reader sees you@yourcompany.com while the signature belongs to your sending platform, alignment fails even though both records are valid. Our guide to how SPF, DKIM and DMARC actually work unpacks it.
The Outlook sender requirements, word for word
| Requirement | Microsoft’s wording | How to satisfy it |
|---|---|---|
| SPF | “Must Pass for the sending domain.” | Publish one SPF record covering every service that sends for you. Microsoft adds: “Your domain’s DNS record should accurately list authorized IP addresses/hosts.” |
| DKIM | “Must Pass to validate email integrity and authenticity.” | Switch DKIM signing on in each sending platform and add the selector records it hands you. |
| DMARC | “At least p=none and align with either SPF or DKIM (preferably both).” | Publish a DMARC record with p=none and a reporting address, then confirm your visible From domain matches what SPF or DKIM signs. |
p=none is the gentlest DMARC policy there is: receivers take no special action and simply report back, so publishing it cannot break working mail. Microsoft would rather you went further in time, answering “Absolutely, once your legitimate sources are aligned” when its own FAQ asks about p=reject, while advising “moving gradually”.
Two traps sit inside those three lines. The first is SPF lookups. Microsoft warns that “If you exceed 10 DNS lookups, your SPF check might fail”, and every include: drags further lookups in behind it, so a domain that has quietly collected a CRM, a help desk and two newsletter tools may already be over.
The second is assuming your email vendor has this covered. Asked exactly that, Microsoft answers: “Yes. Even if you outsource sending, authentication is tied to your domain. Coordinate with your provider to ensure correct DNS settings.” Our email authentication setup checklist walks through what goes where.
What Microsoft recommends on top
Four more practices sit under “Additional Email Hygiene Recommendations”, things large senders “should also adopt to maintain quality and trust”:
- Compliant P2 (Primary) Sender Addresses: “Ensure the ‘From’ or ‘Reply-To’ address is valid, reflects the true sending domain, and can receive replies.”
- Functional Unsubscribe Links: “Provide an easy, clearly visible way for recipients to opt out of further messages, particularly for marketing or bulk mail.”
- List Hygiene & Bounce Management: “Remove invalid addresses regularly to reduce spam complaints, bounces, and wasted messages.”
- Transparent Mailing Practices: “Use accurate subject lines, avoid deceptive headers, and ensure your recipients have consented to receive your messages.”
Labeled recommendations, which reads softer than it proves to be: the same section closes by stating that Outlook “reserves the right to take negative action” against non-compliant senders, “including filtering or blocking”, singling out “critical breaches of authentication or hygiene”. Worth noticing what is absent, too: no complaint-rate ceiling, no required one-click unsubscribe header, nothing about forward and reverse DNS.
What “more than 5,000 emails per day” means in practice
The announcement never spells out how the count is measured: no rolling window, no note on when a day starts. It does tell you who Microsoft has in mind: “By focusing on senders of 5,000+ messages a day, we significantly reduce the likelihood of spam and spoofing campaigns reaching our user base.”
So treat the number as a boundary drawn in pencil. A 20,000-address list with a third of its addresses on Outlook.com sails past 5,000 on any day you mail the whole thing, and spreading that send across a week only keeps you under on paper.
What happens to mail that fails
The announcement is messy here, having been edited after publication: it now carries two accounts of the same deadline.
The headline change reads: “For domains sending over 5,000 emails per day, Outlook will soon require compliance with SPF, DKIM, DMARC. Non-compliant messages will first be routed to Junk. If issues remain unresolved, they may eventually be rejected.”
An April 29 update then says Microsoft “made a decision to reject messages that don’t pass the required authentication requirements detailed above”, and prints the exact bounce text: “550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.”
The paragraph immediately after describes the softer path: “After May 5th, 2025, Outlook will begin routing messages from high volume non-compliant domains to the Junk folder, giving senders an opportunity to address any outstanding issues”, with a note that “in the future (date to be announced), non-compliant messages will be rejected to further protect users.”
Both sit on the live page. The honest reading: Junk routing is the published behavior, rejection the published intention, with the bounce text released early so you recognize it when it appears. Any article handing you a firm rejection date goes further than Microsoft has. Our guide to reading email bounce codes explains how codes like this are built.
Asked whether a recipient’s safe senders list lets you skip the check, Microsoft answers: “No. Safe Sender list won’t be honored.”
How this compares with Gmail and Yahoo
If you did the work for Google and Yahoo back in 2024, you are most of the way there. Their published lists run longer, covering forward and reverse DNS, TLS, message formatting, a spam complaint ceiling and one-click unsubscribe, and we translated all of it in the Gmail and Yahoo bulk sender rules in plain English. Microsoft’s set is narrower: authentication and alignment, with the rest framed as recommendation. The overlap is what matters, since SPF and DKIM passing plus an aligned DMARC record at p=none covers the authentication core of all three, from one handful of DNS entries.
How to check where you stand
Send yourself a test message at an Outlook.com address you control, open it, and look for the option to view the message source. The authentication results near the top show spf, dkim and dmarc with a pass or fail beside each, plus the domain each one used. If dmarc fails while spf and dkim pass, you have found your alignment problem.
Then read your DMARC record with any public DNS lookup tool. You want a record that exists, a policy you chose deliberately, and a rua address somebody monitors. Microsoft confirms it sends the aggregate reports: “We send RUA to the addresses specified in your DMARC record.” It also states “We don’t have plans to send RUF”, so do not wait on forensic reports. While you are there, check your SPF record against Microsoft’s ceiling of ten DNS lookups.
Authentication is one input among several, and our walkthrough on checking your sender reputation covers the rest.
A do-this-week list
- Work out what share of your list sits on outlook.com, hotmail.com and live.com. That tells you whether 5,000 a day is theoretical or Tuesday.
- Send one test message to an Outlook.com address and read the authentication results.
- Fix whichever of the three is failing, starting with DKIM if your platform never had it switched on.
- Publish a DMARC record at p=none with a reporting address if you do not have one.
- Put a monthly reminder in your calendar to read those reports, because a record nobody reads tells you nothing when a new tool starts sending as you.
The hygiene half of the bargain
Authentication proves the mail is really yours. It says nothing about whether the addresses you are mailing still exist, and Microsoft’s recommendations make clear both sides count: “Remove invalid addresses regularly to reduce spam complaints, bounces, and wasted messages.” Asked how often, the FAQ says to “Aim to remove inactive or invalid addresses regularly”, suggesting monthly or quarterly.
That second half is what list verification handles. Running a list through Reoon Email Verifier before a large send clears out dead addresses and flags disposable or risky mailboxes, which keeps bounces and complaints down where providers are watching. Set the records once, then keep the list clean on a schedule. A free account comes with free verification credits every day, no card needed, enough to sample a list and see what is in it.
FAQ
Do the Outlook sender requirements apply to business Microsoft 365 mailboxes?
The announcement names the consumer service: Outlook.com, hotmail.com and live.com addresses. Mailboxes hosted on Microsoft 365 are a different product and are not covered by this requirement. The distinction rarely changes what you should do, since most lists carry consumer Outlook addresses anyway and the same records serve everyone.
Is a DMARC policy of p=none enough for Outlook?
Yes. The requirement reads “At least p=none and align with either SPF or DKIM (preferably both)”, so the mildest policy passes as long as alignment holds. A p=none record asks receivers to take no special action and simply send you reports, which makes it safe to publish.
What is the 550 5.7.515 error?
It is the rejection text Microsoft published for mail that fails these checks: “550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.” Seeing it means the receiving server refused your message on authentication grounds rather than content. Find the failing record, fix it, then retest.
What if I send fewer than 5,000 emails a day to Outlook?
Enforcement targets high volume domains first, and Microsoft puts it plainly: “While enforcement first targets large senders, all senders benefit from these best practices. Strong authentication protects your reputation.” Unauthenticated mail from a small sender can still be filtered on ordinary spam grounds, and the setup is one afternoon of DNS work.







