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.

CriterionCorrect pickWrong pick to avoid
Standard sends BCL 6 bulk mail to Junk; it must go to quarantine instead, using only preset policiesAssign 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 protectionAdd an exclusion inside the Built-in protection preset itselfA 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 addedEnable-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

Traps