You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Remove-SensitiveInformationScan.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
16
16
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.
18
18
19
19
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Remove-SensitiveInformationScanRule.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
16
16
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.
18
18
19
19
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
Copy file name to clipboardExpand all lines: exchange/exchange-ps/exchange/Set-SensitiveInformationScan.md
+22-6Lines changed: 22 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.reviewer:
14
14
## SYNOPSIS
15
15
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
16
16
17
-
Use the Set-SensitiveInformationScan cmdlet to modify sensitive information scans.
17
+
Use the Set-SensitiveInformationScan cmdlet to modify on-demand classification scans.
18
18
19
19
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
20
20
@@ -66,10 +66,10 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
66
66
67
67
### Example 1
68
68
```powershell
69
-
{{ Add example code here }}
69
+
Set-SensitiveInformationScan "SharePoint scan" -AddOneDriveLocation All -Workload OneDriveForBusiness
70
70
```
71
71
72
-
{{ Add example description here }}
72
+
This example updates the on-demand classification scan to also include all OneDrive accounts.
73
73
74
74
## PARAMETERS
75
75
@@ -100,6 +100,8 @@ The AddEndpointDLPLocation parameter specifies the user accounts to add to the l
100
100
101
101
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>"`.
102
102
103
+
A scan can't have Endpoint devices and SharePoint/OneDrive locations together in the same command.
104
+
103
105
For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
104
106
105
107
```yaml
@@ -122,6 +124,8 @@ The AddEndpointDlpLocationException parameter specifies the user accounts to add
122
124
123
125
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>"`.
124
126
127
+
A scan can't have Endpoint devices and SharePoint/OneDrive locations together in the same command.
128
+
125
129
For more information about Endpoint DLP, see [Learn about Endpoint data loss prevention](https://learn.microsoft.com/purview/endpoint-dlp-learn-about).
{{ 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.
This example updates the on-demand classification scan to classify pdf, docx and csv file types.
50
50
51
51
## PARAMETERS
52
52
@@ -287,5 +287,7 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
287
287
## OUTPUTS
288
288
289
289
## 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.
0 commit comments