Changes for Allow sender

Author: chrisda

exchange/exchange-ps/exchange/New-QuarantinePermissions.md

@@ -51,7 +51,7 @@ In the same Windows PowerShell session, you can use `$NoAccess` for the _EndUser
 
 ### Example 2
 ```powershell
-$LimitedAccess = New-QuarantinePermissions -PermissionToBlockSender $true -PermissionToDelete $true -PermissionToPreview $true -PermissionToRequestRelease $true
+$LimitedAccess = New-QuarantinePermissions -PermissionToAllowSender $true -PermissionToDelete $true -PermissionToPreview $true -PermissionToRequestRelease $true
 ```
 
 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`.
@@ -60,7 +60,7 @@ In the same Windows PowerShell session, you can use `$LimitedAccess` for the _En
 
 ### Example 3
 ```powershell
-$FullAccess = New-QuarantinePermissions -PermissionToBlockSender $true -PermissionToDelete $true -PermissionToPreview $true -PermissionToRelease $true
+$FullAccess = New-QuarantinePermissions -PermissionToAllowSender $true -PermissionToDelete $true -PermissionToPreview $true -PermissionToRelease $true
 ```
 
 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`.

exchange/exchange-ps/exchange/New-QuarantinePolicy.md

@@ -37,6 +37,7 @@ New-QuarantinePolicy [-Name] <String>
  [-EndUserSpamNotificationLanguage <EsnLanguage>]
  [-EsnCustomSubject <MultiValuedProperty>]
  [-ESNEnabled <Boolean>]
+ [-IncludeMessagesFromBlockedSenderAddress <Boolean>]
  [-MultiLanguageCustomDisclaimer <MultiValuedProperty>]
  [-MultiLanguageSenderName <MultiValuedProperty>]
  [-MultiLanguageSetting <MultiValuedProperty>]
@@ -216,7 +217,7 @@ This parameter uses a decimal value that's converted from a binary value. The bi
 
 - PermissionToViewHeader: The value 0 doesn't hide the **View message header** action in quarantine. If the message is visible in quarantine, the action is always available for the message.
 - PermissionToDownload: This permission is not used (the value 0 or 1 does nothing).
-- PermissionToAllowSender: This permission is not used (the value 0 or 1 does nothing).
+- PermissionToAllowSender
 - PermissionToBlockSender
 - PermissionToRequestRelease: Don't set this permission and PermissionToRelease to the value 1. Set one value to 1 and the other value to 0, or set both values to 0.
 - PermissionToRelease: Don't set this permission and PermissionToRequestRelease to value 1. Set one value to 1 and the other value to 0, or set both values to 0. This permission isn't honored for messages that were quarantined as malware or high confidence phishing. If the quarantine policy gives users this permission, users are allowed to request the release of their quarantined malware or high confidence phishing messages as if PermissionToRequestRelease was selected instead.
@@ -226,8 +227,8 @@ This parameter uses a decimal value that's converted from a binary value. The bi
 The values for the preset end-user permission groups are described in the following list:
 
 - No access: Binary = 0000000, so use the decimal value 0.
-- Limited access: Binary = 00011011, so use the decimal value 27.
-- Full access: Binary = 00010111, so use the decimal value 23.
+- Limited access: Binary = 00101011, so use the decimal value 43.
+- Full access: Binary = 00100111, so use the decimal value 39.
 
 For custom permissions, get the binary value that corresponds to the permissions you want. Convert the binary value to a decimal value to use. Don't use the binary value for this parameter.
 
@@ -360,6 +361,25 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -IncludeMessagesFromBlockedSenderAddress
+The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are:
+
+- $true: Recipients get quarantine notifications for affected messages from blocked senders.
+- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online, Exchange Online Protection
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -MultiLanguageCustomDisclaimer
 This parameter is reserved for internal Microsoft use.
 

exchange/exchange-ps/exchange/Set-QuarantinePolicy.md

@@ -38,6 +38,7 @@ Set-QuarantinePolicy [-Identity] <QuarantineTagIdParameter>
  [-EsnCustomSubject <MultiValuedProperty>]
  [-ESNEnabled <Boolean>]
  [-IgnoreDehydratedFlag]
+ [-IncludeMessagesFromBlockedSenderAddress <Boolean>]
  [-MultiLanguageCustomDisclaimer <MultiValuedProperty>]
  [-MultiLanguageSenderName <MultiValuedProperty>]
  [-MultiLanguageSetting <MultiValuedProperty>]
@@ -234,7 +235,7 @@ This parameter uses a decimal value that's converted from a binary value. The bi
 
 - PermissionToViewHeader: The value 0 doesn't hide the **View message header** action in quarantine. If the message is visible in quarantine, the action is always available for the message.
 - PermissionToDownload: This permission is not used (the value 0 or 1 does nothing).
-- PermissionToAllowSender: This permission is not used (the value 0 or 1 does nothing).
+- PermissionToAllowSender
 - PermissionToBlockSender
 - PermissionToRequestRelease: Don't set this permission and PermissionToRelease to the value 1. Set one value to 1 and the other value to 0, or set both values to 0.
 - PermissionToRelease: Don't set this permission and PermissionToRequestRelease to value 1. Set one value to 1 and the other value to 0, or set both values to 0. This permission isn't honored for messages that were quarantined as malware or high confidence phishing. If the quarantine policy gives users this permission, users are allowed to request the release of their quarantined malware or high confidence phishing messages as if PermissionToRequestRelease was selected instead.
@@ -244,8 +245,8 @@ This parameter uses a decimal value that's converted from a binary value. The bi
 The values for the preset end-user permission groups are described in the following list:
 
 - No access: Binary = 0000000, so use the decimal value 0.
-- Limited access: Binary = 00011011, so use the decimal value 27.
-- Full access: Binary = 00010111, so use the decimal value 23.
+- Limited access: Binary = 00101011, so use the decimal value 43.
+- Full access: Binary = 00100111, so use the decimal value 39.
 
 For custom permissions, get the binary value that corresponds to the permissions you want. Convert the binary value to a decimal value to use. Don't use the binary value for this parameter.
 
@@ -392,6 +393,25 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -IncludeMessagesFromBlockedSenderAddress
+The IncludeMessagesFromBlockedSenderAddress parameter specifies whether to send quarantine notifications for quarantined messages from blocked sender addresses. Valid values are:
+
+- $true: Recipients get quarantine notifications for affected messages from blocked senders.
+- $false: Recipients don't get quarantine notifications for affected messages from blocked senders. This is the default value.
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Exchange Online, Exchange Online Protection
+
+Required: False
+Position: Named
+Default value: False
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -MultiLanguageCustomDisclaimer
 The MultiLanguageCustomDisclaimer parameter specifies the custom disclaimer text to use near the bottom of quarantine notifications. The localized text, **A disclaimer from your organization:** is always included first, followed by the text you specify for this parameter.