Skip to content

Commit d30f287

Browse files
authored
Update New-DlpComplianceRule.md
1 parent 96a01aa commit d30f287

File tree

1 file changed

+7
-9
lines changed

1 file changed

+7
-9
lines changed

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

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1155,20 +1155,18 @@ The EvaluateRulePerComponent parameter specifies whether a match for conditions
11551155
- $true: A DLP rule match for conditions and exceptions must be in the same message component (for example, in the message body or in a single attachment).
11561156
- $false: A DLP rule match for conditions and exceptions can be anywhere in the message.
11571157

1158-
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.
1158+
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.
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.
1160+
**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.
11611161

11621162
This parameter works with the following conditions or exceptions only:
11631163

1164-
- Content contains
1165-
- Attachment contains
1166-
- Attachment is not labeled
1167-
- File extension is
1168-
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-
1164+
- Content contains.
1165+
- Attachment contains.
1166+
- Attachment is not labeled.
1167+
- File extension is.
11711168

1169+
**Note**: Unsupported conditions evaluate the entire email message and attachments as a single component. Supported conditions are evaluated for each email message component.
11721170

11731171
```yaml
11741172
Type: Boolean

0 commit comments

Comments
 (0)