Skip to content

Commit c43f375

Browse files
committed
Updates to HostedContentFilterPolicy cmdlet topics
Revied and edited weird/non-functional PR MicrosoftDocs#4074
1 parent c35dd92 commit c43f375

File tree

2 files changed

+98
-15
lines changed

2 files changed

+98
-15
lines changed

exchange/exchange-ps/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md

Lines changed: 48 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -62,10 +62,12 @@ New-HostedContentFilterPolicy [-Name] <String>
6262
[-MarkAsSpamWebBugsInHtml <Off | On | Test>]
6363
[-ModifySubjectValue <String>]
6464
[-PhishSpamAction <MoveToJmf | AddXHeader | ModifySubject | Redirect | Delete | Quarantine | NoAction>]
65+
[-PhishZapEnabled <$true | $false>
6566
[-QuarantineRetentionPeriod <Int32>]
6667
[-RedirectToRecipients <MultiValuedProperty>]
6768
[-RegionBlockList <MultiValuedProperty>]
6869
[-SpamAction <MoveToJmf | AddXHeader | ModifySubject | Redirect | Delete | Quarantine | NoAction>]
70+
[-SpamZapEnabled <$true | $false>]
6971
[-TestModeAction <None | AddXHeader | BccMessage>]
7072
[-TestModeBccToRecipients <MultiValuedProperty>]
7173
[-WhatIf]
@@ -796,6 +798,27 @@ Accept pipeline input: False
796798
Accept wildcard characters: False
797799
```
798800
801+
### -PhishZapEnabled
802+
The PhishZapEnabled parameter specifies whether to enable [zero-hour auto purge (ZAP)](https://docs.microsoft.com/office365/securitycompliance/zero-hour-auto-purge) to detect phish messages in the user's Inbox. Valid values are:
803+
804+
- $true: Phish ZAP is enabled. Phish messages that are detected in the user's Inbox (regardless of read or unread status) are automatically moved to the Junk Email folder. This is the default value.
805+
806+
- $false: Phish ZAP is disabled.
807+
808+
**Note**: The ZapEnabled parameter that controls both phish ZAP and spam ZAP will be deprecated in a future release. During the transition, both parameters will be available. If you have scripts that use the ZapEnabled parameter for phish, we recommend updating them to use this parameter instead. By default, the value for this parameter is inherited from the ZapEnabled parameter. After you configure phish ZAP in the admin center or by using this parameter, the value of the ZapEnabled parameter for phish ZAP is ignored.
809+
810+
```yaml
811+
Type: $true | $false
812+
Parameter Sets: (All)
813+
Aliases:
814+
Applicable: Exchange Online, Exchange Online Protection
815+
Required: False
816+
Position: Named
817+
Default value: None
818+
Accept pipeline input: False
819+
Accept wildcard characters: False
820+
```
821+
799822
### -QuarantineRetentionPeriod
800823
The QuarantineRetentionPeriod parameter specifies the length of time in days that spam messages remain in the quarantine. Valid input for this parameter is an integer between 1 and 15. The default value is 15.
801824
@@ -872,6 +895,27 @@ Accept pipeline input: False
872895
Accept wildcard characters: False
873896
```
874897
898+
### -SpamZapEnabled
899+
The SpamZapEnabled parameter specifies whether to enable [zero-hour auto purge (ZAP)](https://docs.microsoft.com/office365/securitycompliance/zero-hour-auto-purge) to detect unread spam messages in the user's Inbox. Valid values are:
900+
901+
- $true: Spam ZAP is enabled. Unread spam messages that are detected in the user's Inbox are automatically moved to the Junk Email folder. This is the default value.
902+
903+
- $false: Spam ZAP is disabled.
904+
905+
**Note**: The ZapEnabled parameter that controls both phish ZAP and spam ZAP will be deprecated in a future release. During the transition, both parameters will be available. If you have scripts that use the ZapEnabled parameter for spam, we recommend updating them to use this parameter instead. By default, the value for this parameter is inherited from the ZapEnabled parameter. After you configure spam ZAP in the admin center or by using this parameter, the value of the ZapEnabled parameter for spam ZAP is ignored.
906+
907+
```yaml
908+
Type: $true | $false
909+
Parameter Sets: (All)
910+
Aliases:
911+
Applicable: Exchange Online, Exchange Online Protection
912+
Required: False
913+
Position: Named
914+
Default value: None
915+
Accept pipeline input: False
916+
Accept wildcard characters: False
917+
```
918+
875919
### -TestModeAction
876920
The TestModeAction parameter specifies the additional action to take on messages that match any of the IncreaseScoreWith or MarkAsSpam parameters that are set to the value Test. Valid values are:
877921
@@ -926,21 +970,13 @@ Accept wildcard characters: False
926970
```
927971
928972
### -ZapEnabled
929-
The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for spam. ZAP detects unread spam messages that have already been delivered to the user's Inbox. Valid values are:
930-
931-
- $true: ZAP for spam is enabled. Unread spam messages that are detected in the user's Inbox are automatically moved to the Junk Email folder. This is the default value.
932-
933-
- $false: ZAP for spam is disabled.
934-
935-
Note: ZAP for spam requires that the following action parameters are set to the value MoveToJmf:
973+
The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for phish and spam. Valid values are:
936974
937-
- BulkSpamAction
975+
- $true: ZAP for phish and spam is enabled. Unread spam messages or phish messages (regardless of read or unread status) that are detected in the user's Inbox are automatically moved to the Junk Email folder. This is the default value.
938976
939-
- HighConfidenceSpamAction
977+
- $false: ZAP for phish and spam is disabled.
940978
941-
- PhishSpamAction
942-
943-
- SpamAction
979+
**Note**: This parameter will be deprecated in a future release. During the transition, this parameter and the PhishZapEnabled and SpamZapEnabled parameters will be available. If you have scripts that use this parameter, we recommend updating them to use the PhishZapEnabled and SpamZapEnabled parameters instead. By default, the value for the PhishZapEnabled and SpamZapEnabled parameters is inherited from this parameter. After you configure phish ZAP or spam ZAP in the admin center or by using the PhishZapEnabled and SpamZapEnabled parameters, the value of this parameter is ignored.
944980
945981
```yaml
946982
Type: $true | $false

exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md

Lines changed: 50 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -63,10 +63,12 @@ Set-HostedContentFilterPolicy [-Identity] <HostedContentFilterPolicyIdParameter>
6363
[-MarkAsSpamWebBugsInHtml <Off | On | Test>]
6464
[-ModifySubjectValue <String>]
6565
[-PhishSpamAction <MoveToJmf | AddXHeader | ModifySubject | Redirect | Delete | Quarantine | NoAction>]
66+
[-PhishZapEnabled <$true | $false>
6667
[-QuarantineRetentionPeriod <Int32>]
6768
[-RedirectToRecipients <MultiValuedProperty>]
6869
[-RegionBlockList <MultiValuedProperty>]
6970
[-SpamAction <MoveToJmf | AddXHeader | ModifySubject | Redirect | Delete | Quarantine | NoAction>]
71+
[-SpamZapEnabled <$true | $false>]
7072
[-TestModeAction <None | AddXHeader | BccMessage>]
7173
[-TestModeBccToRecipients <MultiValuedProperty>]
7274
[-WhatIf]
@@ -818,6 +820,27 @@ Accept pipeline input: False
818820
Accept wildcard characters: False
819821
```
820822
823+
### -PhishZapEnabled
824+
The PhishZapEnabled parameter specifies whether to enable [zero-hour auto purge (ZAP)](https://docs.microsoft.com/office365/securitycompliance/zero-hour-auto-purge) to detect phish messages in the user's Inbox. Valid values are:
825+
826+
- $true: Phish ZAP is enabled. Phish messages that are detected in the user's Inbox (regardless of read or unread status) are automatically moved to the Junk Email folder. This is the default value.
827+
828+
- $false: Phish ZAP is disabled.
829+
830+
**Note**: The ZapEnabled parameter that controls both phish ZAP and spam ZAP will be deprecated in a future release. During the transition, both parameters will be available. If you have scripts that use the ZapEnabled parameter for phish, we recommend updating them to use this parameter instead. By default, the value for this parameter is inherited from the ZapEnabled parameter. After you configure phish ZAP in the admin center or by using this parameter, the value of the ZapEnabled parameter for phish ZAP is ignored.
831+
832+
```yaml
833+
Type: $true | $false
834+
Parameter Sets: (All)
835+
Aliases:
836+
Applicable: Exchange Online, Exchange Online Protection
837+
Required: False
838+
Position: Named
839+
Default value: None
840+
Accept pipeline input: False
841+
Accept wildcard characters: False
842+
```
843+
821844
### -QuarantineRetentionPeriod
822845
The QuarantineRetentionPeriod parameter specifies the length of time in days that spam messages remain in the quarantine. Valid input for this parameter is an integer between 1 and 15. The default value is 15.
823846
@@ -902,6 +925,28 @@ Accept pipeline input: False
902925
Accept wildcard characters: False
903926
```
904927
928+
### -SpamZapEnabled
929+
The SpamZapEnabled parameter specifies whether to enable [zero-hour auto purge (ZAP)](https://docs.microsoft.com/office365/securitycompliance/zero-hour-auto-purge) to detect unread spam messages in the user's Inbox. Valid values are:
930+
931+
- $true: Spam ZAP is enabled. Unread spam messages that are detected in the user's Inbox are automatically moved to the Junk Email folder. This is the default value.
932+
933+
- $false: Spam ZAP is disabled.
934+
935+
**Note**: The ZapEnabled parameter that controls both phish ZAP and spam ZAP will be deprecated in a future release. During the transition, both parameters will be available. If you have scripts that use the ZapEnabled parameter for spam, we recommend updating them to use this parameter instead. By default, the value for this parameter is inherited from the ZapEnabled parameter. After you configure spam ZAP in the admin center or by using this parameter, the value of the ZapEnabled parameter for spam ZAP is ignored.
936+
937+
```yaml
938+
Type: $true | $false
939+
Parameter Sets: (All)
940+
Aliases:
941+
Applicable: Exchange Online, Exchange Online Protection
942+
Required: False
943+
Position: Named
944+
Default value: None
945+
Accept pipeline input: False
946+
Accept wildcard characters: False
947+
```
948+
949+
905950
### -TestModeAction
906951
The TestModeAction parameter specifies the additional action to take on messages when the IncreaseScoreWith or MarkAsSpam parameters that are set to the value Test. Valid values are:
907952
@@ -956,11 +1001,13 @@ Accept wildcard characters: False
9561001
```
9571002
9581003
### -ZapEnabled
959-
The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP). ZAP detects unread messages that have already been delivered to the user's Inbox. Valid values are:
1004+
The ZapEnabled parameter specifies whether to enable zero-hour auto purge (ZAP) for phish and spam. Valid values are:
1005+
1006+
- $true: ZAP for phish and spam is enabled. Unread spam messages or phish messages (regardless of read or unread status) that are detected in the user's Inbox are automatically moved to the Junk Email folder. This is the default value.
9601007
961-
- $true: ZAP is enabled. Unread messages that are detected in the user's Inbox are automatically moved to the Junk Email folder. This is the default value.
1008+
- $false: ZAP for phish and spam is disabled.
9621009
963-
- $false: ZAP is disabled.
1010+
**Note**: This parameter will be deprecated in a future release. During the transition, this parameter and the PhishZapEnabled and SpamZapEnabled parameters will be available. If you have scripts that use this parameter, we recommend updating them to use the PhishZapEnabled and SpamZapEnabled parameters instead. By default, the value for the PhishZapEnabled and SpamZapEnabled parameters is inherited from this parameter. After you configure phish ZAP or spam ZAP in the admin center or by using the PhishZapEnabled and SpamZapEnabled parameters, the value of this parameter is ignored.
9641011
9651012
```yaml
9661013
Type: $true | $false

0 commit comments

Comments
 (0)