New-QuarantinePermissions
This cmdlet is available only in the cloud-based service.
Use the New-QuarantinePermissions cmdlet to create quarantine permissions objects to use with the EndUserQuarantinePermission parameter on the New-QuarantinePolicy or Set-QuarantinePolicy cmdlets.
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax.
Syntax
New-QuarantinePermissions
[[-PermissionToAllowSender] <Boolean>]
[[-PermissionToBlockSender] <Boolean>]
[[-PermissionToDelete] <Boolean>]
[[-PermissionToDownload] <Boolean>]
[[-PermissionToPreview] <Boolean>]
[[-PermissionToRelease] <Boolean>]
[[-PermissionToRequestRelease] <Boolean>]
[[-PermissionToViewHeader] <Boolean>]
[<CommonParameters>] Description
The default value for any parameters that you don't use is $false, so you only need to use parameters (permissions) that you want to set to $true.
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.
Examples
Example 1
$NoAccess = New-QuarantinePermissionsThis 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.
In the same Windows PowerShell session, you can use $NoAccess for the EndUserQuarantinePermissions parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command.
Example 2
$LimitedAccess = New-QuarantinePermissions -PermissionToBlockSender $true -PermissionToDelete $true -PermissionToPreview $true -PermissionToRequestRelease $trueThis 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.
In the same Windows PowerShell session, you can use $LimitedAccess for the EndUserQuarantinePermissions parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command.
Example 3
$FullAccess = New-QuarantinePermissions -PermissionToBlockSender $true -PermissionToDelete $true -PermissionToPreview $true -PermissionToRelease $trueThis 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.
In the same Windows PowerShell session, you can use $FullAccess for the EndUserQuarantinePermissions parameter value in a New-QuarantinePolicy or Set-QuarantinePolicy command.
Parameters
-PermissionToAllowSender
The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Safe Senders list. Valid values are:
- $true: Allow sender is available for affected messages in quarantine.
- $false: Allow sender isn't available for affected messages in quarantine. This is the default value.
| Type: | Boolean |
| Position: | 1 |
| Default value: | False |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-PermissionToBlockSender
The PermissionToBlockSender parameter specifies whether users are allowed to add the quarantined message sender to their Blocked Senders list. Valid values are:
- $true: Block sender is available in quarantine notifications for affected messages, and Block sender is available for affected messages in quarantine.
- $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.
| Type: | Boolean |
| Position: | 2 |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-PermissionToDelete
The PermissionToDelete parameter specifies whether users are allowed to delete messages from quarantine. Valid values are:
- $true: Delete messages and Delete from quarantine are available for affected messages in quarantine.
- $false: Delete messages and Delete from quarantine aren't available for affected messages in quarantine. This is the default value.
| Type: | Boolean |
| Position: | 3 |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-PermissionToDownload
The PermissionToDownload parameter specifies whether users are allowed to download messages from quarantine. Valid values are:
- $true: The permission is enabled.
- $false: The permission is disabled. This is the default value.
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.
| Type: | Boolean |
| Position: | 4 |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-PermissionToPreview
The PermissionToPreview parameter specifies whether users are allowed to preview quarantined messages. Valid values are:
- $true: Preview message is available for affected messages in quarantine.
- $false: Preview message isn't available for affected messages in quarantine. This is the default value.
| Type: | Boolean |
| Position: | 5 |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-PermissionToRelease
The PermissionToRelease parameter specifies whether users are allowed to directly release affected messages from quarantine. Valid values are:
- $true: Release is available in quarantine notifications for affected messages, and Release (Release email) is available for affected messages in quarantine.
- $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.
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.
| Type: | Boolean |
| Position: | 6 |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-PermissionToRequestRelease
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:
- $true: Request Release is available in quarantine notifications for affected messages, and Request release is available for affected messages in quarantine.
- $false: Request Release isn't available in quarantine notifications for affected messages, and Request release isn't available for affected messages in quarantine.
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.
| Type: | Boolean |
| Position: | 7 |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
-PermissionToViewHeader
The PermissionToViewHeader parameter specifies whether users are allowed to view the message headers of quarantined messages. Valid values are:
- $true: The permission is enabled.
- $false: The permission is disabled. This is the default value.
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.
| Type: | Boolean |
| Position: | 8 |
| Default value: | None |
| Required: | False |
| Accept pipeline input: | False |
| Accept wildcard characters: | False |
| Applies to: | Exchange Online, Exchange Online Protection |
Tilbakemeldinger
Kommer snart: Gjennom 2024 faser vi ut GitHub Issues som tilbakemeldingsmekanisme for innhold, og erstatter det med et nytt system for tilbakemeldinger. Hvis du vil ha mer informasjon, kan du se: https://aka.ms/ContentUserFeedback.
Send inn og vis tilbakemelding for