Skip to content

Commit a0c599d

Browse files
authored
Merge branch 'SIS-chrisda' into patch-18
2 parents c8c279b + 6e0a8d6 commit a0c599d

File tree

5 files changed

+32
-12
lines changed

5 files changed

+32
-12
lines changed

exchange/exchange-ps/exchange/New-SensitiveInformationScan.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,12 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
5353

5454
### Example 1
5555
```powershell
56-
{{ Add example code here }}
56+
New-SensitiveInformationScan "SharePoint scan" -SharePointLocation All
57+
58+
New-SensitiveInformationScanRule "SharePoint scan rule" -ContentExtensionMatchesWords "pdf", "docx" -Policy "SharePoint scan" -Workload SharePoint
5759
```
5860

59-
{{ Add example description here }}
61+
This example creates a scan for all SharePoint sites scoped to pdf and docx files only.
6062

6163
## PARAMETERS
6264

exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.reviewer:
1414
## SYNOPSIS
1515
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
1616

17-
Use the Remove-SensitiveInformationScan cmdlet to remove sensitive information scans.
17+
Use the Remove-SensitiveInformationScan cmdlet to delete on-demand classification scans. You can't delete a scan if estimation or classification is in progress.
1818

1919
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
2020

exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.reviewer:
1414
## SYNOPSIS
1515
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
1616

17-
Use the Remove-SensitiveInformationScanRule cmdlet to remove sensitive information scan rules.
17+
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.
1818

1919
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
2020

exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md

Lines changed: 22 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.reviewer:
1414
## SYNOPSIS
1515
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
1616

17-
Use the Set-SensitiveInformationScan cmdlet to modify sensitive information scans.
17+
Use the Set-SensitiveInformationScan cmdlet to modify on-demand classification scans.
1818

1919
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
2020

@@ -66,10 +66,10 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
6666

6767
### Example 1
6868
```powershell
69-
{{ Add example code here }}
69+
Set-SensitiveInformationScan "SharePoint scan" -AddOneDriveLocation All -Workload OneDriveForBusiness
7070
```
7171

72-
{{ Add example description here }}
72+
This example updates the on-demand classification scan to also include all OneDrive accounts.
7373

7474
## PARAMETERS
7575

@@ -100,6 +100,8 @@ The AddEndpointDLPLocation parameter specifies the user accounts to add to the l
100100
101101
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>"`.
102102

103+
A scan can't have Endpoint devices and SharePoint/OneDrive locations together in the same command.
104+
103105
For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
104106

105107
```yaml
@@ -122,6 +124,8 @@ The AddEndpointDlpLocationException parameter specifies the user accounts to add
122124

123125
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>"`.
124126

127+
A scan can't have Endpoint devices and SharePoint/OneDrive locations together in the same command.
128+
125129
For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
126130

127131
```yaml
@@ -425,7 +429,13 @@ Accept wildcard characters: False
425429
```
426430

427431
### -Mode
428-
{{ Fill Mode Description }}
432+
The Mode parameter specifies the scan mode. Valid values are:
433+
434+
- Enable: Use this value to start the scan.
435+
- Disable
436+
- TestWithNotifications
437+
- TestWithoutNotifications
438+
- PendingDeletion
429439

430440
```yaml
431441
Type: PolicyMode
@@ -671,7 +681,10 @@ Accept wildcard characters: False
671681
```
672682

673683
### -StartImpactAssessment
674-
{{ Fill StartImpactAssessment Description }}
684+
The StartImpactAssessment parameter specifies whether to start cost estimation for on-demand classification scans. Valid values are:
685+
686+
- $true: Start cost estimation for on-demand classification scans.
687+
- $false: Don't start cost estimation for on-demand classification scans.
675688

676689
```yaml
677690
Type: Boolean
@@ -687,7 +700,10 @@ Accept wildcard characters: False
687700
```
688701

689702
### -StopImpactAssessmentAndStartClassification
690-
{{ Fill StopImpactAssessmentAndStartClassification Description }}
703+
The StopImpactAssessmentAndStartClassification specifies whether to stop cost estimation and start classification for devices where estimation completed successfully. Valid values are:
704+
705+
- $true: Start classification for devices where estimation completed successfully.
706+
- $false: Don't start classification for devices where estimation completed successfully.
691707

692708
```yaml
693709
Type: Boolean

exchange/exchange-ps/exchange/Set-SensitiveInformationScanRule.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,10 +43,10 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
4343

4444
### Example 1
4545
```powershell
46-
{{ Add example code here }}
46+
Set-SensitiveInformationScanRule "SharePoint scan rule1" -ContentExtensionMatchesWords "pdf","docx,csv" -StartImpactAssessment $true
4747
```
4848

49-
{{ Add example description here }}
49+
This example updates the on-demand classification scan to classify pdf, docx and csv file types.
5050

5151
## PARAMETERS
5252

@@ -287,5 +287,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
287287
## OUTPUTS
288288

289289
## NOTES
290+
- You can't modify rules in the ClassificationInProgress and ClassificationComplete states.
291+
- You need to use the StartImpactAssessment parameter with the value $true to restart estimation. Otherwise, the scan remains in the ImpactAssessmentRequired state.
290292

291293
## RELATED LINKS

0 commit comments

Comments
 (0)