Troubleshoot Microsoft 365 SPF Validation Errors for Rejected Email
Question details
Determine why a recipient domain rejects Microsoft 365 email with an SPF validation error.

- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- Email sent to one recipient domain is rejected, while messages to other domains are delivered.
- Observed behavior
- The rejection identifies an unauthorized IPv6 sending address even though the published SPF record includes spf.protection.outlook.com and ends with -all.
Locate the complete non-delivery report and identify the domain used in the message's envelope sender or return path. Have access to that domain's DNS records, or contact its DNS administrator.
Trace the Sending Path and Verify the SPF Record
Use the rejection details to identify the server checked by the recipient and confirm that its sending service is authorized.
Open the non-delivery report in your mail client and save or forward the complete report privately to your administrator. In Outlook, you can save the message as an MSG file using File > Save As.
In the report, look for the rejected IPv6 address, the return-path or envelope-sender domain, and any diagnostic text identifying the server or service that sent the message.
In the Exchange admin center, open Mail flow > Message trace and search for the affected message. Compare the trace and available message headers with the reported address to identify any relay, forwarding service, or third-party sender in the path.
In your DNS provider's management console, inspect the SPF TXT record for the envelope-sender domain. Confirm that it authorizes every legitimate sending service, including Microsoft 365, and that the domain has only one SPF record. If another service sent the message, follow that provider's instructions to add its authorization to the existing record.

Test the Recipient Domain and Review Its Filtering
Use comparison tests and the recipient's logs to determine whether the rejection is specific to the sender or the recipient's policy.
Work With Office Documents While You Resolve Email Delivery
WPS Office is a free, lightweight alternative with a familiar interface and Microsoft Office format compatibility, making it easier to move your document work between suites. SPF validation and email routing must still be resolved with your mail and DNS administrators.

Frequently Asked Questions
Why does email fail SPF for only one recipient domain?
Recipient domains can apply different filtering policies. Ask the affected recipient's administrator to check their SPF result and filtering logs for the reported sending address.
Does the Microsoft 365 SPF include authorize every email service I use?
No. The include:spf.protection.outlook.com mechanism covers Microsoft 365's designated sending infrastructure, but other relays or third-party services may require separate authorization in the same SPF record.
Which domain's SPF record should I check?
Check the envelope-sender domain shown in the return path or rejection details. It can differ from the visible From address, particularly when forwarding or another sending service is involved.
Should I add the rejected IPv6 address to my SPF record?
Only after confirming that the address belongs to a legitimate sending service you use. Check the non-delivery report, message trace, and service provider's SPF guidance before editing the DNS TXT record.
Can WPS Office fix a Microsoft 365 SPF rejection?
No. SPF is evaluated using DNS records and the email sending path. Use the Exchange admin center, your DNS provider's console, and the recipient's filtering logs to investigate the rejection.




