Skip to content

Update Set-SensitiveInformationScanRule.md #12894

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 17, 2025
Merged

Update Set-SensitiveInformationScanRule.md #12894

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
69e8d1c
Update Set-SensitiveInformationScanRule.md
aamalhot Jul 17, 2025
a8e4774
Update Set-SensitiveInformationScanRule.md
chrisda Jul 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 }}
This example updates the on-demand classification scan to classify pdf, docx and csv file types.

## PARAMETERS

Expand Down Expand Up @@ -287,5 +287,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
## OUTPUTS

## NOTES
- 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