Skip to content

Commit 96a01aa

Browse files
authored
Update New-DlpComplianceRule.md with parameter notes
Clarified behavior of DLP rule matching with new notes on parameter effects.
1 parent 2485b23 commit 96a01aa

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1157,13 +1157,19 @@ The EvaluateRulePerComponent parameter specifies whether a match for conditions
11571157

11581158
For example, say a DLP rule is configured to block messages that contain three or more Social Security numbers (SSNs). When the value of this parameter is $true, a message is blocked only if there are three or more SSNs in the message body, or there are three or more SSNs in a specific attachment. The DLP rule doesn't match and the message isn't blocked if there are two SSNs in the message body, one SSN in an attachment, and two SSNs in another attachment in the same email message.
11591159

1160+
**Note** : When this is turned on the scoping within Content Contains condition is overriden, that is even if the scoping is set to Attachments only the message body will also be scanned as a separate component and even when the scoping is set to Message only the attachments are scanned as individual components.
1161+
11601162
This parameter works with the following conditions or exceptions only:
11611163

11621164
- Content contains
11631165
- Attachment contains
11641166
- Attachment is not labeled
11651167
- File extension is
11661168

1169+
**Note** : When the rule contains any conditions other than the above, the unsupported conditions will be evaluated considering entire email including the attachments as a single component, but the supported conditions are evaluated for each component.
1170+
1171+
1172+
11671173
```yaml
11681174
Type: Boolean
11691175
Parameter Sets: (All)

0 commit comments

Comments
 (0)