From a4da604c6619f16f04a57347b4a52a796171b7c3 Mon Sep 17 00:00:00 2001 From: ybhargav1995 <102363816+ybhargav1995@users.noreply.github.com> Date: Thu, 20 Nov 2025 19:20:37 +0530 Subject: [PATCH 1/2] Update note on DLP rule parameter scoping Clarified note about parameter behavior in DLP rules. --- .../exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md index 03c3164518..8a31cf5e8b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md @@ -1134,7 +1134,7 @@ The EvaluateRulePerComponent parameter specifies whether a match for conditions 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. -**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. +**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. Same applies even when the Content Contains condition is within the NOT operator as well. This parameter works with the following conditions or exceptions only: From d40bac81160a2bd9a9938250775d263f219a00c6 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 20 Nov 2025 09:01:30 -0800 Subject: [PATCH 2/2] Update New-DlpComplianceRule.md --- .../exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md index 8a31cf5e8b..53c50391ba 100644 --- a/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/New-DlpComplianceRule.md @@ -1134,7 +1134,7 @@ The EvaluateRulePerComponent parameter specifies whether a match for conditions 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. -**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. Same applies even when the Content Contains condition is within the NOT operator as well. +**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. This parameter works with the following conditions or exceptions only: