Security Policy Errors

Block Domain-Spoofing Phishing Emails in Exchange Online

Camila MilosovichCamila Milosovich Nov 20, 2026 869 views

Question details

Reduce phishing emails that impersonate an organization's domain in a hybrid Exchange environment.

Block Domain-Spoofing Phishing Emails in Exchange Online
Product
Exchange Online and Exchange Online Protection
Device & OS
not provided
Scenario
The organization wants to authenticate legitimate senders and filter inbound messages that spoof its domain.
Observed behavior
DKIM signs authorized outbound messages, but attackers can still send unauthenticated messages that appear to come from the organization's domain.
Before you start

List every service authorized to send mail for the domain, and check the domain's current SPF, DKIM, DMARC, and MX DNS records. Confirm whether inbound internet mail reaches Exchange Online Protection directly or passes through another gateway or on-premises Exchange first.

Solution 1Recommended

Configure SPF, DKIM, and DMARC for the domain

Use domain authentication and an enforced DMARC policy to help receiving systems identify and handle unauthorized messages.

1
Review authorized senders

In your DNS provider's management console, inspect the domain's existing SPF TXT record and identify all legitimate sending services, including on-premises servers and third-party platforms.

2
Update the SPF record

Edit the domain's single SPF TXT record to include all authorized senders and end it with an appropriate failure mechanism, such as -all. Keep the record within SPF DNS lookup limits.

3
Enable DKIM signing

In the Microsoft Defender portal, go to Email & collaboration > Policies & rules > Threat policies > Email authentication settings > DKIM. Select the domain, publish any requested DNS records, and enable signing. Configure DKIM separately for other legitimate sending services.

4
Publish and enforce DMARC

At your DNS provider, publish a TXT record at _dmarc.yourdomain with a reporting address. Start with p=none to review authentication and alignment results, then move to p=quarantine or p=reject after legitimate senders are correctly configured.

Configure SPF, DKIM, and DMARC for the domain
DMARC enforcement depends on the receiver: DMARC requires SPF or DKIM to pass and align with the visible From domain. Receiving systems decide how to apply the domain's policy; publishing it does not prevent an attacker from sending spoofed mail.
Free Microsoft Office alternative

Document your email security policies with WPS Office

WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility for an easier transition. Use it to maintain sender inventories and security policy documents; Exchange Online protection must still be configured in Microsoft.

Organize authorized sender inventories and email security review notes.Open and edit Microsoft Word DOCX and Excel XLSX files.Use familiar document and spreadsheet tools with a lightweight interface.Move existing Office documents into WPS without starting from scratch.
microsoft office alternative - wps office

Frequently Asked Questions

Why can someone spoof my domain even though DKIM is enabled?

DKIM signs messages sent by configured services; it does not stop an attacker from sending unsigned mail with your domain in the From address. Publish DMARC and configure receiving-side anti-spoofing policies to help identify and handle those messages.

Should I set DMARC to reject immediately?

First publish a DMARC TXT record with p=none and a reporting address, then review whether legitimate services pass SPF or DKIM with alignment. Move to quarantine or reject after correcting authorized senders to reduce the risk of legitimate mail being rejected.

Where can I check how a spoofed message reached a mailbox?

In the Exchange admin center, go to Mail flow > Message trace and search for the message. Review its Received and Authentication-Results headers to check the route and authentication results.

Does my MX record matter in a hybrid Exchange setup?

Yes. The MX record determines where inbound internet mail is initially delivered. Check it in your DNS console, then review any gateway and Exchange connectors to ensure messages are inspected before delivery.

Can I publish a separate SPF record for each sending service?

No. Use one SPF TXT record for the domain and include all authorized senders in that record. Check the combined record against SPF DNS lookup limits.