Description
In every anti-phishing policy (the default policy, custom policies and the preset policies), the
spoof setting Honor DMARC record policy when the message is detected as spoof is on
(HonorDmarcPolicy $true), with:
p=quarantinefailures: Quarantine the message (DmarcQuarantineAction Quarantine);p=rejectfailures: Reject the message (DmarcRejectAction Reject).
Spoof intelligence stays enabled (EnableSpoofIntelligence $true).
Rationale
A domain owner who publishes p=reject states that unauthenticated mail with its domain is
forged. Honoring that policy stops the forgery at the door instead of moving it to Junk Email,
where users still find and open it. This setting is part of Exchange Online Protection and needs no
extra license.
Impact
None known for well-configured senders. Messages from domains with broken authentication and an enforcing DMARC policy are quarantined or rejected; senders of legitimate mail can be allowed through the spoof intelligence insight.
Audit
- Sign in to the Microsoft Defender portal (https://security.microsoft.com) as at least a Security Reader.
- Browse to Email & collaboration > Policies & rules > Threat policies > Anti-phishing and open each policy (Office365 AntiPhish Default and custom policies).
- Under Actions, check that Honor DMARC record policy when the message is detected as
spoof is selected, with Quarantine the message for
p=quarantineand Reject the message forp=reject. - In Exchange Online PowerShell (read-only):
Get-AntiPhishPolicy | Format-Table Name, Enabled, EnableSpoofIntelligence, HonorDmarcPolicy, DmarcQuarantineAction, DmarcRejectAction - Fail if a policy that applies to users has
HonorDmarcPolicyset toFalse, or a weaker action than the ones above.
Remediation
- In the Defender portal, open each anti-phishing policy > Actions > Edit actions.
- Select Honor DMARC record policy when the message is detected as spoof, choose Quarantine the message and Reject the message, and save.
- PowerShell equivalent (Security Administrator):
(The preset policies cannot be edited and already use these values.)Get-AntiPhishPolicy | Set-AntiPhishPolicy -EnableSpoofIntelligence $true -HonorDmarcPolicy $true ` -DmarcQuarantineAction Quarantine -DmarcRejectAction Reject
Rollback
Set-AntiPhishPolicy -Identity <policy> -HonorDmarcPolicy $false.
References
- Anti-phishing policies in Microsoft 365 Microsoft, vendor-doc, accessed 2026-10-24
- Recommended settings for EOP and Microsoft Defender for Office 365 security Microsoft, vendor-doc, accessed 2026-10-24
- ORCA - Office 365 Recommended Configuration Analyzer (check ORCA-244) Microsoft (community project), tool, accessed 2026-10-24
Mappings
| Framework | ID | Relation |
|---|---|---|
| NIST SP 800-53 Rev. 55.1.1 | SI-8 | related |
How this control relates to the other framework's: equivalent, stricter, looser, partial or related.
Threats mitigated
| Taxonomy | ID |
|---|---|
| MITRE ATT&CK | T1566 |
Related controls
- related
CB-M365-MAIL-016Publish an enforcing DMARC policy with reporting for every domain - related
CB-M365-MAIL-018Configure Enhanced Filtering and trusted ARC sealers behind a third-party mail gateway - related
CB-M365-MAIL-029Configure anti-phishing impersonation protection, mailbox intelligence and safety tips
People and lifecycle
| Authors |
|
| Introduced in | v0.1.0 |
| Created, updated | 2026-10-24, 2026-10-24 |
| Translations | fr |