From f1e7456361cf2b51b21395b80667ee7876b9051f Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Mon, 9 Jun 2025 16:46:06 -0700
Subject: [PATCH 01/21] Create

---
 .../Cancel-SensitiveInformationScan.md        | 109 +++
 .../exchange/Get-SensitiveInformationScan.md  | 138 ++++
 .../Get-SensitiveInformationScanRule.md       |  86 +++
 .../exchange/New-SensitiveInformationScan.md  | 508 +++++++++++++
 .../New-SensitiveInformationScanRule.md       | 298 ++++++++
 .../Remove-SensitiveInformationScan.md        | 108 +++
 .../Remove-SensitiveInformationScanRule.md    | 107 +++
 .../exchange/Set-SensitiveInformationScan.md  | 695 ++++++++++++++++++
 .../Set-SensitiveInformationScanRule.md       | 287 ++++++++
 9 files changed, 2336 insertions(+)
 create mode 100644 exchange/exchange-ps/exchange/Cancel-SensitiveInformationScan.md
 create mode 100644 exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md
 create mode 100644 exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md
 create mode 100644 exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
 create mode 100644 exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
 create mode 100644 exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
 create mode 100644 exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
 create mode 100644 exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
 create mode 100644 exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md

diff --git a/exchange/exchange-ps/exchange/Cancel-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Cancel-SensitiveInformationScan.md
new file mode 100644
index 0000000000..db4687eed9
--- /dev/null
+++ b/exchange/exchange-ps/exchange/Cancel-SensitiveInformationScan.md
@@ -0,0 +1,109 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/cancel-sensitiveinformationscan
+applicable: Security & Compliance
+title: Cancel-SensitiveInformationScan
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Cancel-SensitiveInformationScan
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the Cancel-SensitiveInformationScan cmdlet to cancel sensitive information scans.
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+### Identity (Default)
+```
+Cancel-SensitiveInformationScan [-Identity] <PolicyIdParameter>
+ [-Confirm]
+ [-WhatIf]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Cancel-SensitiveInformationScan -Identity "HR Department"
+```
+
+This example cancels the specified sensitive information scan.
+
+## PARAMETERS
+
+### -Identity
+The Identity parameter specifies the sensitive information scan that you want to cancel. You can use any value that uniquely identifies the scan. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+```yaml
+Type: PolicyIdParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: True
+Position: 0
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+
+### -Confirm
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+The WhatIf switch doesn't work in Security & Compliance PowerShell.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md
new file mode 100644
index 0000000000..78ddca81f9
--- /dev/null
+++ b/exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md
@@ -0,0 +1,138 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-sensitiveinformationscan
+applicable: Security & Compliance
+title: Get-SensitiveInformationScan
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Get-SensitiveInformationScan
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the Get-SensitiveInformationScan cmdlet to view sensitive information scans.
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Get-SensitiveInformationScan [[-Identity] <PolicyIdParameter>]
+ [-IncludeImpactAssessment <Boolean>]
+ [-IncludeProgressForAllActiveScans <Boolean>]
+ [-IncludeScanProgress <Boolean>]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Get-SensitiveInformationScan | Format-Table Name,ParentPolicyName
+```
+
+This example returns a summary list of all sensitive information scans in the organization.
+
+### Example 2
+```powershell
+Get-SensitiveInformationScan -Identity "HR Department Scan"
+```
+
+This example returns detailed information for the specified scan.
+
+## PARAMETERS
+
+### -Identity
+The Identity parameter specifies the sensitive information scan that you want to view. You can use any value that uniquely identifies the scan. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+```yaml
+Type: PolicyIdParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: 0
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+
+### -IncludeImpactAssessment
+The IncludeImpactAssessment parameter specifies whether to ???. Valid values are:
+
+- $true: ???
+- $false: ???
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -IncludeProgressForAllActiveScans
+The IncludeProgressForAllActiveScans parameter specifies whether to ???. Valid values are:
+
+- $true: ???
+- $false: ???
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -IncludeScanProgress
+The IncludeScanProgress parameter specifies whether to ???. Valid values are:
+
+- $true: ???
+- $false: ???
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md
new file mode 100644
index 0000000000..6b0f999225
--- /dev/null
+++ b/exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md
@@ -0,0 +1,86 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/get-sensitiveinformationscanrule
+applicable: Security & Compliance
+title: Get-SensitiveInformationScanRule
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Get-SensitiveInformationScanRule
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the Get-SensitiveInformationScanRule cmdlet to
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Get-SensitiveInformationScanRule [[-Identity] <ComplianceRuleIdParameter>] [-Policy <PolicyIdParameter>] [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+{{ Add example code here }}
+```
+
+{{ Add example description here }}
+
+## PARAMETERS
+
+### -Identity
+The Identity parameter specifies the sensitive information scan rule that you want to view. You can use any value that uniquely identifies the rule. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+```yaml
+Type: ComplianceRuleIdParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: 0
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+
+### -Policy
+{{ Fill Policy Description }}
+
+```yaml
+Type: PolicyIdParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
new file mode 100644
index 0000000000..0eaa365532
--- /dev/null
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
@@ -0,0 +1,508 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-sensitiveinformationscan
+applicable: Security & Compliance
+title: New-SensitiveInformationScan
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# New-SensitiveInformationScan
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the New-SensitiveInformationScan cmdlet to
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+New-SensitiveInformationScan [-Name] <String>
+ [-Comment <String>]
+ [-Confirm]
+ [-EndpointDlpLocation <MultiValuedProperty>]
+ [-EndpointDlpLocationException <MultiValuedProperty>]
+ [-ExceptIfOneDriveSharedBy <RecipientIdParameter[]>]
+ [-ExceptIfOneDriveSharedByMemberOf <RecipientIdParameter[]>]
+ [-ExchangeLocation <MultiValuedProperty>]
+ [-ExchangeSender <SmtpAddress[]>]
+ [-ExchangeSenderException <SmtpAddress[]>]
+ [-ExchangeSenderMemberOf <RecipientIdParameter[]>]
+ [-ExchangeSenderMemberOfException <RecipientIdParameter[]>]
+ [-OneDriveLocation <MultiValuedProperty>]
+ [-OneDriveLocationException <MultiValuedProperty>]
+ [-OneDriveSharedBy <RecipientIdParameter[]>]
+ [-OneDriveSharedByMemberOf <RecipientIdParameter[]>]
+ [-PolicyRBACScopes <MultiValuedProperty>]
+ [-SharePointLocation <MultiValuedProperty>]
+ [-SharePointLocationException <MultiValuedProperty>]
+ [-TeamsLocation <MultiValuedProperty>]
+ [-TeamsLocationException <MultiValuedProperty>]
+ [-WhatIf]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+{{ Add example code here }}
+```
+
+{{ Add example description here }}
+
+## PARAMETERS
+
+### -Name
+{{ Fill Name Description }}
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: True
+Position: 0
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Comment
+The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Confirm
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -EndpointDlpLocation
+**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
+
+The EndpointDLPLocation parameter specifies the user accounts to include in scan for Endpoint DLP when they are logged on to an onboarded device. You identify the account by name or email address. You can use the value All to include all user accounts.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -EndpointDlpLocationException
+**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
+
+The EndpointDlpLocationException parameter specifies the user accounts to exclude from Endpoint DLP when you use the value All for the EndpointDlpLocation parameter. You identify the account by name or email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExceptIfOneDriveSharedBy
+The ExceptIfOneDriveSharedBy parameter specifies the users to exclude from the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (laura@contoso.onmicrosoft.com).
+
+To use this parameter, OneDrive sites need to be included in the scan (the OneDriveLocation parameter value is All, which is the default value).
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMemberOf parameters.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExceptIfOneDriveSharedByMemberOf
+The ExceptIfOneDriveSharedByMemberOf parameter specifies the distribution groups or mail-enabled security groups to exclude from the scan (the OneDrive sites of group members are excluded from the scan). You identify the groups by email address.
+
+To use this parameter, OneDrive sites need to be included in the scan (the OneDriveLocation parameter value is All, which is the default value).
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMemberOf parameters.
+
+You can't use this parameter to specify Microsoft 365 Groups.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeLocation
+The ExchangeLocation parameter specifies whether to include email messages in the scan. The valid value for this parameter is All. If you don't want to include email messages in the scan, don't use this parameter (the default value is blank or $null).
+
+You can use this parameter in the following procedures:
+
+- If you use `-ExchangeLocation All` by itself, the scan applies to email for all users.
+
+- To include email of specific group members in the scan, use `-ExchangeLocation All` with the ExchangeSenderMemberOf parameter in the same command. Only email of members of the specified groups is included in the scan.
+
+- To exclude email of specific group members from the scan, use `-ExchangeLocation All` with the ExchangeSenderMemberOfException parameter in the same command. Only email of members of the specified groups is excluded from the scan.
+
+You can't specify inclusions and exclusions in the same scan.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSender
+The ExchangeSender parameter specifies the users whose email is included in the scan. You identify the users by email address. You can specify internal or external email addresses.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You must use this parameter with the ExchangeLocation parameter.
+
+You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters.
+
+```yaml
+Type: SmtpAddress[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderException
+The ExchangeSenderException parameter specifies the internal users whose email is excluded from the scan. You identify the users by email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You must use this parameter with the ExchangeLocation parameter.
+
+You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
+
+```yaml
+Type: SmtpAddress[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderMemberOf
+The ExchangeSenderMemberOf parameter specifies the distribution groups or security groups to include in the scan (email of the group members is included in the scan). You identify the groups by email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You must use this parameter with the ExchangeLocation parameter.
+
+You can't use this parameter with the ExchangeSenderMemberOfException parameter.
+
+You can't use this parameter to specify Microsoft 365 Groups.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderMemberOfException
+The ExchangeSenderMemberOfException parameter specifies the distribution groups or security groups to exclude from the scan (email of the group members is excluded from the scan). You identify the groups by email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You must use this parameter with the ExchangeLocation parameter.
+
+You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
+
+You can't use this parameter to specify Microsoft 365 Groups.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -OneDriveLocation
+The OneDriveLocation parameter specifies the OneDrive sites to include in the scan. You identify the site by its URL value, or you can use the value All to include all sites.
+
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -OneDriveLocationException
+This parameter specifies the OneDrive sites to exclude when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value.
+
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -OneDriveSharedBy
+The OneDriveSharedBy parameter specifies the users to include in the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (laura@contoso.onmicrosoft.com).
+
+To use this parameter, OneDrive sites need to be included in the scan (the OneDriveLocation parameter value is All, which is the default value).
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDriveSharedByMemberOf parameters.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -OneDriveSharedByMemberOf
+The OneDriveSharedByMemberOf parameter specifies the distribution groups or mail-enabled security groups to include in the scan (the OneDrive sites of group members are included in the scan). You identify the groups by email address.
+
+To use this parameter, OneDrive sites need to be included in the scan (the OneDriveLocation parameter value is All, which is the default value).
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDriveSharedByMemberOf parameters.
+
+You can't use this parameter to specify Microsoft 365 Groups.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -PolicyRBACScopes
+{{ Fill PolicyRBACScopes Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -SharePointLocation
+{{ Fill SharePointLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -SharePointLocationException
+{{ Fill SharePointLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -TeamsLocation
+{{ Fill TeamsLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -TeamsLocationException
+{{ Fill TeamsLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+The WhatIf switch doesn't work in Security & Compliance PowerShell.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+Applicable:
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
new file mode 100644
index 0000000000..fdfba641e6
--- /dev/null
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
@@ -0,0 +1,298 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/new-sensitiveinformationscanrule
+applicable: Security & Compliance
+title: New-SensitiveInformationScanRule
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# New-SensitiveInformationScanRule
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the New-SensitiveInformationScan cmdlet to
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+New-SensitiveInformationScanRule [-Name] <String> -Policy <PolicyIdParameter> -Workload <PolicyConfiguration.Workload>
+ [-Comment <String>]
+ [-Confirm]
+ [-ContentCreatedOrUpdatedDateFrom <System.DateTime>]
+ [-ContentCreatedOrUpdatedDateTo <System.DateTime>]
+ [-ContentExtensionMatchesWords <MultiValuedProperty>]
+ [-ContentPropertyContainsWords <MultiValuedProperty>]
+ [-ExceptIfContentExtensionMatchesWords <MultiValuedProperty>]
+ [-ExceptIfContentPropertyContainsWords <MultiValuedProperty>]
+ [-StartImpactAssessment <Boolean>]
+ [-WhatIf]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+{{ Add example code here }}
+```
+
+{{ Add example description here }}
+
+## PARAMETERS
+
+### -Name
+{{ Fill Name Description }}
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: True
+Position: 0
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Policy
+{{ Fill Policy Description }}
+
+```yaml
+Type: PolicyIdParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Workload
+The Workload parameter specifies the workload. Valid values are:
+
+- Applications
+- AuditAlerting
+- AWS
+- Azure
+- AzureBatch
+- Copilot
+- DynamicScope
+- EndpointDevices
+- Exchange
+- ExchangeOnPremises
+- Intune
+- ModernGroup
+- OneDriveForBusiness
+- OnPremisesScanner
+- PowerBI
+- PublicFolder
+- SharePoint
+- SharePointOnPremises
+- Skype
+- Substrate
+- Teams
+- ThirdPartyApps
+- UnifiedAuditAzure
+
+This value appears in the LogicalWorkload property in the output of the Get-SensitiveInformationScanRule cmdlet.
+
+```yaml
+Type: PolicyConfiguration.Workload
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: True
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Comment
+The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Confirm
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ContentCreatedOrUpdatedDateFrom
+{{ Fill ContentCreatedOrUpdatedDateFrom Description }}
+
+```yaml
+Type: System.DateTime
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ContentCreatedOrUpdatedDateTo
+{{ Fill ContentCreatedOrUpdatedDateTo Description }}
+
+```yaml
+Type: System.DateTime
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ContentExtensionMatchesWords
+{{ Fill ContentExtensionMatchesWords Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ContentPropertyContainsWords
+{{ Fill ContentPropertyContainsWords Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExceptIfContentExtensionMatchesWords
+{{ Fill ExceptIfContentExtensionMatchesWords Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExceptIfContentPropertyContainsWords
+{{ Fill ExceptIfContentPropertyContainsWords Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -StartImpactAssessment
+{{ Fill StartImpactAssessment Description }}
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+The WhatIf switch doesn't work in Security & Compliance PowerShell.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
new file mode 100644
index 0000000000..03d11b7992
--- /dev/null
+++ b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
@@ -0,0 +1,108 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/remove-sensitiveinformationscan
+applicable: Security & Compliance
+title: Remove-SensitiveInformationScan
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Remove-SensitiveInformationScan
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the Remove-SensitiveInformationScan cmdlet to remove sensitive information scans.
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Remove-SensitiveInformationScan [-Identity] <PolicyIdParameter>
+ [-Confirm]
+ [-WhatIf]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Remove-SensitiveInformationScan -Identity "HR Department"
+```
+
+This example removes the specified sensitive information scan.
+
+## PARAMETERS
+
+### -Identity
+The Identity parameter specifies the sensitive information scan that you want to remove. You can use any value that uniquely identifies the scan. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+```yaml
+Type: PolicyIdParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: True
+Position: 0
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+
+### -Confirm
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+The WhatIf switch doesn't work in Security & Compliance PowerShell.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
new file mode 100644
index 0000000000..b0021e4f90
--- /dev/null
+++ b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
@@ -0,0 +1,107 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/remove-sensitiveinformationscanrule
+applicable: Security & Compliance
+title: Remove-SensitiveInformationScanRule
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Remove-SensitiveInformationScanRule
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the Remove-SensitiveInformationScanRule cmdlet to remove sensitive information scan rules.
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Remove-SensitiveInformationScanRule [-Identity] <ComplianceRuleIdParameter>
+ [-Confirm]
+ [-WhatIf]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+Remove-SensitiveInformationScanRule -Identity "HR Department Rule"
+```
+
+This example removes the specified sensitive information scan rule.
+
+## PARAMETERS
+
+### -Identity
+The Identity parameter specifies the sensitive information scan rule that you want to remove. You can use any value that uniquely identifies the rule. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+```yaml
+Type: ComplianceRuleIdParameter
+Parameter Sets: (All)
+Applicable: Security & Compliance
+
+Required: True
+Position: 0
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+
+### -Confirm
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+The WhatIf switch doesn't work in Security & Compliance PowerShell.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
new file mode 100644
index 0000000000..f8d37f8b8c
--- /dev/null
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
@@ -0,0 +1,695 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/set-sensitiveinformationscan
+applicable: Security & Compliance
+title: Set-SensitiveInformationScan
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Set-SensitiveInformationScan
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the Set-SensitiveInformationScan cmdlet to
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Set-SensitiveInformationScan [-Identity] <PolicyIdParameter>
+ [-AddEndpointDlpLocation <MultiValuedProperty>]
+ [-AddEndpointDlpLocationException <MultiValuedProperty>]
+ [-AddExchangeLocation <MultiValuedProperty>]
+ [-AddOneDriveLocation <MultiValuedProperty>]
+ [-AddOneDriveLocationException <MultiValuedProperty>]
+ [-AddSharePointLocation <MultiValuedProperty>]
+ [-AddSharePointLocationException <MultiValuedProperty>]
+ [-AddTeamsLocation <MultiValuedProperty>]
+ [-AddTeamsLocationException <MultiValuedProperty>]
+ [-CancelScan <Boolean>]
+ [-Comment <String>]
+ [-Confirm]
+ [-ExceptIfOneDriveSharedBy <RecipientIdParameter[]>]
+ [-ExceptIfOneDriveSharedByMemberOf <RecipientIdParameter[]>]
+ [-ExchangeSender <SmtpAddress[]>]
+ [-ExchangeSenderException <SmtpAddress[]>]
+ [-ExchangeSenderMemberOf <RecipientIdParameter[]>]
+ [-ExchangeSenderMemberOfException <RecipientIdParameter[]>]
+ [-Mode <PolicyMode>]
+ [-OneDriveSharedBy <RecipientIdParameter[]>]
+ [-OneDriveSharedByMemberOf <RecipientIdParameter[]>]
+ [-PolicyRBACScopes <MultiValuedProperty>]
+ [-RemoveEndpointDlpLocation <MultiValuedProperty>]
+ [-RemoveEndpointDlpLocationException <MultiValuedProperty>]
+ [-RemoveExchangeLocation <MultiValuedProperty>]
+ [-RemoveOneDriveLocation <MultiValuedProperty>]
+ [-RemoveOneDriveLocationException <MultiValuedProperty>]
+ [-RemoveSharePointLocation <MultiValuedProperty>]
+ [-RemoveSharePointLocationException <MultiValuedProperty>]
+ [-RemoveTeamsLocation <MultiValuedProperty>]
+ [-RemoveTeamsLocationException <MultiValuedProperty>]
+ [-StartImpactAssessment <Boolean>]
+ [-StopImpactAssessmentAndStartClassification <Boolean>]
+ [-WhatIf]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+{{ Add example code here }}
+```
+
+{{ Add example description here }}
+
+## PARAMETERS
+
+### -Identity
+The Identity parameter specifies the sensitive information scan that you want to modify. You can use any value that uniquely identifies the scan. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+```yaml
+Type: PolicyIdParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: True
+Position: 0
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+
+### -AddEndpointDlpLocation
+{{ Fill AddEndpointDlpLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AddEndpointDlpLocationException
+{{ Fill AddEndpointDlpLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AddExchangeLocation
+{{ Fill AddExchangeLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AddOneDriveLocation
+{{ Fill AddOneDriveLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AddOneDriveLocationException
+{{ Fill AddOneDriveLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AddSharePointLocation
+{{ Fill AddSharePointLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AddSharePointLocationException
+{{ Fill AddSharePointLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AddTeamsLocation
+{{ Fill AddTeamsLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -AddTeamsLocationException
+{{ Fill AddTeamsLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -CancelScan
+{{ Fill CancelScan Description }}
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Comment
+The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Confirm
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExceptIfOneDriveSharedBy
+The ExceptIfOneDriveSharedBy parameter specifies the users to exclude from the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (laura@contoso.onmicrosoft.com).
+
+To use this parameter, OneDrive sites need to be included in the scan (the OneDriveLocation parameter value is All, which is the default value).
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMemberOf parameters.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExceptIfOneDriveSharedByMemberOf
+{{ Fill ExceptIfOneDriveSharedByMemberOf Description }}
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSender
+The ExchangeSender parameter specifies the users whose email is included in the scan. You identify the users by email address. You can specify internal or external email addresses.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You must use this parameter with the ExchangeLocation parameter.
+
+You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters.
+
+```yaml
+Type: SmtpAddress[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderException
+The ExchangeSenderException parameter specifies the internal users whose email is excluded from the scan. You identify the users by email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You must use this parameter with the ExchangeLocation parameter.
+
+You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
+
+```yaml
+Type: SmtpAddress[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderMemberOf
+The ExchangeSenderMemberOf parameter specifies the distribution groups or security groups to include in the scan (email of the group members is included in the scan). You identify the groups by email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You must use this parameter with the ExchangeLocation parameter.
+
+You can't use this parameter with the ExchangeSenderMemberOfException parameter.
+
+You can't use this parameter to specify Microsoft 365 Groups.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderMemberOfException
+The ExchangeSenderMemberOfException parameter specifies the distribution groups or security groups to exclude from the scan (email of the group members is excluded from the scan). You identify the groups by email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You must use this parameter with the ExchangeLocation parameter.
+
+You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
+
+You can't use this parameter to specify Microsoft 365 Groups.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Mode
+{{ Fill Mode Description }}
+
+```yaml
+Type: PolicyMode
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -OneDriveSharedBy
+The OneDriveSharedBy parameter specifies the users to include in the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (laura@contoso.onmicrosoft.com).
+
+To use this parameter, one of the following statements must be true:
+
+- The scan already includes OneDrive sites (in the output of Get-DlpCOmpliancePolicy, the OneDriveLocation property value is All, which is the default value).
+- Use `-AddOneDriveLocation All` in the same command with this parameter.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDriveSharedByMemberOf parameters.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -OneDriveSharedByMemberOf
+{{ Fill OneDriveSharedByMemberOf Description }}
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -PolicyRBACScopes
+{{ Fill PolicyRBACScopes Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveEndpointDlpLocation
+{{ Fill RemoveEndpointDlpLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveEndpointDlpLocationException
+{{ Fill RemoveEndpointDlpLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveExchangeLocation
+{{ Fill RemoveExchangeLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveOneDriveLocation
+{{ Fill RemoveOneDriveLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveOneDriveLocationException
+{{ Fill RemoveOneDriveLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveSharePointLocation
+{{ Fill RemoveSharePointLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveSharePointLocationException
+{{ Fill RemoveSharePointLocationException Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveTeamsLocation
+{{ Fill RemoveTeamsLocation Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -RemoveTeamsLocationException
+{{ Fill RemoveTeamsLocationException Description }}
+
+```yaml
+Type:MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -StartImpactAssessment
+{{ Fill StartImpactAssessment Description }}
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -StopImpactAssessmentAndStartClassification
+{{ Fill StopImpactAssessmentAndStartClassification Description }}
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+The WhatIf switch doesn't work in Security & Compliance PowerShell.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS
diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
new file mode 100644
index 0000000000..b19aade77b
--- /dev/null
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
@@ -0,0 +1,287 @@
+---
+external help file: Microsoft.Exchange.TransportMailflow-Help.xml
+online version: https://learn.microsoft.com/powershell/module/exchange/set-sensitiveinformationscanrule
+applicable: Security & Compliance
+title: Set-SensitiveInformationScanRule
+schema: 2.0.0
+author: chrisda
+ms.author: chrisda
+ms.reviewer:
+---
+
+# Set-SensitiveInformationScanRule
+
+## SYNOPSIS
+This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
+
+Use the Set-SensitiveInformationScan cmdlet to
+
+For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
+
+## SYNTAX
+
+```
+Set-SensitiveInformationScanRule [-Identity] <ComplianceRuleIdParameter>
+ [-Comment <String>]
+ [-Confirm]
+ [-ContentCreatedOrUpdatedDateFrom <System.DateTime>]
+ [-ContentCreatedOrUpdatedDateTo <System.DateTime>]
+ [-ContentExtensionMatchesWords <MultiValuedProperty>]
+ [-ContentPropertyContainsWords <MultiValuedProperty>]
+ [-ExceptIfContentExtensionMatchesWords <MultiValuedProperty>]
+ [-ExceptIfContentPropertyContainsWords <MultiValuedProperty>]
+ [-StartImpactAssessment <Boolean>]
+ [-WhatIf]
+ [-Workload <PolicyConfiguration.Workload>]
+ [<CommonParameters>]
+```
+
+## DESCRIPTION
+To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
+
+## EXAMPLES
+
+### Example 1
+```powershell
+PS C:\> {{ Add example code here }}
+```
+
+{{ Add example description here }}
+
+## PARAMETERS
+
+### -Identity
+The Identity parameter specifies the sensitive information scan rule that you want to modify. You can use any value that uniquely identifies the rule. For example:
+
+- Name
+- Distinguished name (DN)
+- GUID
+
+```yaml
+Type: ComplianceRuleIdParameter
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: True
+Position: 0
+Default value: None
+Accept pipeline input: True (ByPropertyName, ByValue)
+Accept wildcard characters: False
+```
+
+### -Comment
+The Comment parameter specifies an optional comment. If you specify a value that contains spaces, enclose the value in quotation marks ("), for example: "This is an admin note".
+
+```yaml
+Type: String
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Confirm
+The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding.
+
+- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`.
+- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: cf
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ContentCreatedOrUpdatedDateFrom
+{{ Fill ContentCreatedOrUpdatedDateFrom Description }}
+
+```yaml
+Type: System.DateTime
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ContentCreatedOrUpdatedDateTo
+{{ Fill ContentCreatedOrUpdatedDateTo Description }}
+
+```yaml
+Type: System.DateTime
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ContentExtensionMatchesWords
+{{ Fill ContentExtensionMatchesWords Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ContentPropertyContainsWords
+{{ Fill ContentPropertyContainsWords Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExceptIfContentExtensionMatchesWords
+{{ Fill ExceptIfContentExtensionMatchesWords Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExceptIfContentPropertyContainsWords
+{{ Fill ExceptIfContentPropertyContainsWords Description }}
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -StartImpactAssessment
+{{ Fill StartImpactAssessment Description }}
+
+```yaml
+Type: Boolean
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+The WhatIf switch doesn't work in Security & Compliance PowerShell.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -Workload
+The Workload parameter specifies the workload. Valid values are:
+
+- Applications
+- AuditAlerting
+- AWS
+- Azure
+- AzureBatch
+- Copilot
+- DynamicScope
+- EndpointDevices
+- Exchange
+- ExchangeOnPremises
+- Intune
+- ModernGroup
+- OneDriveForBusiness
+- OnPremisesScanner
+- PowerBI
+- PublicFolder
+- SharePoint
+- SharePointOnPremises
+- Skype
+- Substrate
+- Teams
+- ThirdPartyApps
+- UnifiedAuditAzure
+
+This value appears in the LogicalWorkload property in the output of the Get-SensitiveInformationScanRule cmdlet.
+
+```yaml
+Type: PolicyConfiguration.Workload
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### CommonParameters
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).
+
+## INPUTS
+
+## OUTPUTS
+
+## NOTES
+
+## RELATED LINKS

From 750ed098b0a061141881ba2230036f28d6f31ace Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Mon, 9 Jun 2025 17:17:50 -0700
Subject: [PATCH 02/21] Copied param descriptions

---
 .../exchange/Get-SensitiveInformationScan.md  |   2 +-
 .../Get-SensitiveInformationScanRule.md       |   2 +-
 .../exchange/New-SensitiveInformationScan.md  |  32 +++-
 .../New-SensitiveInformationScanRule.md       |  14 +-
 .../exchange/Set-SensitiveInformationScan.md  | 169 ++++++++++++++----
 .../Set-SensitiveInformationScanRule.md       |  16 +-
 6 files changed, 179 insertions(+), 56 deletions(-)

diff --git a/exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md
index 78ddca81f9..7547c958c0 100644
--- a/exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Get-SensitiveInformationScan cmdlet to view sensitive information scans.
+Use the Get-SensitiveInformationScan cmdlet to view the properties of sensitive information scans.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md
index 6b0f999225..6cf020dc48 100644
--- a/exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Get-SensitiveInformationScanRule cmdlet to
+Use the Get-SensitiveInformationScanRule cmdlet to view sensitive information scan rules.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
index 0eaa365532..ba774165ba 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the New-SensitiveInformationScan cmdlet to
+Use the New-SensitiveInformationScan cmdlet to create sensitive information scans.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -61,7 +61,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 ## PARAMETERS
 
 ### -Name
-{{ Fill Name Description }}
+The Name parameter specifies the unique name of the scan. If the value contains spaces, enclose the value in quotation marks.
 
 ```yaml
 Type: String
@@ -156,7 +156,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfOneDriveSharedBy
-The ExceptIfOneDriveSharedBy parameter specifies the users to exclude from the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (laura@contoso.onmicrosoft.com).
+The ExceptIfOneDriveSharedBy parameter specifies the users to exclude from the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
 
 To use this parameter, OneDrive sites need to be included in the scan (the OneDriveLocation parameter value is All, which is the default value).
 
@@ -355,7 +355,7 @@ Accept wildcard characters: False
 ```
 
 ### -OneDriveSharedBy
-The OneDriveSharedBy parameter specifies the users to include in the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (laura@contoso.onmicrosoft.com).
+The OneDriveSharedBy parameter specifies the users to include in the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
 
 To use this parameter, OneDrive sites need to be included in the scan (the OneDriveLocation parameter value is All, which is the default value).
 
@@ -401,7 +401,9 @@ Accept wildcard characters: False
 ```
 
 ### -PolicyRBACScopes
-{{ Fill PolicyRBACScopes Description }}
+The PolicyRBACScopes parameter specifies the administrative units to assign to the scan. A valid value is the Microsoft Entra ObjectID (GUID value) of the administrative unit. You can specify multiple values separated by commas.
+
+Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell.
 
 ```yaml
 Type: MultiValuedProperty
@@ -417,7 +419,11 @@ Accept wildcard characters: False
 ```
 
 ### -SharePointLocation
-{{ Fill SharePointLocation Description }}
+The SharePointLocation parameter specifies the SharePoint sites to include in the scan. You identify the site by its URL value, or you can use the value All to include all sites.
+
+You can't add SharePoint sites to the policy until they have been indexed.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -433,7 +439,11 @@ Accept wildcard characters: False
 ```
 
 ### -SharePointLocationException
-{{ Fill SharePointLocationException Description }}
+The SharePointLocationException parameter specifies the SharePoint sites to exclude when you use the value All for the SharePointLocation parameter. You identify the site by its URL value.
+
+You can't add SharePoint sites to the scan until they have been indexed.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -449,7 +459,9 @@ Accept wildcard characters: False
 ```
 
 ### -TeamsLocation
-{{ Fill TeamsLocation Description }}
+The TeamsLocation parameter specifies the Teams chat and channel messages to include in the scan. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group. You can use the value All to include all accounts, distribution groups, and mail-enabled security groups.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -465,7 +477,9 @@ Accept wildcard characters: False
 ```
 
 ### -TeamsLocationException
-{{ Fill TeamsLocationException Description }}
+The TeamsLocation parameter specifies the Teams chat and channel messages to exclude from the DLP policy when you use the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
index fdfba641e6..96d0e19fc1 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the New-SensitiveInformationScan cmdlet to
+Use the New-SensitiveInformationScan cmdlet to create sensitive information scan rules.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -191,7 +191,7 @@ Accept wildcard characters: False
 ```
 
 ### -ContentExtensionMatchesWords
-{{ Fill ContentExtensionMatchesWords Description }}
+The ContentExtensionMatchesWords parameter specifies a condition for the rule that looks for words in file extensions. You can specify multiple words separated by commas. Irrespective of the original file type, this predicate matches based on the extension that is present in the name of the file.
 
 ```yaml
 Type: MultiValuedProperty
@@ -207,7 +207,9 @@ Accept wildcard characters: False
 ```
 
 ### -ContentPropertyContainsWords
-{{ Fill ContentPropertyContainsWords Description }}
+The ContentPropertyContainsWords parameter specifies a condition for the rule that's based on a property match in content. The rule is applied to content that contains the specified property.
+
+This parameter accepts values in the format: `"Property1:Value1,Value2","Property2:Value3,Value4",..."PropertyN:ValueN,ValueN"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -223,7 +225,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfContentExtensionMatchesWords
-{{ Fill ExceptIfContentExtensionMatchesWords Description }}
+The ExceptIfContentExtensionMatchesWords parameter specifies an exception for the rule that looks for words in file extensions. You can specify multiple words separated by commas. Irrespective of what the original file type is, this predicate matches based on the extension that is present in the name of the file.
 
 ```yaml
 Type: MultiValuedProperty
@@ -239,7 +241,9 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfContentPropertyContainsWords
-{{ Fill ExceptIfContentPropertyContainsWords Description }}
+The ExceptIfContentPropertyContainsWords parameter specifies an exception for the rule that's based on a property match in content. The rule is not applied to content that contains the specified property.
+
+This parameter accepts values in the format: `"Property1:Value1,Value2","Property2:Value3,Value4",..."PropertyN:ValueN,ValueN"`.
 
 ```yaml
 Type: MultiValuedProperty
diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
index f8d37f8b8c..637565cde2 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Set-SensitiveInformationScan cmdlet to
+Use the Set-SensitiveInformationScan cmdlet to modify sensitive information scans.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -94,7 +94,13 @@ Accept wildcard characters: False
 ```
 
 ### -AddEndpointDlpLocation
-{{ Fill AddEndpointDlpLocation Description }}
+**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
+
+The AddEndpointDLPLocation parameter specifies the user accounts to add to the list of included accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
 
 ```yaml
 Type: MultiValuedProperty
@@ -110,7 +116,13 @@ Accept wildcard characters: False
 ```
 
 ### -AddEndpointDlpLocationException
-{{ Fill AddEndpointDlpLocationException Description }}
+**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
+
+The AddEndpointDlpLocationException parameter specifies the user accounts to add to the list of excluded accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
 
 ```yaml
 Type: MultiValuedProperty
@@ -126,7 +138,15 @@ Accept wildcard characters: False
 ```
 
 ### -AddExchangeLocation
-{{ Fill AddExchangeLocation Description }}
+The AddExchangeLocation parameter adds email messages to the scan if they're not already included. The valid value for this parameter is All.
+
+If the scan doesn't already include email messages (in the output of the Get-DlpCompliancePolicy cmdlet, the ExchangeLocation property value is blank), you can use this parameter in the following procedures:
+
+- If you use `-AddExchangeLocation All` by itself, the scan applies to email for all users.
+
+- To include email of specific group members in the scan, use `-AddExchangeLocation All` with the ExchangeSenderMemberOf parameter in the same command. Only email of members of the specified groups is included in the scan.
+
+- To exclude email of specific group members from the scan, use `-AddExchangeLocation All` with the ExchangeSenderMemberOfException parameter in the same command. Only email of members of the specified groups is excluded from the scan.
 
 ```yaml
 Type: MultiValuedProperty
@@ -142,7 +162,9 @@ Accept wildcard characters: False
 ```
 
 ### -AddOneDriveLocation
-{{ Fill AddOneDriveLocation Description }}
+The AddOneDriveLocation parameter specifies the OneDrive sites to add to the list of included sites when you aren't using the value All for the OneDriveLocation parameter. You identify the site by its URL value.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -158,7 +180,9 @@ Accept wildcard characters: False
 ```
 
 ### -AddOneDriveLocationException
-{{ Fill AddOneDriveLocationException Description }}
+The AddOneDriveLocationException parameter specifies the OneDrive sites to add to the list of excluded sites when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -174,7 +198,11 @@ Accept wildcard characters: False
 ```
 
 ### -AddSharePointLocation
-{{ Fill AddSharePointLocation Description }}
+The AddSharePointLocation parameter specifies the SharePoint sites to add to the list of included sites if you used the value All for the SharePointLocation parameter. You identify the site by its URL value.
+
+You can't add SharePoint sites to the scan until they have been indexed.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -190,7 +218,11 @@ Accept wildcard characters: False
 ```
 
 ### -AddSharePointLocationException
-{{ Fill AddSharePointLocationException Description }}
+The AddSharePointLocationException parameter specifies the SharePoint sites to add to the list of excluded sites if you used the value All for the SharePointLocation parameter. You identify the site by its URL value.
+
+You can't add SharePoint sites to the scan until they have been indexed.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -206,7 +238,9 @@ Accept wildcard characters: False
 ```
 
 ### -AddTeamsLocation
-{{ Fill AddTeamsLocation Description }}
+The AddTeamsLocation parameter specifies the accounts, distribution groups, or mail-enabled security groups to add to the list of included Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -222,7 +256,9 @@ Accept wildcard characters: False
 ```
 
 ### -AddTeamsLocationException
-{{ Fill AddTeamsLocationException Description }}
+The AddTeamsLocationException parameter specifies the accounts, distribution groups, or mail-enabled security groups to add to the list of excluded Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -289,9 +325,12 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfOneDriveSharedBy
-The ExceptIfOneDriveSharedBy parameter specifies the users to exclude from the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (laura@contoso.onmicrosoft.com).
+The ExceptIfOneDriveSharedBy parameter specifies the users to exclude from the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
 
-To use this parameter, OneDrive sites need to be included in the scan (the OneDriveLocation parameter value is All, which is the default value).
+To use this parameter, one of the following statements must be true:
+
+- The scan already includes OneDrive sites (in the output of Get-DlpCOmpliancePolicy, the OneDriveLocation property value is All, which is the default value).
+- Use `-AddOneDriveLocation All` in the same command with this parameter.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
@@ -311,7 +350,18 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfOneDriveSharedByMemberOf
-{{ Fill ExceptIfOneDriveSharedByMemberOf Description }}
+The ExceptIfOneDriveSharedByMemberOf parameter specifies the distribution groups or mail-enabled security groups to exclude from the scan (the OneDrive sites of group members are excluded from the scan). You identify the groups by email address.
+
+To use this parameter, one of the following statements must be true:
+
+- The scan already includes OneDrive sites (in the output of Get-DlpCOmpliancePolicy, the OneDriveLocation property value is All, which is the default value).
+- Use `-AddOneDriveLocation All` in the same command with this parameter.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You can't use this parameter with the OneDriveSharedBy or OneDriveSharedByMemberOf parameters.
+
+You can't use this parameter to specify Microsoft 365 Groups.
 
 ```yaml
 Type: RecipientIdParameter[]
@@ -327,11 +377,14 @@ Accept wildcard characters: False
 ```
 
 ### -ExchangeSender
-The ExchangeSender parameter specifies the users whose email is included in the scan. You identify the users by email address. You can specify internal or external email addresses.
+The ExchangeSender parameter specifies the users whose email is included in the scan. You specify the users by email address. You can specify internal or external email addresses.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
-You must use this parameter with the ExchangeLocation parameter.
+To use this parameter, one of the following statements must be true:
+
+- The scan already includes email messages (in the output of the Get-SensitiveInformationScan cmdlet, the ExchangeLocation property value is All).
+- Use `-AddExchangeLocation All` in the same command with this parameter.
 
 You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters.
 
@@ -353,7 +406,10 @@ The ExchangeSenderException parameter specifies the internal users whose email i
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
-You must use this parameter with the ExchangeLocation parameter.
+To use this parameter, one of the following statements must be true:
+
+- The scan already includes email messages (in the output of Get-SensitiveInformationScan, the ExchangeLocation property value is All).
+- Use `-AddExchangeLocation All` in the same command with this parameter.
 
 You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
 
@@ -371,13 +427,16 @@ Accept wildcard characters: False
 ```
 
 ### -ExchangeSenderMemberOf
-The ExchangeSenderMemberOf parameter specifies the distribution groups or security groups to include in the scan (email of the group members is included in the scan). You identify the groups by email address.
+The ExchangeSenderMemberOf parameter specifies the distribution groups or mail-enabled security groups to include in the scan (email of the group members is included in the scan). You identify the groups by email address.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
-You must use this parameter with the ExchangeLocation parameter.
+To use this parameter, one of the following statements must be true:
+
+- The scan already includes email messages (in the output of Get-SensitiveInformationScan, the ExchangeLocation property value is All).
+- Use `-AddExchangeLocation All` in the same command with this parameter.
 
-You can't use this parameter with the ExchangeSenderMemberOfException parameter.
+You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters.
 
 You can't use this parameter to specify Microsoft 365 Groups.
 
@@ -395,11 +454,14 @@ Accept wildcard characters: False
 ```
 
 ### -ExchangeSenderMemberOfException
-The ExchangeSenderMemberOfException parameter specifies the distribution groups or security groups to exclude from the scan (email of the group members is excluded from the scan). You identify the groups by email address.
+The ExchangeSenderMemberOfException parameter specifies the distribution groups or mail-enabled security groups to exclude from the scan (email of the group members is excluded from the scan). You identify the groups by email address.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
-You must use this parameter with the ExchangeLocation parameter.
+To use this parameter, one of the following statements must be true:
+
+- The scan already includes email messages (in the output of Get-SensitiveInformationScan, the ExchangeLocation property value is All).
+- Use `-AddExchangeLocation All` in the same command with this parameter.
 
 You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
 
@@ -435,11 +497,11 @@ Accept wildcard characters: False
 ```
 
 ### -OneDriveSharedBy
-The OneDriveSharedBy parameter specifies the users to include in the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (laura@contoso.onmicrosoft.com).
+The OneDriveSharedBy parameter specifies the users to include in the DLP scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
 
 To use this parameter, one of the following statements must be true:
 
-- The scan already includes OneDrive sites (in the output of Get-DlpCOmpliancePolicy, the OneDriveLocation property value is All, which is the default value).
+- The scan already includes OneDrive sites (in the output of Get-SensitiveInformationScan, the OneDriveLocation property value is All, which is the default value).
 - Use `-AddOneDriveLocation All` in the same command with this parameter.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
@@ -460,7 +522,18 @@ Accept wildcard characters: False
 ```
 
 ### -OneDriveSharedByMemberOf
-{{ Fill OneDriveSharedByMemberOf Description }}
+The OneDriveSharedByMemberOf parameter specifies the distribution groups or mail-enabled security groups to include in the DLP scan (the OneDrive sites of group members are included in the scan). You identify the groups by email address.
+
+To use this parameter, one of the following statements must be true:
+
+- The scan already includes OneDrive sites (in the output of Get-SensitiveInformationScan, the OneDriveLocation property value is All, which is the default value).
+- Use `-AddOneDriveLocation All` in the same command with this parameter.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+You can't use this parameter with the ExceptIfOneDriveSharedBy or ExceptIfOneDriveSharedByMemberOf parameters.
+
+You can't use this parameter to specify Microsoft 365 Groups.
 
 ```yaml
 Type: RecipientIdParameter[]
@@ -476,7 +549,9 @@ Accept wildcard characters: False
 ```
 
 ### -PolicyRBACScopes
-{{ Fill PolicyRBACScopes Description }}
+The PolicyRBACScopes parameter specifies the administrative units to assign to the scan. A valid value is the Microsoft Entra ObjectID (GUID value) of the administrative unit. You can specify multiple values separated by commas.
+
+Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell.
 
 ```yaml
 Type: MultiValuedProperty
@@ -492,7 +567,13 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveEndpointDlpLocation
-{{ Fill RemoveEndpointDlpLocation Description }}
+**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
+
+The RemoveEndpointDlpLocation parameter specifies the user accounts to remove from the list of included accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You specify the account by name or email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
 
 ```yaml
 Type: MultiValuedProperty
@@ -508,7 +589,13 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveEndpointDlpLocationException
-{{ Fill RemoveEndpointDlpLocationException Description }}
+**Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
+
+The RemoveEndpointDlpLocation parameter specifies the user accounts to remove from the list of excluded accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You specify the account by name or email address.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+
+For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
 
 ```yaml
 Type: MultiValuedProperty
@@ -524,7 +611,9 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveExchangeLocation
-{{ Fill RemoveExchangeLocation Description }}
+The RemoveExchangeLocation parameter removes email messages from the scan if they're already included. The valid value for this parameter is All.
+
+If the scan already includes email messages (in the output of the Get-DlpCompliancePolicy cmdlet, the ExchangeLocation property value is All), you can use `-RemoveExchangeLocation All` to prevent the scan from applying to email messages.
 
 ```yaml
 Type: MultiValuedProperty
@@ -540,7 +629,9 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveOneDriveLocation
-{{ Fill RemoveOneDriveLocation Description }}
+The RemoveOneDriveLocation parameter specifies the OneDrive sites to remove from the list of included sites when you aren't using the value All for the OneDriveLocation parameter. You identify the site by its URL value.
+
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -556,7 +647,9 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveOneDriveLocationException
-{{ Fill RemoveOneDriveLocationException Description }}
+This parameter specifies the OneDrive sites to remove from the list of excluded sites when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value.
+
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -572,7 +665,9 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveSharePointLocation
-{{ Fill RemoveSharePointLocation Description }}
+The RemoveSharePointLocation parameter specifies the SharePoint sites to remove from the list of included sites if you used the value All for the SharePointLocation parameter. You specify the site by its URL value.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -588,7 +683,9 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveSharePointLocationException
-{{ Fill RemoveSharePointLocationException Description }}
+The RemoveSharePointLocationException parameter specifies the SharePoint sites to remove from the list of excluded sites if you used the value All for the SharePointLocation parameter. You specify the site by its URL value.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -604,7 +701,9 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveTeamsLocation
-{{ Fill RemoveTeamsLocation Description }}
+The RemoveTeamsLocation parameter specifies the accounts, distribution groups, or mail-enabled security groups to remove from the list of included Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You specify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -620,7 +719,9 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveTeamsLocationException
-{{ Fill RemoveTeamsLocationException Description }}
+The RemoveTeamsLocationException parameter specifies the accounts, distribution groups, or mail-enabled security groups to remove from the list of excluded Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
+
+To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
 ```yaml
 Type:MultiValuedProperty
diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
index b19aade77b..e941622f3d 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Set-SensitiveInformationScan cmdlet to
+Use the Set-SensitiveInformationScan cmdlet to modify sensitive information scan rules.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -43,7 +43,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 
 ### Example 1
 ```powershell
-PS C:\> {{ Add example code here }}
+{{ Add example code here }}
 ```
 
 {{ Add example description here }}
@@ -138,7 +138,7 @@ Accept wildcard characters: False
 ```
 
 ### -ContentExtensionMatchesWords
-{{ Fill ContentExtensionMatchesWords Description }}
+The ContentExtensionMatchesWords parameter specifies a condition for the rule that looks for words in file extensions. You can specify multiple words separated by commas. Irrespective of the original file type, this predicate matches based on the extension that is present in the name of the file.
 
 ```yaml
 Type: MultiValuedProperty
@@ -154,7 +154,9 @@ Accept wildcard characters: False
 ```
 
 ### -ContentPropertyContainsWords
-{{ Fill ContentPropertyContainsWords Description }}
+The ContentPropertyContainsWords parameter specifies a condition for the rule that's based on a property match in content. The rule is applied to content that contains the specified property.
+
+This parameter accepts values in the format: `"Property1:Value1,Value2","Property2:Value3,Value4",..."PropertyN:ValueN,ValueN"`.
 
 ```yaml
 Type: MultiValuedProperty
@@ -170,7 +172,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfContentExtensionMatchesWords
-{{ Fill ExceptIfContentExtensionMatchesWords Description }}
+The ExceptIfContentExtensionMatchesWords parameter specifies an exception for the rule that looks for words in file extensions. You can specify multiple words separated by commas. Irrespective of what the original file type is, this predicate matches based on the extension that is present in the name of the file.
 
 ```yaml
 Type: MultiValuedProperty
@@ -186,7 +188,9 @@ Accept wildcard characters: False
 ```
 
 ### -ExceptIfContentPropertyContainsWords
-{{ Fill ExceptIfContentPropertyContainsWords Description }}
+The ExceptIfContentPropertyContainsWords parameter specifies an exception for the DLP rule that's based on a property match in content. The rule is not applied to content that contains the specified property.
+
+This parameter accepts values in the format: `"Property1:Value1,Value2","Property2:Value3,Value4",..."PropertyN:ValueN,ValueN"`.
 
 ```yaml
 Type: MultiValuedProperty

From 17a1f2af53d1a20724d3faf7aaaedf7809a87bec Mon Sep 17 00:00:00 2001
From: Aakash Malhotra <53205984+aamalhot@users.noreply.github.com>
Date: Tue, 10 Jun 2025 14:51:03 +0530
Subject: [PATCH 03/21] Update New-SensitiveInformationScan.md

Only endpoint, onedrive, sharepoint are in scope of current release
---
 .../exchange/New-SensitiveInformationScan.md  | 242 +-----------------
 1 file changed, 5 insertions(+), 237 deletions(-)

diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
index ba774165ba..6b212374f8 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the New-SensitiveInformationScan cmdlet to create sensitive information scans.
+Use the New-SensitiveInformationScan cmdlet to create a new on-demand classification scan. Learn more about On-demand classification [https://learn.microsoft.com/purview/on-demand-classification].
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -28,20 +28,10 @@ New-SensitiveInformationScan [-Name] <String>
  [-EndpointDlpLocationException <MultiValuedProperty>]
  [-ExceptIfOneDriveSharedBy <RecipientIdParameter[]>]
  [-ExceptIfOneDriveSharedByMemberOf <RecipientIdParameter[]>]
- [-ExchangeLocation <MultiValuedProperty>]
- [-ExchangeSender <SmtpAddress[]>]
- [-ExchangeSenderException <SmtpAddress[]>]
- [-ExchangeSenderMemberOf <RecipientIdParameter[]>]
- [-ExchangeSenderMemberOfException <RecipientIdParameter[]>]
- [-OneDriveLocation <MultiValuedProperty>]
- [-OneDriveLocationException <MultiValuedProperty>]
  [-OneDriveSharedBy <RecipientIdParameter[]>]
  [-OneDriveSharedByMemberOf <RecipientIdParameter[]>]
- [-PolicyRBACScopes <MultiValuedProperty>]
  [-SharePointLocation <MultiValuedProperty>]
  [-SharePointLocationException <MultiValuedProperty>]
- [-TeamsLocation <MultiValuedProperty>]
- [-TeamsLocationException <MultiValuedProperty>]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -114,11 +104,11 @@ Accept wildcard characters: False
 ### -EndpointDlpLocation
 **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
 
-The EndpointDLPLocation parameter specifies the user accounts to include in scan for Endpoint DLP when they are logged on to an onboarded device. You identify the account by name or email address. You can use the value All to include all user accounts.
+The EndpointDLPLocation parameter specifies the user accounts to include in scan for devices. You identify the account by name or email address. You can use the value All to include all user accounts.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
-For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
+For more information about onboarding devices to Purview, see [Learn about device onboarding](https://learn.microsoft.com/purview/endpoint-dlp-getting-started)).
 
 ```yaml
 Type: MultiValuedProperty
@@ -136,11 +126,11 @@ Accept wildcard characters: False
 ### -EndpointDlpLocationException
 **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
 
-The EndpointDlpLocationException parameter specifies the user accounts to exclude from Endpoint DLP when you use the value All for the EndpointDlpLocation parameter. You identify the account by name or email address.
+The EndpointDlpLocationException parameter specifies the user accounts to exclude in an on-demand classification scan for devices. You identify the account by name or email address. 
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
-For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
+For more information about onboarding devices to Purview, see [Learn about device onboarding](https://learn.microsoft.com/purview/endpoint-dlp-getting-started)).
 
 ```yaml
 Type: MultiValuedProperty
@@ -201,159 +191,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -ExchangeLocation
-The ExchangeLocation parameter specifies whether to include email messages in the scan. The valid value for this parameter is All. If you don't want to include email messages in the scan, don't use this parameter (the default value is blank or $null).
-
-You can use this parameter in the following procedures:
-
-- If you use `-ExchangeLocation All` by itself, the scan applies to email for all users.
-
-- To include email of specific group members in the scan, use `-ExchangeLocation All` with the ExchangeSenderMemberOf parameter in the same command. Only email of members of the specified groups is included in the scan.
-
-- To exclude email of specific group members from the scan, use `-ExchangeLocation All` with the ExchangeSenderMemberOfException parameter in the same command. Only email of members of the specified groups is excluded from the scan.
-
-You can't specify inclusions and exclusions in the same scan.
-
-```yaml
-Type: MultiValuedProperty
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -ExchangeSender
-The ExchangeSender parameter specifies the users whose email is included in the scan. You identify the users by email address. You can specify internal or external email addresses.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-You must use this parameter with the ExchangeLocation parameter.
-
-You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters.
-
-```yaml
-Type: SmtpAddress[]
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -ExchangeSenderException
-The ExchangeSenderException parameter specifies the internal users whose email is excluded from the scan. You identify the users by email address.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-You must use this parameter with the ExchangeLocation parameter.
-
-You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
-
-```yaml
-Type: SmtpAddress[]
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -ExchangeSenderMemberOf
-The ExchangeSenderMemberOf parameter specifies the distribution groups or security groups to include in the scan (email of the group members is included in the scan). You identify the groups by email address.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-You must use this parameter with the ExchangeLocation parameter.
-
-You can't use this parameter with the ExchangeSenderMemberOfException parameter.
-
-You can't use this parameter to specify Microsoft 365 Groups.
-
-```yaml
-Type: RecipientIdParameter[]
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -ExchangeSenderMemberOfException
-The ExchangeSenderMemberOfException parameter specifies the distribution groups or security groups to exclude from the scan (email of the group members is excluded from the scan). You identify the groups by email address.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-You must use this parameter with the ExchangeLocation parameter.
-
-You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
-
-You can't use this parameter to specify Microsoft 365 Groups.
-
-```yaml
-Type: RecipientIdParameter[]
-Parameter Sets: (All)
-Aliases:
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -OneDriveLocation
-The OneDriveLocation parameter specifies the OneDrive sites to include in the scan. You identify the site by its URL value, or you can use the value All to include all sites.
-
-You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
-
-```yaml
-Type: MultiValuedProperty
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -OneDriveLocationException
-This parameter specifies the OneDrive sites to exclude when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value.
-
-You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
-
-```yaml
-Type: MultiValuedProperty
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -OneDriveSharedBy
 The OneDriveSharedBy parameter specifies the users to include in the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
 
@@ -400,24 +237,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -PolicyRBACScopes
-The PolicyRBACScopes parameter specifies the administrative units to assign to the scan. A valid value is the Microsoft Entra ObjectID (GUID value) of the administrative unit. You can specify multiple values separated by commas.
-
-Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell.
-
-```yaml
-Type: MultiValuedProperty
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -SharePointLocation
 The SharePointLocation parameter specifies the SharePoint sites to include in the scan. You identify the site by its URL value, or you can use the value All to include all sites.
 
@@ -458,57 +277,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -TeamsLocation
-The TeamsLocation parameter specifies the Teams chat and channel messages to include in the scan. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group. You can use the value All to include all accounts, distribution groups, and mail-enabled security groups.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-```yaml
-Type: MultiValuedProperty
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -TeamsLocationException
-The TeamsLocation parameter specifies the Teams chat and channel messages to exclude from the DLP policy when you use the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-```yaml
-Type: MultiValuedProperty
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -WhatIf
-The WhatIf switch doesn't work in Security & Compliance PowerShell.
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases: wi
-Applicable:
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
 
 ### CommonParameters
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).

From 2f8c34787c47dde256974027584fb4130a86a1f9 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 10 Jun 2025 19:32:10 -0700
Subject: [PATCH 04/21] Update New-SensitiveInformationScan.md

---
 .../exchange/New-SensitiveInformationScan.md  | 177 +++++++++++++++++-
 1 file changed, 176 insertions(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
index 6b212374f8..f67fc7f0ac 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the New-SensitiveInformationScan cmdlet to create a new on-demand classification scan. Learn more about On-demand classification [https://learn.microsoft.com/purview/on-demand-classification].
+Use the New-SensitiveInformationScan cmdlet to create new on-demand classification scans. Learn more about on-demand classifications at [On-demand classification](https://learn.microsoft.com/purview/on-demand-classification).
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -28,10 +28,20 @@ New-SensitiveInformationScan [-Name] <String>
  [-EndpointDlpLocationException <MultiValuedProperty>]
  [-ExceptIfOneDriveSharedBy <RecipientIdParameter[]>]
  [-ExceptIfOneDriveSharedByMemberOf <RecipientIdParameter[]>]
+ [-ExchangeLocation <MultiValuedProperty>]
+ [-ExchangeSender <SmtpAddress[]>]
+ [-ExchangeSenderException <SmtpAddress[]>]
+ [-ExchangeSenderMemberOf <RecipientIdParameter[]>]
+ [-ExchangeSenderMemberOfException <RecipientIdParameter[]>]
+ [-OneDriveLocation <MultiValuedProperty>]
+ [-OneDriveLocationException <MultiValuedProperty>]
  [-OneDriveSharedBy <RecipientIdParameter[]>]
  [-OneDriveSharedByMemberOf <RecipientIdParameter[]>]
+ [-PolicyRBACScopes <MultiValuedProperty>]
  [-SharePointLocation <MultiValuedProperty>]
  [-SharePointLocationException <MultiValuedProperty>]
+ [-TeamsLocation <MultiValuedProperty>]
+ [-TeamsLocationException <MultiValuedProperty>]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -191,6 +201,112 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -ExchangeLocation
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSender
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: SmtpAddress[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderException
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: SmtpAddress[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderMemberOf
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -ExchangeSenderMemberOfException
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: RecipientIdParameter[]
+Parameter Sets: (All)
+Aliases:
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -OneDriveLocation
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -OneDriveLocationException
+This parameter specifies the OneDrive sites to exclude when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value.
+
+You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -OneDriveSharedBy
 The OneDriveSharedBy parameter specifies the users to include in the scan (the sites of the OneDrive user accounts are included in the scan). You identify the users by UPN (`laura@contoso.onmicrosoft.com`).
 
@@ -237,6 +353,21 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -PolicyRBACScopes
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -SharePointLocation
 The SharePointLocation parameter specifies the SharePoint sites to include in the scan. You identify the site by its URL value, or you can use the value All to include all sites.
 
@@ -277,6 +408,50 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -TeamsLocation
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -TeamsLocationException
+This parameter is reserved for internal Microsoft use.
+
+```yaml
+Type: MultiValuedProperty
+Parameter Sets: (All)
+Aliases:
+Applicable: Security & Compliance
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
+### -WhatIf
+The WhatIf switch doesn't work in Security & Compliance PowerShell.
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: wi
+Applicable:
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
 
 ### CommonParameters
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216).

From 29eeb82b9cea024da837f0a4c9b3385ca5c027b6 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 10 Jun 2025 19:34:04 -0700
Subject: [PATCH 05/21] Update New-SensitiveInformationScan.md

---
 .../exchange/New-SensitiveInformationScan.md       | 14 +++++++++++++-
 1 file changed, 13 insertions(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
index f67fc7f0ac..f019f75294 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
@@ -209,6 +209,7 @@ Type: MultiValuedProperty
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -224,6 +225,7 @@ Type: SmtpAddress[]
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -239,6 +241,7 @@ Type: SmtpAddress[]
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -254,6 +257,7 @@ Type: RecipientIdParameter[]
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -268,6 +272,8 @@ This parameter is reserved for internal Microsoft use.
 Type: RecipientIdParameter[]
 Parameter Sets: (All)
 Aliases:
+Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -283,6 +289,7 @@ Type: MultiValuedProperty
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -300,6 +307,7 @@ Type: MultiValuedProperty
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -361,6 +369,7 @@ Type: MultiValuedProperty
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -416,6 +425,7 @@ Type: MultiValuedProperty
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -431,6 +441,7 @@ Type: MultiValuedProperty
 Parameter Sets: (All)
 Aliases:
 Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None
@@ -445,7 +456,8 @@ The WhatIf switch doesn't work in Security & Compliance PowerShell.
 Type: SwitchParameter
 Parameter Sets: (All)
 Aliases: wi
-Applicable:
+Applicable: Security & Compliance
+
 Required: False
 Position: Named
 Default value: None

From 3129358586223742f920913ddc462e78a8f52b85 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Tue, 10 Jun 2025 19:45:02 -0700
Subject: [PATCH 06/21] Update New-ApplicationAccessPolicy.md

Typo fix
---
 exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md b/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md
index bc6d569955..3a8139e536 100644
--- a/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md
+++ b/exchange/exchange-ps/exchange/New-ApplicationAccessPolicy.md
@@ -15,7 +15,7 @@ ms.reviewer:
 This cmdlet is available only in the cloud-based service.
 
 > [!IMPORTANT]
-> App Access Policies will soon be replaced by Role Based Access Control for Applications. To learn more, see [Roles Based Access Control for Exchange Applications](https://learn.microsoft.com/exchange/permissions-exo/application-rbac).
+> App Access Policies will soon be replaced by Role Based Access Control for Applications. To learn more, see [Role Based Access Control for Exchange Applications](https://learn.microsoft.com/exchange/permissions-exo/application-rbac).
 
 Use the New-ApplicationAccessPolicy cmdlet to restrict or deny access to a specific set of mailboxes by an application that uses APIs (Outlook REST, Microsoft Graph, or Exchange Web Services (EWS)). These policies are complementary to the permission scopes that are declared by the application.
 

From d6480f96789486e812f8644a45521af7565499e4 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 11 Jun 2025 08:36:36 -0700
Subject: [PATCH 07/21] Update Set-SensitiveInformationScan.md

Updates to match New-
---
 .../exchange/Set-SensitiveInformationScan.md  | 90 +++----------------
 1 file changed, 13 insertions(+), 77 deletions(-)

diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
index 637565cde2..eb9a12589a 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
@@ -138,15 +138,7 @@ Accept wildcard characters: False
 ```
 
 ### -AddExchangeLocation
-The AddExchangeLocation parameter adds email messages to the scan if they're not already included. The valid value for this parameter is All.
-
-If the scan doesn't already include email messages (in the output of the Get-DlpCompliancePolicy cmdlet, the ExchangeLocation property value is blank), you can use this parameter in the following procedures:
-
-- If you use `-AddExchangeLocation All` by itself, the scan applies to email for all users.
-
-- To include email of specific group members in the scan, use `-AddExchangeLocation All` with the ExchangeSenderMemberOf parameter in the same command. Only email of members of the specified groups is included in the scan.
-
-- To exclude email of specific group members from the scan, use `-AddExchangeLocation All` with the ExchangeSenderMemberOfException parameter in the same command. Only email of members of the specified groups is excluded from the scan.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty
@@ -162,9 +154,7 @@ Accept wildcard characters: False
 ```
 
 ### -AddOneDriveLocation
-The AddOneDriveLocation parameter specifies the OneDrive sites to add to the list of included sites when you aren't using the value All for the OneDriveLocation parameter. You identify the site by its URL value.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty
@@ -180,9 +170,7 @@ Accept wildcard characters: False
 ```
 
 ### -AddOneDriveLocationException
-The AddOneDriveLocationException parameter specifies the OneDrive sites to add to the list of excluded sites when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty
@@ -238,9 +226,7 @@ Accept wildcard characters: False
 ```
 
 ### -AddTeamsLocation
-The AddTeamsLocation parameter specifies the accounts, distribution groups, or mail-enabled security groups to add to the list of included Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty
@@ -256,9 +242,7 @@ Accept wildcard characters: False
 ```
 
 ### -AddTeamsLocationException
-The AddTeamsLocationException parameter specifies the accounts, distribution groups, or mail-enabled security groups to add to the list of excluded Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty
@@ -377,16 +361,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExchangeSender
-The ExchangeSender parameter specifies the users whose email is included in the scan. You specify the users by email address. You can specify internal or external email addresses.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-To use this parameter, one of the following statements must be true:
-
-- The scan already includes email messages (in the output of the Get-SensitiveInformationScan cmdlet, the ExchangeLocation property value is All).
-- Use `-AddExchangeLocation All` in the same command with this parameter.
-
-You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: SmtpAddress[]
@@ -402,16 +377,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExchangeSenderException
-The ExchangeSenderException parameter specifies the internal users whose email is excluded from the scan. You identify the users by email address.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-To use this parameter, one of the following statements must be true:
-
-- The scan already includes email messages (in the output of Get-SensitiveInformationScan, the ExchangeLocation property value is All).
-- Use `-AddExchangeLocation All` in the same command with this parameter.
-
-You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: SmtpAddress[]
@@ -427,18 +393,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExchangeSenderMemberOf
-The ExchangeSenderMemberOf parameter specifies the distribution groups or mail-enabled security groups to include in the scan (email of the group members is included in the scan). You identify the groups by email address.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-To use this parameter, one of the following statements must be true:
-
-- The scan already includes email messages (in the output of Get-SensitiveInformationScan, the ExchangeLocation property value is All).
-- Use `-AddExchangeLocation All` in the same command with this parameter.
-
-You can't use this parameter with the ExchangeSenderException or ExchangeSenderMemberOfException parameters.
-
-You can't use this parameter to specify Microsoft 365 Groups.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: RecipientIdParameter[]
@@ -454,18 +409,7 @@ Accept wildcard characters: False
 ```
 
 ### -ExchangeSenderMemberOfException
-The ExchangeSenderMemberOfException parameter specifies the distribution groups or mail-enabled security groups to exclude from the scan (email of the group members is excluded from the scan). You identify the groups by email address.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
-
-To use this parameter, one of the following statements must be true:
-
-- The scan already includes email messages (in the output of Get-SensitiveInformationScan, the ExchangeLocation property value is All).
-- Use `-AddExchangeLocation All` in the same command with this parameter.
-
-You can't use this parameter with the ExchangeSender or ExchangeSenderMemberOf parameters.
-
-You can't use this parameter to specify Microsoft 365 Groups.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: RecipientIdParameter[]
@@ -629,9 +573,7 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveOneDriveLocation
-The RemoveOneDriveLocation parameter specifies the OneDrive sites to remove from the list of included sites when you aren't using the value All for the OneDriveLocation parameter. You identify the site by its URL value.
-
-You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty
@@ -647,9 +589,7 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveOneDriveLocationException
-This parameter specifies the OneDrive sites to remove from the list of excluded sites when you use the value All for the OneDriveLocation parameter. You identify the site by its URL value.
-
-You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"Value1","Value2",..."ValueN"`.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty
@@ -701,9 +641,7 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveTeamsLocation
-The RemoveTeamsLocation parameter specifies the accounts, distribution groups, or mail-enabled security groups to remove from the list of included Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You specify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty
@@ -719,9 +657,7 @@ Accept wildcard characters: False
 ```
 
 ### -RemoveTeamsLocationException
-The RemoveTeamsLocationException parameter specifies the accounts, distribution groups, or mail-enabled security groups to remove from the list of excluded Teams chat and channel messages if you used the value All for the TeamsLocation parameter. You identify the entries by the email address or name of the account, distribution group, or mail-enabled security group.
-
-To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type:MultiValuedProperty

From b19cda7fad1c7a93951d9c771cab42f2e4194632 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Wed, 11 Jun 2025 08:37:04 -0700
Subject: [PATCH 08/21] Update Set-SensitiveInformationScan.md

---
 exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
index eb9a12589a..6ebb403c00 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
@@ -493,9 +493,7 @@ Accept wildcard characters: False
 ```
 
 ### -PolicyRBACScopes
-The PolicyRBACScopes parameter specifies the administrative units to assign to the scan. A valid value is the Microsoft Entra ObjectID (GUID value) of the administrative unit. You can specify multiple values separated by commas.
-
-Administrative units are available only in Microsoft Entra ID P1 or P2. You create and manage administrative units in Microsoft Graph PowerShell.
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
 Type: MultiValuedProperty

From 55786be5ce28f66fe341e8013d1c6dc97e1c887b Mon Sep 17 00:00:00 2001
From: Aakash Malhotra <53205984+aamalhot@users.noreply.github.com>
Date: Thu, 17 Jul 2025 13:13:56 +0530
Subject: [PATCH 09/21] Update New-SensitiveInformationScan.md

---
 .../exchange-ps/exchange/New-SensitiveInformationScan.md     | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
index f019f75294..28291ca7a2 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
@@ -53,10 +53,11 @@ 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.
 
 ## PARAMETERS
 

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 10/21] 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 719fb2dadda82087e836e7ca8e0c17d5a593fa99 Mon Sep 17 00:00:00 2001
From: Aakash Malhotra <53205984+aamalhot@users.noreply.github.com>
Date: Thu, 17 Jul 2025 13:20:40 +0530
Subject: [PATCH 11/21] Update Remove-SensitiveInformationScan.md

---
 .../exchange-ps/exchange/Remove-SensitiveInformationScan.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
index 03d11b7992..3f8185ab73 100644
--- a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Remove-SensitiveInformationScan cmdlet to remove sensitive information scans.
+Use the Remove-SensitiveInformationScan cmdlet to delete on-demand classification scans. Deleting a scan is not supported if estimation or classification is in progress.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 

From 4e13af31c1dec5b41e6ef19e33c13c4361e10c59 Mon Sep 17 00:00:00 2001
From: Aakash Malhotra <53205984+aamalhot@users.noreply.github.com>
Date: Thu, 17 Jul 2025 13:22:13 +0530
Subject: [PATCH 12/21] Update Remove-SensitiveInformationScanRule.md

---
 .../exchange-ps/exchange/Remove-SensitiveInformationScanRule.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
index b0021e4f90..9f121fb349 100644
--- a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Remove-SensitiveInformationScanRule cmdlet to remove sensitive information scan rules.
+Use the Remove-SensitiveInformationScanRule cmdlet to delete on-demand classification scan rules. Rules cannot be deleted when parent scan is in state ClassificationInProgress and ClassificationComplete. 
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 

From 69e8d1c77867fe1270ee275fb5ba59efbd84019f Mon Sep 17 00:00:00 2001
From: Aakash Malhotra <53205984+aamalhot@users.noreply.github.com>
Date: Thu, 17 Jul 2025 13:30:22 +0530
Subject: [PATCH 13/21] Update Set-SensitiveInformationScanRule.md

---
 .../exchange/Set-SensitiveInformationScanRule.md           | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
index e941622f3d..54e52fe030 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
@@ -43,10 +43,10 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 
 ### Example 1
 ```powershell
-{{ Add example code here }}
+Set-SensitiveInformationScanRule "SharePoint scan rule1" -ContentExtensionMatchesWords "pdf", "docx,csv" -StartImpactAssessment $true
 ```
 
-{{ Add example description here }}
+Above example updates the on-demand classification scan to classify pdf, docx and csv file types.
 
 ## PARAMETERS
 
@@ -287,5 +287,8 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## OUTPUTS
 
 ## NOTES
+- Modifying rule in ClassificationInProgress and ClassificationComplete states is not allowed
+- StartImpactAssessment $true must be passed to restart estimation. Otherwise, scan remains in ImpactAssessmentRequired state
+
 
 ## RELATED LINKS

From f2d9431fc2b52548624ad619eb71e3088f3f9311 Mon Sep 17 00:00:00 2001
From: Aakash Malhotra <53205984+aamalhot@users.noreply.github.com>
Date: Thu, 17 Jul 2025 13:36:38 +0530
Subject: [PATCH 14/21] Update Set-SensitiveInformationScan.md

---
 .../exchange/Set-SensitiveInformationScan.md     | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
index 6ebb403c00..3f2a7639c7 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Set-SensitiveInformationScan cmdlet to modify sensitive information scans.
+Use the Set-SensitiveInformationScan cmdlet to modify on-demand classification scans.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
@@ -66,10 +66,10 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 
 ### Example 1
 ```powershell
-{{ Add example code here }}
+Set-SensitiveInformationScan "SharePoint scan" -AddOneDriveLocation All -Workload OneDriveForBusiness
 ```
 
-{{ Add example description here }}
+Above example updates the on-demand classification scan to also include All OneDrive for business accounts.
 
 ## PARAMETERS
 
@@ -96,7 +96,7 @@ Accept wildcard characters: False
 ### -AddEndpointDlpLocation
 **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
 
-The AddEndpointDLPLocation parameter specifies the user accounts to add to the list of included accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address.
+The AddEndpointDLPLocation parameter specifies the user accounts to add to the list of included accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address. A scan cannot have Endpoint devices and SharePoint/OneDrive for business locations together.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
@@ -118,7 +118,7 @@ Accept wildcard characters: False
 ### -AddEndpointDlpLocationException
 **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
 
-The AddEndpointDlpLocationException parameter specifies the user accounts to add to the list of excluded accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address.
+The AddEndpointDlpLocationException parameter specifies the user accounts to add to the list of excluded accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address. A scan cannot have Endpoint devices and SharePoint/OneDrive for business locations together.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
@@ -425,7 +425,7 @@ Accept wildcard characters: False
 ```
 
 ### -Mode
-{{ Fill Mode Description }}
+Defines scan mode. Setting to Enable start the scan.
 
 ```yaml
 Type: PolicyMode
@@ -671,7 +671,7 @@ Accept wildcard characters: False
 ```
 
 ### -StartImpactAssessment
-{{ Fill StartImpactAssessment Description }}
+Start cost estimation for on-demand classification scan
 
 ```yaml
 Type: Boolean
@@ -687,7 +687,7 @@ Accept wildcard characters: False
 ```
 
 ### -StopImpactAssessmentAndStartClassification
-{{ Fill StopImpactAssessmentAndStartClassification Description }}
+Stop cost estimation and start classification for devices where estimation had completed successfully.
 
 ```yaml
 Type: Boolean

From fa589e6a92165ec2e4e62e8fa2fb3ab7d2db0658 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 17 Jul 2025 08:09:39 -0700
Subject: [PATCH 15/21] Update New-SensitiveInformationScan.md

---
 exchange/exchange-ps/exchange/New-SensitiveInformationScan.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
index 28291ca7a2..d2fbd755e1 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScan.md
@@ -54,10 +54,11 @@ 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 example creates a scan for all SharePoint sites scoped to pdf and docx files only.
 
 ## PARAMETERS
 

From 95e16c0f18dc6bb31db4b0f7404b57a5c98ab584 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 17 Jul 2025 09:19:20 -0700
Subject: [PATCH 16/21] Update Remove-SensitiveInformationScan.md

---
 .../exchange-ps/exchange/Remove-SensitiveInformationScan.md     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
index 3f8185ab73..95ad49ddb8 100644
--- a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Remove-SensitiveInformationScan cmdlet to delete on-demand classification scans. Deleting a scan is not supported if estimation or classification is in progress.
+Use the Remove-SensitiveInformationScan cmdlet to delete on-demand classification scans. You can't delete a scan if estimation or classification is in progress.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 

From c9e9bd60a7f669552096f15a8d817dab84cf8515 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 17 Jul 2025 09:20:50 -0700
Subject: [PATCH 17/21] Update Remove-SensitiveInformationScanRule.md

---
 .../exchange-ps/exchange/Remove-SensitiveInformationScanRule.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
index 9f121fb349..609e23c1c5 100644
--- a/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
@@ -14,7 +14,7 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
 
-Use the Remove-SensitiveInformationScanRule cmdlet to delete on-demand classification scan rules. Rules cannot be deleted when parent scan is in state ClassificationInProgress and ClassificationComplete. 
+Use the Remove-SensitiveInformationScanRule cmdlet to delete on-demand classification scan rules. You can't delete a rule when a parent scan is in the ClassificationInProgress or ClassificationComplete state. 
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 

From a8e47741c2114e518175b147e72a1c285f97f1b5 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 17 Jul 2025 09:25:19 -0700
Subject: [PATCH 18/21] Update Set-SensitiveInformationScanRule.md

---
 .../exchange/Set-SensitiveInformationScanRule.md         | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
index 54e52fe030..73a265c830 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
@@ -43,10 +43,10 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 
 ### Example 1
 ```powershell
-Set-SensitiveInformationScanRule "SharePoint scan rule1" -ContentExtensionMatchesWords "pdf", "docx,csv" -StartImpactAssessment $true
+Set-SensitiveInformationScanRule "SharePoint scan rule1" -ContentExtensionMatchesWords "pdf","docx,csv" -StartImpactAssessment $true
 ```
 
-Above example updates the on-demand classification scan to classify pdf, docx and csv file types.
+This example updates the on-demand classification scan to classify pdf, docx and csv file types.
 
 ## PARAMETERS
 
@@ -287,8 +287,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 ## OUTPUTS
 
 ## NOTES
-- Modifying rule in ClassificationInProgress and ClassificationComplete states is not allowed
-- StartImpactAssessment $true must be passed to restart estimation. Otherwise, scan remains in ImpactAssessmentRequired state
-
+- You can't modify rules in the ClassificationInProgress and ClassificationComplete states.
+- You need to use the StartImpactAssessment parameter with the value $true to restart estimation. Otherwise, the scan remains in the ImpactAssessmentRequired state.
 
 ## RELATED LINKS

From b01c4310f5ff721f295082a6c52e0ef2155f0047 Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Thu, 17 Jul 2025 09:51:20 -0700
Subject: [PATCH 19/21] Update Set-SensitiveInformationScan.md

---
 .../exchange/Set-SensitiveInformationScan.md  | 28 +++++++++++++++----
 1 file changed, 22 insertions(+), 6 deletions(-)

diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
index 3f2a7639c7..105954e2e9 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
@@ -69,7 +69,7 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
 Set-SensitiveInformationScan "SharePoint scan" -AddOneDriveLocation All -Workload OneDriveForBusiness
 ```
 
-Above example updates the on-demand classification scan to also include All OneDrive for business accounts.
+This example updates the on-demand classification scan to also include all OneDrive accounts.
 
 ## PARAMETERS
 
@@ -96,10 +96,12 @@ Accept wildcard characters: False
 ### -AddEndpointDlpLocation
 **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
 
-The AddEndpointDLPLocation parameter specifies the user accounts to add to the list of included accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address. A scan cannot have Endpoint devices and SharePoint/OneDrive for business locations together.
+The AddEndpointDLPLocation parameter specifies the user accounts to add to the list of included accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
+A scan can't have Endpoint devices and SharePoint/OneDrive locations together in the same command.
+
 For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
 
 ```yaml
@@ -118,10 +120,12 @@ Accept wildcard characters: False
 ### -AddEndpointDlpLocationException
 **Note**: This parameter requires membership in the Compliance Administrator or Compliance Data Administrator roles in Microsoft Entra ID.
 
-The AddEndpointDlpLocationException parameter specifies the user accounts to add to the list of excluded accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address. A scan cannot have Endpoint devices and SharePoint/OneDrive for business locations together.
+The AddEndpointDlpLocationException parameter specifies the user accounts to add to the list of excluded accounts for Endpoint DLP if you used the value All for the EndpointDLPLocation parameter. You identify the account by name or email address.
 
 To enter multiple values, use the following syntax: `<value1>,<value2>,...<valueX>`. If the values contain spaces or otherwise require quotation marks, use the following syntax: `"<value1>","<value2>",..."<valueX>"`.
 
+A scan can't have Endpoint devices and SharePoint/OneDrive locations together in the same command.
+
 For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
 
 ```yaml
@@ -425,7 +429,13 @@ Accept wildcard characters: False
 ```
 
 ### -Mode
-Defines scan mode. Setting to Enable start the scan.
+The Mode parameter specifies the scan mode. Valid values are:
+
+- Enable: Use this value to start the scan.
+- Disable
+- TestWithNotifications
+- TestWithoutNotifications
+- PendingDeletion
 
 ```yaml
 Type: PolicyMode
@@ -671,7 +681,10 @@ Accept wildcard characters: False
 ```
 
 ### -StartImpactAssessment
-Start cost estimation for on-demand classification scan
+The StartImpactAssessment parameter specifies whether to start cost estimation for on-demand classification scans. Valid values are:
+
+- $true: Start cost estimation for on-demand classification scans.
+- $false: Don't start cost estimation for on-demand classification scans.
 
 ```yaml
 Type: Boolean
@@ -687,7 +700,10 @@ Accept wildcard characters: False
 ```
 
 ### -StopImpactAssessmentAndStartClassification
-Stop cost estimation and start classification for devices where estimation had completed successfully.
+The StopImpactAssessmentAndStartClassification specifies whether to stop cost estimation and start classification for devices where estimation completed successfully. Valid values are:
+
+- $true: Start classification for devices where estimation completed successfully.
+- $false: Don't start classification for devices where estimation completed successfully.
 
 ```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 20/21] 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

From 43b3bf61b63aff616ae27669dfe8382d740af05f Mon Sep 17 00:00:00 2001
From: Chris Davis <chris.davis@microsoft.com>
Date: Fri, 18 Jul 2025 08:53:29 -0700
Subject: [PATCH 21/21] Date-time updates

---
 .../New-SensitiveInformationScanRule.md       | 14 ++++++++++++--
 .../Set-SensitiveInformationScanRule.md       | 19 ++++++++++++++++---
 2 files changed, 28 insertions(+), 5 deletions(-)

diff --git a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
index 948a0ad3a7..941aebf160 100644
--- a/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/New-SensitiveInformationScanRule.md
@@ -161,7 +161,12 @@ Accept wildcard characters: False
 ```
 
 ### -ContentCreatedOrUpdatedDateFrom
-The ContentCreatedOrUpdatedDateFrom prameter specifies the earliest modification date-time of files that are considered in scope of this scan.
+The ContentCreatedOrUpdatedDateFrom parameter specifies the earliest modification date-time of files that are considered in scope of this scan.
+
+To specify a date/time value for this parameter, use either of the following options:
+
+- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z".
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
 
 ```yaml
 Type: System.DateTime
@@ -177,7 +182,12 @@ Accept wildcard characters: False
 ```
 
 ### -ContentCreatedOrUpdatedDateTo
-The ContentCreatedOrUpdatedDateTo prameter specifies the latest modification date-time of files that are considered in scope of this scan.
+The ContentCreatedOrUpdatedDateTo parameter specifies the latest modification date-time of files that are considered in scope of this scan.
+
+To specify a date/time value for this parameter, use either of the following options:
+
+- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z".
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
 
 ```yaml
 Type: System.DateTime
diff --git a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
index 73a265c830..aad5a5c700 100644
--- a/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
+++ b/exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
@@ -106,7 +106,12 @@ Accept wildcard characters: False
 ```
 
 ### -ContentCreatedOrUpdatedDateFrom
-{{ Fill ContentCreatedOrUpdatedDateFrom Description }}
+The ContentCreatedOrUpdatedDateFrom parameter specifies the earliest modification date-time of files that are considered in scope of this scan.
+
+To specify a date/time value for this parameter, use either of the following options:
+
+- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z".
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
 
 ```yaml
 Type: System.DateTime
@@ -122,7 +127,12 @@ Accept wildcard characters: False
 ```
 
 ### -ContentCreatedOrUpdatedDateTo
-{{ Fill ContentCreatedOrUpdatedDateTo Description }}
+The ContentCreatedOrUpdatedDateTo parameter specifies the latest modification date-time of files that are considered in scope of this scan.
+
+To specify a date/time value for this parameter, use either of the following options:
+
+- Specify the date/time value in UTC: For example, "2021-05-06 14:30:00z".
+- Specify the date/time value as a formula that converts the date/time in your local time zone to UTC: For example, `(Get-Date "5/6/2021 9:30 AM").ToUniversalTime()`. For more information, see [Get-Date](https://learn.microsoft.com/powershell/module/Microsoft.PowerShell.Utility/Get-Date).
 
 ```yaml
 Type: System.DateTime
@@ -206,7 +216,10 @@ Accept wildcard characters: False
 ```
 
 ### -StartImpactAssessment
-{{ Fill StartImpactAssessment Description }}
+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
