Skip to content

The right SPF record for Microsoft 365 and Google Workspace

SPF is one TXT record that lists who may send email for your domain. It's short, but small mistakes make it fail silently.

Google Workspace gets checks, alerts, app discovery, phishing practice, licenses, time machine and log questions like Microsoft 365, checked daily (on Protect, Microsoft 365 is also rechecked within minutes when a watched setting changes), with sign-ins and admin changes watched every 15 minutes on both. Baselines and "changed outside TenantWard" work for both: for Google Workspace, groups, calendars and mailbox forwarding are put back automatically, while its policy settings (2-Step Verification, Drive sharing, forwarding, less secure apps) are told, not put back, because Google doesn't let other apps change them; TenantWard shows what to change and where. Staged sign-in policies and locking an account on its own are Microsoft 365 only for now.

Updated October 4, 2026

The records

Each include is a sender. Add the include your other services document, such as your CRM, helpdesk or invoicing tool.

Microsoft 365:     v=spf1 include:spf.protection.outlook.com -all
Google Workspace:  v=spf1 include:_spf.google.com ~all
Both, plus a newsletter tool:
                   v=spf1 include:spf.protection.outlook.com include:_spf.google.com include:servers.mcsv.net ~all

Common mistakes

  • Two SPF records on the same domain. There must be exactly one TXT record starting with v=spf1; merge them
  • More than 10 DNS lookups. Each include, a, mx and redirect counts, including nested ones. Past 10, SPF returns a permanent error
  • Using +all, which lets anyone send as you
  • Forgetting a sender, so its mail fails SPF and, once DMARC is set to quarantine or reject, gets rejected
  • Leaving old includes for services you no longer use

~all or -all?

~all (soft fail) asks receivers to accept but treat failures with suspicion. -all (hard fail) says anything not listed isn't you. Once DMARC is set to quarantine or reject, the DMARC policy decides what happens, so either works; -all is the stricter signal once you're confident the list is complete.

Doing it with TenantWard

TenantWard reads your SPF, counts lookups, spots duplicates and proposes a corrected record. With your DNS host connected it publishes the change, keeps the previous value and can undo it.

Questions

What is the SPF record for Microsoft 365?
v=spf1 include:spf.protection.outlook.com -all, plus an include for any other service that sends email as your domain.
What is the SPF record for Google Workspace?
v=spf1 include:_spf.google.com ~all, plus an include for any other service that sends email as your domain.

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.