You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: defender-office-365/quarantine-quarantine-notifications.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -82,7 +82,7 @@ The actions that are available for messages in the quarantine notification depen
82
82
83
83
-**Request release**: Available for messages that were quarantined by features using a quarantine policy with the **Limited access** permission group or the individual **Allow recipients to request a message to be released from quarantine** (_PermissionToRequestRelease_) permission. For example, custom quarantine policies.
84
84
85
-
Selecting the action opens an informational web page that acknowledges the request to release the message from quarantine (**The message release request has been initiated. The tenant admin will determine if the request should be approved or denied.**). The **Release status** value of the message on the **Email** tab of the **Quarantine** page is **Release requested**.
85
+
Selecting the action opens an informational web page that acknowledges the request to release the message from quarantine (**The message release request has been initiated. The tenant admin will determine if the request should be approved or denied.**). The **Release status** value of the message on the **Email** tab of the **Quarantine** page is **Release requested**. The "Request to release quarantined message" is sent by default to the "TenantAdmin" hidden group - all users with admin privileges. This can be configured within **Threat Policies** > **Alert Policies** through the web portal, but configuring via PowerShell cannot be done without an Enterprise license.
86
86
87
87
-**Block Sender**: Available for messages that were quarantined by features using a custom quarantine policy with the **Block sender** (_PermissionToBlockSender_) permission.
0 commit comments