Defender preset security policies: which one, and how to change it
Verdict: Assign Strict, not a Standard edit, to send BCL 6 bulk mail to quarantine - individual preset settings can't be changed. Exclude unlicensed mailboxes inside Built-in protection itself. Re-enabling Standard in PowerShell needs both the EOP and ATP protection-policy-rule cmdlets.
| Criterion | Correct pick | Wrong pick to avoid |
|---|---|---|
| Standard sends BCL 6 bulk mail to Junk; it must go to quarantine instead, using only preset policies | Assign the Strict preset instead of Standard (Strict's bulk threshold is 5, and it quarantines) | Edit the bulk email threshold inside Standard, or add a custom anti-spam policy alongside it (individual preset settings can't be edited; preset policies take precedence over custom ones) |
| Some mailboxes lack Defender for Office 365 licences and must stop receiving Built-in protection | Add an exclusion inside the Built-in protection preset itself | A recipient condition on Standard (adds licence-dependent protection instead), or a custom Safe Attachments policy scoped to exclude those mailboxes (they stay in Built-in protection's scope) |
| Re-enable the Standard preset in Exchange Online PowerShell after Defender for Office 365 was added | Enable-EOPProtectionPolicyRule AND Enable-ATPProtectionPolicyRule, both against "Standard Preset Security Policy" | Running only one of the two cmdlets, or New-AntiPhishPolicy/Set-HostedContentFilterPolicy (wrong cmdlets entirely) |
Rules
- Assign the Strict preset, not a Standard edit, to send BCL 6 bulk mail to quarantine instead of Junk - Strict's bulk threshold is 5, Standard's is 6.
- Individual settings inside a preset security policy cannot be edited; changing behaviour means assigning a different preset.
- Add an exclusion inside the Built-in protection preset itself to stop it covering mailboxes without Defender for Office 365 licences.
- Re-enabling Standard in PowerShell after adding Defender for Office 365 needs both Enable-EOPProtectionPolicyRule and Enable-ATPProtectionPolicyRule against the "Standard Preset Security Policy" identity.
Traps
- Candidates try to edit the bulk-email threshold inside Standard directly; individual preset-policy settings can't be changed, only a different preset can be assigned.
- Candidates add a recipient condition to Standard, or a custom Safe Attachments policy scoped to exclude the mailboxes, expecting that to drop them from Built-in protection; an exclusion inside Built-in protection itself is the documented route. Note: recipients actually included in Standard/Strict or in a custom Safe Links/Safe Attachments policy ARE outside Built-in protection's scope, but that gives them protection they aren't licensed for, not the removal wanted here.
- Candidates run only one of the two Defender for Office 365 re-enable cmdlets and leave Safe Links or Safe Attachments still off; both cmdlets are needed.