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: exchange/exchange-ps/exchange/New-QuarantinePermissions.md
+21-18Lines changed: 21 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available only in the cloud-based service.
16
16
17
-
Use the New-QuarantinePermissions cmdlet to create quarantine permissions objects to use with the New-QuarantinePolicy cmdlet.
17
+
Use the New-QuarantinePermissions cmdlet to create quarantine permissions objects to use with the EndUserQuarantinePermission parameter on the New-QuarantinePolicy or Set-QuarantinePolicy cmdlets.
18
18
19
19
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20
20
@@ -45,7 +45,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
45
45
$NoAccess = New-QuarantinePermissions
46
46
```
47
47
48
-
This example creates the same permissions that are used by the No access permissions group in quarantine tags in the Security & Compliance. The permissions object is stored in the variable named `$NoAccess`.
48
+
This example creates the same permissions that are used by the No access permissions group in quarantine policies. The permissions object is stored in the variable named `$NoAccess`.
49
49
50
50
In the same Windows PowerShell session, you can use `$NoAccess` for the _EndUserQuarantinePermissions_ parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command.
51
51
@@ -54,7 +54,7 @@ In the same Windows PowerShell session, you can use `$NoAccess` for the _EndUser
This example creates the same permissions that are used by the Limited access permissions group in quarantine tags in the Security & Compliance. The permissions object is stored in the variable named `$LimitedAccess`.
57
+
This example creates the same permissions that are used by the Limited access permissions group in quarantine policies. The permissions object is stored in the variable named `$LimitedAccess`.
58
58
59
59
In the same Windows PowerShell session, you can use `$LimitedAccess` for the _EndUserQuarantinePermissions_ parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command.
60
60
@@ -63,14 +63,17 @@ In the same Windows PowerShell session, you can use `$LimitedAccess` for the _En
This example creates the same permissions that are used by the Full access permissions group in quarantine tags in the Security & Compliance. The permissions object is stored in the variable named `$FullAccess`.
66
+
This example creates the same permissions that are used by the Full access permissions group in quarantine policies. The permissions object is stored in the variable named `$FullAccess`.
67
67
68
68
In the same Windows PowerShell session, you can use `$FullAccess` for the _EndUserQuarantinePermissions_ parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command.
69
69
70
70
## PARAMETERS
71
71
72
72
### -PermissionToAllowSender
73
-
{{ Fill PermissionToAllowSender Description }}
73
+
The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are:
74
+
75
+
- $true: Allow sender is available for affected messages in quarantine.
76
+
- $false: Allow sender isn't available for affected messages in quarantine. This is the default value.
The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are:
90
93
91
-
- $true: The Block sender button is included in end-user quarantine notifications.
92
-
- $false: The Block sender button is not included in end-user quarantine notifications. This is the default value.
94
+
- $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine.
95
+
- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value.
The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are:
109
112
110
-
- $true: The Remove from quarantine button is included in the quarantined message details.
111
-
- $false: The Remove from quarantine button is not included in the quarantined message details. This is the default value.
113
+
- $true: Delete messages and Delete from quarantine are available for affected messages in quarantine.
114
+
- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value.
112
115
113
116
```yaml
114
117
Type: Boolean
@@ -129,7 +132,7 @@ The PermissionToDownload parameter specifies whether users are allowed to downlo
129
132
- $true: The permission is enabled.
130
133
- $false: The permission is disabled. This is the default value.
131
134
132
-
Currently, this value has no effect on the buttons that are included in end-user spam notifications or in quarantined message details.
135
+
Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages.
The PermissionToRelease parameter specifies whether users are allowed to directly release messages from quarantine. Valid values are:
170
+
The PermissionToRelease parameter specifies whether users are allowed to directly release affected messages from quarantine. Valid values are:
168
171
169
-
- $true: The Release button is included in end-user spam notifications, and the Release message button is included in the quarantined message details.
170
-
- $false: The Release button is not included in end-user spam notifications, and the Release message button is not included in the quarantined message details. This is the default value.
172
+
- $true: Release is available in quarantine notifications for affected messages, and Release (Release email) is available for affected messages in quarantine.
173
+
- $false: Release message isn't available in quarantine notifications for affected messages, and Release and Release email aren't available for affected messages in quarantine.
171
174
172
175
Don't set this parameter and the _PermissionToRequestRelease_ parameter to $true. Set one parameter to $true and the other to $false, or set both parameters to $false.
The PermissionToRequestRelease parameter specifies whether users are allowed to request messages to be released from quarantine. The request must be approved by an admin. Valid values are:
189
192
190
-
- $true: The Release button is included in end-user spam notifications, and the Release message button is included in the quarantined message details.
191
-
- $false: The Release button is not included in end-user spam notifications, and the Release message button is not included in the quarantined message details. This is the default value.
193
+
- $true: Request Release is available in quarantine notifications for affected messages, and Request release is available for affected messages in quarantine.
194
+
- $false: Request Release isn't available in quarantine notifications for affected messages, and Request release isn't available for affected messages in quarantine.
192
195
193
196
Don't set this parameter and the _PermissionRelease_ parameter to $true. Set one parameter to $true and the other to $false, or set both parameters to $false.
194
197
@@ -211,7 +214,7 @@ The PermissionToViewHeader parameter specifies whether users are allowed to view
211
214
- $true: The permission is enabled.
212
215
- $false: The permission is disabled. This is the default value.
213
216
214
-
Currently, this value has no effect on the buttons that are included in end-user spam notifications or in quarantined message details. The View message header button is always available in the quarantined message details.
217
+
Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine.
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Set-QuarantinePermissions.md
+20-17Lines changed: 20 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available only in the cloud-based service.
16
16
17
-
Use the Set-QuarantinePermissions cmdlet to modify quarantine permissions objects that are used in quarantine tags (the New-QuarantinePolicy or Set-QuarantinePolicy cmdlets). This cmdlet only works on permissions objects that were created by the New-QuarantinePermissions cmdlet and stored in a variable that's currently available in the Windows PowerShell session.
17
+
Use the New-QuarantinePermissions cmdlet to modify quarantine permissions objects to use with the EndUserQuarantinePermission parameter on the New-QuarantinePolicy or Set-QuarantinePolicy cmdlets. This cmdlet works only on a permission object that was created by the New-QuarantinePermissions cmdlet and stored in a variable that's currently available in the Windows PowerShell session.
18
18
19
19
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
To see the current value of the permissions object that you want to modify, run the variable name as a command. For example, run the command `$Perms` to see the quarantine tag permissions stored in the `$Perms` variable.
37
+
To see the current value of the permissions object that you want to modify, run the variable name as a command. For example, run the command `$Perms` to see the quarantine policy permissions stored in the `$Perms` variable.
38
38
39
39
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see [Find the permissions required to run any Exchange cmdlet](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions).
40
40
@@ -45,7 +45,7 @@ You need to be assigned permissions before you can run this cmdlet. Although thi
This example modifies the specified quarantine tag permissions in the exiting `$Perms` permissions object that was created previously in the same Windows PowerShell session (the `$Perms` variable is still available and populated).
48
+
This example modifies the specified quarantine policy permissions in the exiting `$Perms` permissions object that was created previously in the same Windows PowerShell session (the `$Perms` variable is still available and populated).
49
49
50
50
In the same Windows PowerShell session, you can use `$Perms` for the _EndUserQuarantinePermissions_ parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command.
The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are:
72
+
73
+
- $true: Allow sender is available for affected messages in quarantine.
74
+
- $false: Allow sender isn't available for affected messages in quarantine. This is the default value.
The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are:
88
91
89
-
- $true: The Block sender button is included in end-user quarantine notifications.
90
-
- $false: The Block sender button is not included in end-user quarantine notifications. This is the default value.
92
+
- $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine.
93
+
- $false: Block sender isn't available in quarantine notifications for affected messages, and Block sender isn't available for affected messages in quarantine. This is the default value.
The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are:
107
110
108
-
- $true: The Remove from quarantine button is included in the quarantined message details.
109
-
- $false: The Remove from quarantine button is not included in the quarantined message details. This is the default value.
111
+
- $true: Delete messages and Delete from quarantine are available for affected messages in quarantine.
112
+
- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value.
110
113
111
114
```yaml
112
115
Type: Boolean
@@ -127,7 +130,7 @@ The PermissionToDownload parameter specifies whether users are allowed to downlo
127
130
- $true: The permission is enabled.
128
131
- $false: The permission is disabled. This is the default value.
129
132
130
-
Currently, this value has no effect on the buttons that are included in end-user spam notifications or in quarantined message details.
133
+
Currently, this value has no effect on the available actions in quarantine notifications or quarantine for affected messages. End-users can't download quarantined messages.
The PermissionToRelease parameter specifies whether users are allowed to directly release messages from quarantine. Valid values are:
168
+
The PermissionToRelease parameter specifies whether users are allowed to directly release affected messages from quarantine. Valid values are:
166
169
167
-
- $true: The Release button is included in end-user spam notifications, and the Release message button is included in the quarantined message details.
168
-
- $false: The Release button is not included in end-user spam notifications, and the Release message button is not included in the quarantined message details. This is the default value.
170
+
- $true: Release is available in quarantine notifications for affected messages, and Release (Release email) is available for affected messages in quarantine.
171
+
- $false: Release message isn't available in quarantine notifications for affected messages, and Release and Release email aren't available for affected messages in quarantine.
169
172
170
173
Don't set this parameter and the _PermissionToRequestRelease_ parameter to $true. Set one parameter to $true and the other to $false, or set both parameters to $false.
The PermissionToRequestRelease parameter specifies whether users are allowed to request messages to be released from quarantine. The request must be approved by an admin. Valid values are:
187
190
188
-
- $true: The Release button is included in end-user spam notifications, and the Release message button is included in the quarantined message details.
189
-
- $false: The Release button is not included in end-user spam notifications, and the Release message button is not included in the quarantined message details. This is the default value.
191
+
- $true: Request Release is available in quarantine notifications for affected messages, and Request release is available for affected messages in quarantine.
192
+
- $false: Request Release isn't available in quarantine notifications for affected messages, and Request release isn't available for affected messages in quarantine.
190
193
191
194
Don't set this parameter and the _PermissionRelease_ parameter to $true. Set one parameter to $true and the other to $false, or set both parameters to $false.
192
195
@@ -209,7 +212,7 @@ The PermissionToViewHeader parameter specifies whether users are allowed to view
209
212
- $true: The permission is enabled.
210
213
- $false: The permission is disabled. This is the default value.
211
214
212
-
Currently, this value has no effect on the buttons that are included in end-user spam notifications or in quarantined message details. The View message header button is always available in the quarantined message details.
215
+
Currently, this value has no effect on available actions in quarantine notifications or quarantine for affected messages. View message header is always available for affected messages in quarantine.
0 commit comments