Microsoft 365 SPF Record Template
The correct microsoft 365 spf record for Exchange Online, plus when to add ESP includes and how to avoid PermError on crowded TXT records.

include:_spf.google.com in DNS for eleven months after moving mailboxes to Exchange Online. Outbound mail mostly worked. SPF evaluation returned pass for Google's range, not Microsoft's. DMARC alignment failed on some hybrid calendar invites. A client's gateway quarantined proposals until someone noticed the TXT record never changed.
The microsoft 365 spf record is not complicated. One include covers standard Exchange Online outbound. Complexity shows up when you stack marketing tools, ticketing SaaS, and payroll systems on the same domain without counting DNS lookups.Microsoft 365 SPF Record (Exchange Online Only)
If every message leaves through Microsoft 365 and no third-party tool sends as your domain, publish this TXT on the root domain:
v=spf1 include:spf.protection.outlook.com -allWhat it does
include:spf.protection.outlook.com delegates to Microsoft's SPF, which authorizes current Exchange Online sending IPs. -all hard-fails everything else.
Where to publish
DNS host for your domain (Cloudflare, GoDaddy, Route53, Azure DNS). One TXT record on @ or root. Not in M365 admin. DNS only.
For full syntax rules, see zerohook.org/blog/spf-record-syntax-complete-reference.
M365 Plus ESP or SaaS (Common Templates)
M365 + Mailchimp on the same root domain (count lookups before publish):
v=spf1 include:spf.protection.outlook.com include:servers.mcsv.net -allM365 + HubSpot marketing mail:
v=spf1 include:spf.protection.outlook.com include:spf.hubspotemail.net -allM365 + SendGrid transactional:
v=spf1 include:spf.protection.outlook.com include:sendgrid.net -allIn Cloudflare: DNS → Add record → Type TXT → Name @ → Paste the single line → TTL Auto → Save. Remove any second TXT that starts with v=spf1. Two SPF records = PermError.
Validate at zerohook.org/spf-checker. Confirm lookup count stays at or below 10. If permerror, remove dead includes or move marketing to mail.yourdomain.com with its own SPF.
Frequently Asked Questions
Key takeaways
Standard M365-only SPF: v=spf1 include:spf.protection.outlook.com -all
Add one include per live ESP; remove old provider includes after migration.
One SPF TXT per domain; validate lookup count after every edit.
Pair SPF with DKIM and DMARC for Gmail and Microsoft receiver requirements.
Share this analysis
Help others discover this content
More from our blog

How to Check an SPF Record (3 Ways)
Three ways to check an SPF record: dig and nslookup, PowerShell for Microsoft 365 admins, and a validator that counts DNS lookups. Plus how to read what you find.

SPF Flattening: When It Helps and Hurts
SPF flattening replaces includes with IP lists to stay under the 10-lookup cap. Learn when flattening services help, when they cause permerror, and safer alternatives.

Google Workspace SPF Record Mistakes
Google Workspace SPF setup: the correct include:_spf.google.com line, Mailchimp and HubSpot add-ons, and the migration mistakes that leave DMARC failing while Admin looks green.