Investigate Office 365 SPF Warnings for Third-Party SMTP Email
Question details
The user needs to understand why Office 365 displays a fraud warning for same-domain email sent through a third-party SMTP service.

- Product
- Microsoft 365 Exchange Online
- Device & OS
- not provided
- Scenario
- An organization sends email from and to its own domain through a third-party SMTP provider that is included in its SPF record.
- Observed behavior
- Office 365 displays a fraud-detection warning despite the third-party service being included in the domain's SPF record.
Obtain a sample message that displays the warning and access to its complete headers. Have an administrator available to review the domain's DNS records and Exchange Online mail flow settings.
Inspect Message Headers and Authentication Results
Use a flagged message to identify the sending path and determine which authentication or spoofing checks may have triggered the warning.
An SPF pass alone does not guarantee that a message will pass DMARC or avoid a spoofing warning. SPF typically checks the envelope sender domain, which may differ from the visible From domain.
In classic Outlook, open the flagged message, select File > Properties, and copy the Internet headers. In Outlook on the web or new Outlook, open the message and use the More actions menu to find View message details.
In the headers, find Authentication-Results and review the SPF, DKIM, and DMARC results. Compare the domains identified in those results with the domain in the visible From address.
Review the Received headers to identify the third-party SMTP service and the servers that relayed the message before it reached Microsoft 365. Check whether the path matches the intended mail flow.
Use the header results and the warning text to investigate failures or spoofing findings in the Microsoft Defender portal. If the cause remains unclear, provide a sample header to Microsoft support through an approved private channel.

Review SPF, Domain Alignment, and Mail Flow Connectors
Use this review when the headers suggest an unexpected sending route, authentication failure, or domain alignment issue.
Use WPS Office for Everyday Document Work
WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility for a seamless move between document tools. It does not change Exchange Online mail flow or fix SPF warnings.

Frequently Asked Questions
Why can Office 365 flag a message even when SPF passes?
SPF validates an authorized sender for the envelope domain, which may differ from the visible From domain. DKIM, DMARC alignment, spoofing detection, and the message's sending path can also affect the warning.
Where can I find the authentication results for a flagged message?
Open the complete message headers and look for Authentication-Results. In classic Outlook, open the message and select File > Properties to find Internet headers.
Should I add the SMTP provider to my SPF record?
If the provider sends mail using your envelope sender domain, check its documentation and your DNS SPF TXT record to confirm it is authorized. Avoid creating a second SPF record for the same domain.
Where can an administrator check the mail flow connector?
In the Exchange admin center, go to Mail flow > Connectors and review any connector involved in the third-party SMTP route. Compare its settings with the intended mail flow and the provider's instructions.
Will WPS Office remove the Exchange Online fraud warning?
No. WPS Office is an alternative for document work; the warning must be investigated in Microsoft 365, the SMTP provider's settings, and the domain's DNS records.




