Prevent Microsoft 365 Domain Spoofing with SPF, DKIM, and DMARC
Question details
Reduce the risk of attackers sending messages that appear to come from a Microsoft 365 organization's email domain.

- Product
- Microsoft 365 and Exchange Online
- Device & OS
- not provided
- Scenario
- An organization wants to authenticate its outgoing email and help recipients identify messages that spoof its domain.
- Observed behavior
- The desired state is for legitimate senders to pass email authentication and for receiving servers to apply a DMARC policy to messages that fail authentication.
Confirm that you can edit the domain's DNS records and access the Microsoft 365 email authentication settings. List all services that send mail using the domain, including marketing and support platforms.
Configure SPF, DKIM, and DMARC for the sending domain
Use email authentication and a staged DMARC policy to reduce domain spoofing while protecting legitimate mail delivery.
In your DNS hosting provider's domain management console, inspect the existing SPF TXT record. Check your inventory for Microsoft 365 and any third-party services that send mail for the domain.
In the DNS console, edit the domain's existing SPF TXT record to authorize each legitimate sending service. If Microsoft 365 is the only sender, an example is "v=spf1 include:spf.protection.outlook.com -all". Keep only one SPF record for the domain and use the instructions from each additional sender to include it.
In the Microsoft Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings > DKIM. Select your domain and follow the displayed instructions to create the required DNS CNAME records, then return to enable DKIM signing after DNS updates propagate.
In the DNS console, add a TXT record at _dmarc for the domain, such as "v=DMARC1; p=none; rua=mailto:dmarc@example.com". Replace the example address with a mailbox that can receive and review aggregate DMARC reports.
Open the DMARC report mailbox and check that legitimate senders pass SPF or DKIM with domain alignment. Correct any missing sender configuration, then edit the _dmarc TXT record to move from p=none to p=quarantine and, when ready, p=reject.

Use WPS Office for everyday document work
WPS Office is a free, lightweight Office alternative with a familiar interface for working with documents, spreadsheets, and presentations. Its Microsoft Office format support helps you move existing files into your workflow. WPS Office does not configure Microsoft 365 email authentication.

Frequently Asked Questions
What does DMARC monitoring mode do?
A DMARC TXT record with p=none requests monitoring rather than quarantine or rejection. Add a rua address to receive aggregate reports and review them before enforcing a stricter policy.
Can I publish separate SPF records for Microsoft 365 and another sender?
No. A domain should have one SPF TXT record that includes all authorized sending services. Edit the existing record in your DNS console instead of adding a second SPF record.
Where do I find the DKIM records for my Microsoft 365 domain?
In the Microsoft Defender portal, open Email & collaboration > Policies & rules > Threat policies > Email authentication settings > DKIM, then select your domain. Follow the displayed instructions for the required CNAME records.
Will SPF, DKIM, and DMARC stop every spoofed email?
No. DMARC relies on receiving servers to apply the published policy and does not stop every impersonation technique. It helps receivers identify messages that fail authentication and domain alignment.
When should I change DMARC from p=none to p=reject?
Review aggregate reports first and confirm that legitimate services pass aligned SPF or DKIM. Move to p=quarantine, monitor the results, and use p=reject when you are confident legitimate mail is not being affected.




