
A Microsoft 365 tenant can hold many custom domains — brands, regions, outreach domains — and every one that sends email needs a valid SPF record. Managing them one by one works for three domains and falls apart at thirty. This guide covers multi-domain SPF for Microsoft 365: why one record can't cover them all, three patterns for keeping many records consistent, staying within the lookup limit, auditing every domain at once, and fixing the usual problems.
Myth: One SPF Record Can Cover All Your Domains
💡 TL;DR
For multi-domain SPF in Microsoft 365, every custom domain and every sending subdomain needs its own SPF TXT record — one domain's record never covers another. Start each with v=spf1 include:spf.protection.outlook.com -all, keep shared senders consistent using a redirect or a shared include record if many domains need the same policy, stay within 10 DNS lookups per domain, publish v=spf1 -all on domains that don't send, and audit all domains on a schedule.
Here's the myth: "Our main domain's SPF record includes Microsoft 365, so all our other domains in the tenant are covered." They aren't. Receivers check SPF for the domain in the message's envelope sender. Each domain is looked up on its own. A domain with no SPF record of its own has no SPF protection, no matter what the main domain publishes.
Microsoft's own documentation is clear on the subdomain version of this too: an SPF record on contoso.com doesn't cover marketing.contoso.com — each sending subdomain needs its own record.
By the end of this, you'll know exactly how to set up and maintain multi-domain SPF for Microsoft 365 so every domain stays valid as you add more.
The Per-Domain Baseline
Start every domain from the same baseline.
Domain type | SPF record | Notes |
|---|---|---|
Custom domain sending only from Microsoft 365 (commercial) | v=spf1 include:spf.protection.outlook.com -all | Microsoft's documented value |
Sending subdomain | Its own SPF record with the right include | Not covered by the parent's record |
Domain also sending from another service | v=spf1 include:spf.protection.outlook.com include:{service} -all | Count total lookups |
Domain added but not sending | v=spf1 -all | Prevents easy spoofing |
GCC High / DoD tenants | include:spf.protection.office365.us | Sovereign cloud variant |
The tenant's initial onmicrosoft.com domain is managed by Microsoft; you don't publish SPF for it yourself. Microsoft's SPF guide for cloud domains covers each case.
Three Patterns for Managing Many Domains
When many domains need the same sending policy, these patterns keep them consistent.
Pattern | How it works | Good for | Watch out for |
|---|---|---|---|
Independent records | Each domain publishes its own full SPF record | Domains with different senders | Drift when you update one and forget others |
Redirect to a shared policy | Each domain publishes v=spf1 redirect=_spf.{brand}.com; the shared record holds the policy | Many domains with identical senders | The shared record's lookups count for every domain; the redirecting record can't also have its own all qualifier |
Shared include plus Microsoft | Each domain: v=spf1 include:spf.protection.outlook.com include:_spf.{brand}.com -all | A common set of third-party senders plus Microsoft | Lookups add up quickly |
A note on redirect: when a record uses redirect=, the shared record supplies the entire policy, including its all qualifier. That makes it ideal for identical domains, and a poor fit for a domain that needs one extra sender of its own.
For cold email outreach domains that send only from Microsoft 365, independent records are the simplest: each one is a single include, and there's nothing to share. The redirect and shared-include patterns earn their keep on brand domains where marketing, support, and billing tools all send.
Here's the advice we'd push back on: "Add include:{main-domain} to every other domain so they inherit its senders." It works, but every domain now carries all of the main domain's lookups — and any change to the main record silently changes all the others. A dedicated shared record is easier to reason about.
Staying Within the Lookup Limit Across Domains
Count per domain. The 10-lookup limit applies to each domain's evaluation, including nested includes and redirects.
Keep outreach domains minimal. One Microsoft include is enough when cold email tools connect by OAuth and send through Microsoft 365.
Move third-party senders to subdomains with their own SPF records.
Review shared records carefully — one extra include there affects every domain that uses it.
Re-check after vendors change their own includes; nested lookups can grow without you editing anything.
The single-domain basics, including the Google Workspace values, are in SPF record configuration for Google Workspace and Microsoft 365.
Auditing Every Domain at Once
Multi-domain SPF for Microsoft 365 needs regular checks, because drift is invisible until mail fails. A simple audit covers every domain in minutes.
List every domain in the tenant — from the Microsoft 365 admin center, or with Get-AcceptedDomain in Exchange Online PowerShell.
Look up each SPF record — for example, with Resolve-DnsName -Type TXT {domain} in PowerShell or dig +short {domain} TXT.
Flag problems: no record, more than one record, missing Microsoft include, or a parked domain without v=spf1 -all.
Count lookups for each domain with an SPF checker.
Fix and re-check, then send a test message from a mailbox on each changed domain.
Run the audit monthly, and after any DNS change. It fits naturally into the routine in how to monitor email infrastructure health.
A Worked Example: Twelve Domains in One Tenant
Here's how multi-domain SPF for Microsoft 365 might look for a company with one main brand domain, one regional domain, eight outreach domains, and two parked domains.
Domains | SPF approach | Record |
|---|---|---|
Main brand domain (CRM, help desk, and Microsoft 365 send) | Shared include for third parties plus Microsoft | v=spf1 include:spf.protection.outlook.com include:_spf.{brand}.com -all |
Regional domain (same tools as main) | Same shared include | Same as the main domain |
Eight outreach domains (Microsoft 365 only, tools via OAuth) | Independent minimal records | v=spf1 include:spf.protection.outlook.com -all |
Two parked domains | Deny all | v=spf1 -all |
news.{brand}.com (newsletter service) | Own record on the subdomain | The service's include only |
The outreach domains stay at a single lookup each. The brand domains share one maintained list of third-party senders. And the newsletter sender is isolated on its own subdomain, so its include never pushes the main domain over the limit.
Document this layout in your inventory. When a new tool is proposed, the question becomes simple: which group does it belong to? That one habit keeps multi-domain SPF for Microsoft 365 predictable as the domain count grows.
Adding a Third-Party Sender Without Breaking Anything
Confirm how the tool sends. If it sends through your Microsoft 365 mailboxes by OAuth, no SPF change is needed.
If it sends from its own servers, prefer giving it a subdomain with its own SPF record.
If it must use the main domain, add its include to the shared record, then count lookups for every domain that uses it.
Set up DKIM for the tool on the same domain, so DMARC can pass on DKIM even if SPF alignment doesn't.
Test and record the change in your inventory.
Following these steps keeps one new tool from quietly breaking SPF across a dozen domains.
Common Multi-Domain SPF Problems
Problem | Effect | Fix |
|---|---|---|
Domain added to the tenant with no SPF record | No SPF protection; weaker deliverability | Publish the baseline record |
Two SPF records on one domain | SPF permanent error | Merge into one |
Subdomain sending with no record | SPF none for that subdomain | Publish a record on the subdomain |
Shared record over 10 lookups | Every domain using it fails | Trim the shared record; move senders to subdomains |
Parked domains with no SPF | Easier to spoof | Publish v=spf1 -all |
Wrong include for a sovereign cloud | SPF fails for all mail | Use the cloud's documented include |
SPF is only one part of authentication. Each domain also needs DKIM enabled in Microsoft 365 — two CNAME records per domain — and a DMARC record; see the DKIM guide and DNS templates for Google Workspace and Microsoft 365. Keep complaints under 0.1%, per Google's email sender guidelines.
Litemail configures SPF, DKIM, and DMARC automatically on every domain for its Microsoft 365 and Google Workspace inboxes, so multi-domain outreach setups start valid.
Every domain authenticated from day one — Litemail Microsoft 365 inboxes come with SPF, DKIM, and DMARC configured on every domain, full admin access, OAuth export, dedicated US and EU IPs, and pre-warmed options. See Pre-Warmed Inbox Plans → About Litemail — Litemail provides pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated DNS, dedicated US and EU IPs, and full admin access. Pre-warmed plans start at $39/month for 5 inboxes; add-on inboxes go as low as $4.99/inbox on the Scale plan. View pre-warmed inbox plans →
Related reading: SPF Records for Google Workspace and Microsoft 365 · DKIM Guide · Set Up Multiple Domains for Cold Email · Microsoft 365 Inboxes
Key Takeaways
In multi-domain SPF for Microsoft 365, every custom domain and sending subdomain needs its own SPF record.
Baseline for commercial tenants: v=spf1 include:spf.protection.outlook.com -all.
Use independent records for simple outreach domains; use a redirect or shared include where many domains share the same senders.
Count lookups per domain — shared records and nested includes add up.
Publish v=spf1 -all on domains that don't send.
Audit every domain monthly and after DNS changes.
Frequently Asked Questions
Does one SPF record cover all domains in a Microsoft 365 tenant?
No. Each custom domain, and each sending subdomain, needs its own SPF record.
What SPF record should each Microsoft 365 domain use?
For commercial tenants sending only from Microsoft 365: v=spf1 include:spf.protection.outlook.com -all.
Can I share one SPF policy across many domains?
Yes. Each domain can use v=spf1 redirect= pointing to a shared record, or include a shared record alongside Microsoft's include. Count lookups carefully.
How do I audit multi-domain SPF for Microsoft 365?
List the tenant's domains, look up each SPF record, flag missing or duplicate records and lookup problems, fix them, and send test messages.
Do subdomains need their own SPF record in Microsoft 365?
Yes. Microsoft's documentation states the parent domain's SPF record doesn't cover subdomains.
What should unused domains publish?
v=spf1 -all, which tells receivers no mail should come from that domain.
Does Litemail handle SPF for multiple domains?
Yes. Litemail configures SPF, DKIM, and DMARC automatically on every domain for its Microsoft 365 and Google Workspace inboxes.
Many Domains, Every One Authenticated
Litemail inboxes come with SPF, DKIM, and DMARC configured on every domain, full admin access, dedicated US and EU IPs, and free domain replacement on pre-warmed plans.
Plans from $39/month · Microsoft 365 and Google Workspace · Setup in about 5 minutes
Buy Pre-Warmed Email Inboxes & Domains | Litemail — Pre-warmed Google Workspace and Microsoft 365 inboxes with automated DNS, US and EU IPs, and setup in about 5 minutes. Fresh inboxes from $2.50/inbox; pre-warmed from $4.99/inbox at scale. View plans and pricing →
Related reading: Microsoft 365 Pre-Warmed Accounts · Pre-Warmed Domains · Microsoft Cold Email Policy 2026 · Cold Email Deliverability Guide · Litemail Home · Plans and Pricing


