Who the Outlook rules apply to
Microsoft's requirements target high-volume senders, defined as domains that send more than 5,000 emails a day to Outlook.com, Hotmail and Live consumer mailboxes. Microsoft announced the requirements in April 2025 and set enforcement from May 5, 2025. The 5,000 figure counts messages to Microsoft's consumer domains, not your total volume across all providers.
Below that line you are not formally covered, but the same setup is what every mailbox provider rewards. If you send from a domain that will grow past the threshold, set this up before you need it, because fixing authentication after mail starts failing is slower than doing it first.
What to set up
The core requirement is authentication: SPF, DKIM and DMARC all passing, with the domain in your visible From address aligned to the domain that passed SPF or DKIM. Microsoft's guidance accepts a DMARC policy of p=none as the minimum, so you can start in monitoring mode and tighten later once the reports show your legitimate senders pass.
Microsoft also expects the basics of a legitimate bulk sender: a valid From or Reply-To address that can receive mail, a working unsubscribe mechanism on marketing messages, and a clean list. None of these replace authentication, and authentication does not replace them.
- Publish an SPF record listing every service that sends for you, within the 10 DNS lookup limit.
- Turn on DKIM signing in each sending tool using your own domain, not the tool's default.
- Publish a DMARC record at _dmarc.yourdomain with at least p=none and a reporting address.
- Send a test message to an Outlook.com mailbox and confirm the headers show spf=pass, dkim=pass and dmarc=pass.
What failure looks like
Microsoft announced a staged approach: non-compliant mail is first routed to the Junk folder, with outright rejection to follow. When mail is rejected, the sending server receives an SMTP error that says the sending domain does not meet the required authentication level. Reports describe this as a 550 5.7.515 response, which you will see in your sending tool's bounce log.
That bounce is not an address problem. It is a domain problem, and it affects every recipient at Microsoft's consumer domains at once. If you see a spike of 5.7.x bounces to outlook.com and hotmail.com addresses, check authentication before you check your list.
Read bounce codes by their class. A 5.1.1 means the mailbox does not exist, which is a list problem. A 5.7.x code means the receiving server refused your message, which is a sender or authentication problem.
Where list quality fits
Authentication gets your mail accepted. List quality decides whether people want it. Outlook.com, like other providers, watches complaints and bounces as part of your sender reputation, and a list full of dead or recycled addresses pushes both in the wrong direction. Spam traps in an old list can do real damage.
Verify addresses before large sends, especially for lists you did not collect recently. Remove undeliverable addresses, handle risky ones such as catch-all and role addresses on purpose, and suppress anyone who unsubscribes or complains. Verification does not satisfy any Microsoft requirement by itself, but it keeps the part of your record that you control in good shape.
A short audit for your sending domain
Go through this list for each domain you send from. Authentication comes first, because the other items do not help while it fails.
- Check SPF, DKIM and DMARC with a lookup tool and confirm alignment on a real message.
- Send a test to an Outlook.com address and read the authentication results in the headers.
- Search your bounce logs for 5.7.x codes from outlook.com, hotmail.com and live.com.
- Confirm marketing mail carries a working unsubscribe link and that unsubscribes take effect before the next send.
- Verify any list older than a few months before you send to it.
- Read Microsoft's announcement for the current enforcement stage before you change anything drastic.
Key takeaways
0/5Try it on a real address
Run syntax, DNS, MX, disposable, and role checks on any address. No signup needed.
Enter an address and press Check.
Runs real syntax, DNS and mail-server checks.
This demo checks syntax, domain, mail server, disposable and role-address rules. Sign up free for live mailbox checks.
Frequently asked questions
Verify addresses with one API call.
250 free checks to start, no card required. Unknown results are never billed.