From d108d420876f1a66827033fd2f88488109b01344 Mon Sep 17 00:00:00 2001
From: Aakash Malhotra <53205984+aamalhot@users.noreply.github.com>
Date: Thu, 17 Jul 2025 13:18:52 +0530
Subject: [PATCH 1/2] Update New-SensitiveInformationScanRule.md

---
 .../exchange/New-SensitiveInformationScanRule.md | 16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
index 96d0e19fc1..2d9c863446 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
@@ -42,15 +42,16 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 
 ### Example 1
 ```powershell
-{{ Add example code here }}
+New-SensitiveInformationScan "SharePoint scan" -SharePointLocation All
+New-SensitiveInformationScanRule "SharePoint scan rule" -ContentExtensionMatchesWords "pdf", "docx" -Policy "SharePoint scan" -Workload SharePoint
 ```
 
-{{ Add example description here }}
+Above example creates a scan for all sharepoint sites scoped to pdf and docx files only. This cmdlet should be used in combination with New-SensitiveInformationScan.
 
 ## PARAMETERS
 
 ### -Name
-{{ Fill Name Description }}
+Specify rule name for the scan
 
 ```yaml
 Type: String
@@ -66,7 +67,7 @@ Accept wildcard characters: False
 ```
 
 ### -Policy
-{{ Fill Policy Description }}
+Scan policy name that is parent of this rule
 
 ```yaml
 Type: PolicyIdParameter
@@ -159,7 +160,7 @@ Accept wildcard characters: False
 ```
 
 ### -ContentCreatedOrUpdatedDateFrom
-{{ Fill ContentCreatedOrUpdatedDateFrom Description }}
+If specified, files last modified after this date are considered in scope of scan. 
 
 ```yaml
 Type: System.DateTime
@@ -175,7 +176,7 @@ Accept wildcard characters: False
 ```
 
 ### -ContentCreatedOrUpdatedDateTo
-{{ Fill ContentCreatedOrUpdatedDateTo Description }}
+Files last modified before this date are considered in scope of scan.
 
 ```yaml
 Type: System.DateTime
@@ -259,7 +260,8 @@ Accept wildcard characters: False
 ```
 
 ### -StartImpactAssessment
-{{ Fill StartImpactAssessment Description }}
+Set to true to start an scan estimation by default. This needs to be passed as false to prevent starting scan estimation by default.
+
 
 ```yaml
 Type: Boolean

From c8c279b5c25a44ce66e3161eb40d5827aff8ba85 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 17 Jul 2025 10:42:39 -0700
Subject: [PATCH 2/2] Update New-SensitiveInformationScanRule.md

---
 .../exchange/New-SensitiveInformationScanRule.md  | 15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
index 2d9c863446..948a0ad3a7 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
@@ -43,15 +43,16 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 ### Example 1
 ```powershell
 New-SensitiveInformationScan "SharePoint scan" -SharePointLocation All
+
 New-SensitiveInformationScanRule "SharePoint scan rule" -ContentExtensionMatchesWords "pdf", "docx" -Policy "SharePoint scan" -Workload SharePoint
 ```
 
-Above example creates a scan for all sharepoint sites scoped to pdf and docx files only. This cmdlet should be used in combination with New-SensitiveInformationScan.
+This example creates a scan for all SharePoint sites scoped to pdf and docx files only. Use the New-SensitiveInformationScanRule only in combination with New-SensitiveInformationScan.
 
 ## PARAMETERS
 
 ### -Name
-Specify rule name for the scan
+The Name parameter specifes the unique rule name for the scan. If the value contains spaces, enclose the value in quotation marks.
 
 ```yaml
 Type: String
@@ -67,7 +68,7 @@ Accept wildcard characters: False
 ```
 
 ### -Policy
-Scan policy name that is parent of this rule
+The Policy parameter specifies the name of the parent scan policy for this rule. If the value contains spaces, enclose the value in quotation marks.
 
 ```yaml
 Type: PolicyIdParameter
@@ -160,7 +161,7 @@ Accept wildcard characters: False
 ```
 
 ### -ContentCreatedOrUpdatedDateFrom
-If specified, files last modified after this date are considered in scope of scan. 
+The ContentCreatedOrUpdatedDateFrom prameter specifies the earliest modification date-time of files that are considered in scope of this scan.
 
 ```yaml
 Type: System.DateTime
@@ -176,7 +177,7 @@ Accept wildcard characters: False
 ```
 
 ### -ContentCreatedOrUpdatedDateTo
-Files last modified before this date are considered in scope of scan.
+The ContentCreatedOrUpdatedDateTo prameter specifies the latest modification date-time of files that are considered in scope of this scan.
 
 ```yaml
 Type: System.DateTime
@@ -260,8 +261,10 @@ Accept wildcard characters: False
 ```
 
 ### -StartImpactAssessment
-Set to true to start an scan estimation by default. This needs to be passed as false to prevent starting scan estimation by default.
+The StartImpactAssessment parameter specifies whether to start a scan estimation. Valid values are:
 
+- $true: Start an scan estimation by default.
+- $false: Prevent starting scan estimation by default.
 
 ```yaml
 Type: Boolean