Forum Discussion
Enable Quarantine Notifications for Strict protection (Strict Preset Security Policy)
- Well, the DefaultFullAccessPolicy quarantine policy has notifications disabled, and you cannot toggle that. And I guess it overrides the notification settings within the Strict policy. So create a new policy (or use the NotificationEnabledPolicy) and change the settings via PowerShell:
[18:12:54][O365]# Set-HostedContentFilterPolicy "Strict Preset Security*" -PhishQuarantineTag NotificationEnabledPolicy
WARNING: All recommended properties will be controlled by Microsoft.
[18:13:00][O365]# Get-HostedContentFilterPolicy "Strict Preset Security*" | fl PhishQuarantineTag
PhishQuarantineTag : NotificationEnabledPolicy
Rinse and repeat for all other actions as needed.
Kiril-- It can't be done; those things are backed in. But there's nothing in the "Strict" or "Standard" policies that you can't duplicate by creating a new policy yourself that includes user notification. I did that when I realized I would have to release all the junk from quarantine myself -- no way was that happening.
You can use PowerShell to modify some parts of the Standard and Strict preset policies.
This command show you which policy is applied for a High confidence spam message action:
Get-HostedContentFilterPolicy "Strict Preset Security Policy Name" | fl Name,HighConfidenceSpamAction,HighConfidenceSpamQuarantineTagNow, if you have a Quarantine policy with notifications enabled (e.g. NotificationEnablePolicy) you can update the preset policy:
Set-HostedContentFilterPolicy "Strict Preset Security Policy Name" -HighConfidenceSpamQuarantineTag NotificationEnablePolicyAS at April 2023 any attempted adjustments to Standard or strict presets produces the following output...
WARNING: All recommended properties will be controlled by Microsoft.
and no changes are made
- The output was also displayed Dec 2022. Changes made using PowerShell still work though. I assume the Notification is not part of the recommended properties.
