Skip to content

Commit 5953070

Browse files
authored
Merge pull request #13251 from ybhargav1995/patch-36
Update note on DLP rule parameter scoping
2 parents f426e4b + d40bac8 commit 5953070

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1134,7 +1134,7 @@ The EvaluateRulePerComponent parameter specifies whether a match for conditions
11341134

11351135
For example, 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.
11361136

1137-
**Note**: When the value of this parameter is $true, the scoping within Content Contains condition is overriden. In other words, even if the scoping is set to Attachments only, the message body is also scanned as a separate component. Even when the scoping is set to Message only, attachments are scanned as individual components.
1137+
**Note**: When the value of this parameter is $true, the scoping within Content Contains condition is overriden. In other words, even if the scoping is set to Attachments only, the message body is also scanned as a separate component. Even when the scoping is set to Message only, attachments are scanned as individual components. The same behavior applies for the NOT operator on the Content Contains condition.
11381138

11391139
This parameter works with the following conditions or exceptions only:
11401140

0 commit comments

Comments
 (0)