Does Microsoft 365 SPF Allow Email Domain Spoofing?
Question details
Determine whether the Microsoft 365 SPF include allows another tenant to spoof a domain and how to strengthen email authentication.

- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- A domain owner uses Exchange Online and wants to understand the spoofing implications of including Microsoft's SPF record.
- Observed behavior
- The domain's SPF record includes spf.protection.outlook.com, authorizing the sending infrastructure covered by that include.
Identify every service that sends email for your domain and check its current SPF, DKIM, and DMARC DNS records. Make sure you can access the Microsoft 365 admin center and your domain's DNS provider.
Verify Your Domain and Configure SPF, DKIM, and DMARC
Use domain verification and layered email authentication to reduce spoofing risks while keeping legitimate mail working.
Including spf.protection.outlook.com authorizes the infrastructure covered by Microsoft's SPF record; it does not by itself let another Microsoft 365 tenant send as a domain it does not own. SPF checks the sending IP against the envelope sender's domain, not necessarily the visible From address.
SPF alone is not a complete anti-spoofing control, especially with shared sending infrastructure. DKIM and DMARC add authentication and alignment checks for the visible From domain.
In the Microsoft 365 admin center, go to Settings > Domains, select your domain, and confirm that it is verified. If it is not, follow the verification instructions to add the required DNS record.
In your DNS provider's domain settings, edit the existing SPF TXT record to include all legitimate senders. For a domain that sends only through Exchange Online, an example is "v=spf1 include:spf.protection.outlook.com -all". Keep only one SPF record for the domain and include any other authorized sending services before using -all.
In the Microsoft Defender portal, open Email & collaboration > Policies & rules > Threat policies > Email authentication settings, then select DKIM and your domain. Add the requested DNS records at your DNS provider, then enable DKIM signing for the domain.
At your DNS provider, add a TXT record for _dmarc.yourdomain.com. Start with a monitoring policy such as "v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com", using an address that can receive reports. Review the reports and move to p=quarantine or p=reject when legitimate senders authenticate and align correctly.
Send test messages from Exchange Online and each other authorized service to a mailbox where you can inspect message headers. Check the Authentication-Results header for SPF, DKIM, and DMARC results, and correct any failures before enforcing DMARC.

Document Your Email Security Policy in WPS Office
WPS Office is a free, lightweight alternative for writing and maintaining email security procedures in a familiar interface. Its Office format compatibility makes it easier to move existing documents and spreadsheets. WPS Office does not configure Microsoft 365 email authentication or fix Exchange Online spoofing risks.

Frequently Asked Questions
Can another Microsoft 365 tenant send as my domain because we both use Microsoft's SPF include?
Not merely because both domains include spf.protection.outlook.com. Exchange Online checks domain ownership, but SPF authorization alone is not a complete defense against spoofing. Use DKIM and DMARC alignment as additional controls.
Should I use -all in my Microsoft 365 SPF record?
You can use -all to indicate a hard fail for senders not authorized by your SPF record. First, list every legitimate sending service in the single SPF TXT record at your DNS provider; otherwise, legitimate messages may fail SPF.
Why do I need DMARC if SPF is configured?
SPF checks the envelope sender domain, which may differ from the visible From domain. DMARC checks whether SPF or DKIM passes with an aligned domain and lets you publish a policy for messages that fail alignment.
Where do I enable DKIM for my Microsoft 365 domain?
In the Microsoft Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings > DKIM. Select your domain, add the requested DNS records, and enable signing.




