Skip to content

Commit f1e7456

Browse files
chrisdachrisda
committed
Create
1 parent fcab56f commit f1e7456

9 files changed

+2336
-0
lines changed

‎exchange/exchange-ps/exchange/Cancel-SensitiveInformationScan.md‎

Lines changed: 109 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,109 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://learn.microsoft.com/powershell/module/exchange/cancel-sensitiveinformationscan
4+
applicable: Security & Compliance
5+
title: Cancel-SensitiveInformationScan
6+
schema: 2.0.0
7+
author: chrisda
8+
ms.author: chrisda
9+
ms.reviewer:
10+
---
11+
12+
# Cancel-SensitiveInformationScan
13+
14+
## SYNOPSIS
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+
17+
Use the Cancel-SensitiveInformationScan cmdlet to cancel sensitive information scans.
18+
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+
21+
## SYNTAX
22+
23+
### Identity (Default)
24+
```
25+
Cancel-SensitiveInformationScan [-Identity] <PolicyIdParameter>
26+
[-Confirm]
27+
[-WhatIf]
28+
[<CommonParameters>]
29+
```
30+
31+
## DESCRIPTION
32+
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).
33+
34+
## EXAMPLES
35+
36+
### Example 1
37+
```powershell
38+
Cancel-SensitiveInformationScan -Identity "HR Department"
39+
```
40+
41+
This example cancels the specified sensitive information scan.
42+
43+
## PARAMETERS
44+
45+
### -Identity
46+
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:
47+
48+
- Name
49+
- Distinguished name (DN)
50+
- GUID
51+
52+
```yaml
53+
Type: PolicyIdParameter
54+
Parameter Sets: (All)
55+
Aliases:
56+
Applicable: Security & Compliance
57+
58+
Required: True
59+
Position: 0
60+
Default value: None
61+
Accept pipeline input: True (ByPropertyName, ByValue)
62+
Accept wildcard characters: False
63+
```
64+
65+
### -Confirm
66+
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.
67+
68+
- 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`.
69+
- 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.
70+
71+
```yaml
72+
Type: SwitchParameter
73+
Parameter Sets: (All)
74+
Aliases: cf
75+
Applicable: Security & Compliance
76+
77+
Required: False
78+
Position: Named
79+
Default value: None
80+
Accept pipeline input: False
81+
Accept wildcard characters: False
82+
```
83+
84+
### -WhatIf
85+
The WhatIf switch doesn't work in Security & Compliance PowerShell.
86+
87+
```yaml
88+
Type: SwitchParameter
89+
Parameter Sets: (All)
90+
Aliases: wi
91+
Applicable: Security & Compliance
92+
93+
Required: False
94+
Position: Named
95+
Default value: None
96+
Accept pipeline input: False
97+
Accept wildcard characters: False
98+
```
99+
100+
### CommonParameters
101+
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).
102+
103+
## INPUTS
104+
105+
## OUTPUTS
106+
107+
## NOTES
108+
109+
## RELATED LINKS

‎exchange/exchange-ps/exchange/Get-SensitiveInformationScan.md‎

Lines changed: 138 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,138 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://learn.microsoft.com/powershell/module/exchange/get-sensitiveinformationscan
4+
applicable: Security & Compliance
5+
title: Get-SensitiveInformationScan
6+
schema: 2.0.0
7+
author: chrisda
8+
ms.author: chrisda
9+
ms.reviewer:
10+
---
11+
12+
# Get-SensitiveInformationScan
13+
14+
## SYNOPSIS
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+
17+
Use the Get-SensitiveInformationScan cmdlet to view sensitive information scans.
18+
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+
21+
## SYNTAX
22+
23+
```
24+
Get-SensitiveInformationScan [[-Identity] <PolicyIdParameter>]
25+
[-IncludeImpactAssessment <Boolean>]
26+
[-IncludeProgressForAllActiveScans <Boolean>]
27+
[-IncludeScanProgress <Boolean>]
28+
[<CommonParameters>]
29+
```
30+
31+
## DESCRIPTION
32+
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).
33+
34+
## EXAMPLES
35+
36+
### Example 1
37+
```powershell
38+
Get-SensitiveInformationScan | Format-Table Name,ParentPolicyName
39+
```
40+
41+
This example returns a summary list of all sensitive information scans in the organization.
42+
43+
### Example 2
44+
```powershell
45+
Get-SensitiveInformationScan -Identity "HR Department Scan"
46+
```
47+
48+
This example returns detailed information for the specified scan.
49+
50+
## PARAMETERS
51+
52+
### -Identity
53+
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:
54+
55+
- Name
56+
- Distinguished name (DN)
57+
- GUID
58+
59+
```yaml
60+
Type: PolicyIdParameter
61+
Parameter Sets: (All)
62+
Aliases:
63+
Applicable: Security & Compliance
64+
65+
Required: False
66+
Position: 0
67+
Default value: None
68+
Accept pipeline input: True (ByPropertyName, ByValue)
69+
Accept wildcard characters: False
70+
```
71+
72+
### -IncludeImpactAssessment
73+
The IncludeImpactAssessment parameter specifies whether to ???. Valid values are:
74+
75+
- $true: ???
76+
- $false: ???
77+
78+
```yaml
79+
Type: Boolean
80+
Parameter Sets: (All)
81+
Aliases:
82+
Applicable: Security & Compliance
83+
84+
Required: False
85+
Position: Named
86+
Default value: None
87+
Accept pipeline input: False
88+
Accept wildcard characters: False
89+
```
90+
91+
### -IncludeProgressForAllActiveScans
92+
The IncludeProgressForAllActiveScans parameter specifies whether to ???. Valid values are:
93+
94+
- $true: ???
95+
- $false: ???
96+
97+
```yaml
98+
Type: Boolean
99+
Parameter Sets: (All)
100+
Aliases:
101+
Applicable: Security & Compliance
102+
103+
Required: False
104+
Position: Named
105+
Default value: None
106+
Accept pipeline input: False
107+
Accept wildcard characters: False
108+
```
109+
110+
### -IncludeScanProgress
111+
The IncludeScanProgress parameter specifies whether to ???. Valid values are:
112+
113+
- $true: ???
114+
- $false: ???
115+
116+
```yaml
117+
Type: Boolean
118+
Parameter Sets: (All)
119+
Aliases:
120+
Applicable: Security & Compliance
121+
122+
Required: False
123+
Position: Named
124+
Default value: None
125+
Accept pipeline input: False
126+
Accept wildcard characters: False
127+
```
128+
129+
### CommonParameters
130+
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).
131+
132+
## INPUTS
133+
134+
## OUTPUTS
135+
136+
## NOTES
137+
138+
## RELATED LINKS

‎exchange/exchange-ps/exchange/Get-SensitiveInformationScanRule.md‎

Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://learn.microsoft.com/powershell/module/exchange/get-sensitiveinformationscanrule
4+
applicable: Security & Compliance
5+
title: Get-SensitiveInformationScanRule
6+
schema: 2.0.0
7+
author: chrisda
8+
ms.author: chrisda
9+
ms.reviewer:
10+
---
11+
12+
# Get-SensitiveInformationScanRule
13+
14+
## SYNOPSIS
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+
17+
Use the Get-SensitiveInformationScanRule cmdlet to
18+
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+
21+
## SYNTAX
22+
23+
```
24+
Get-SensitiveInformationScanRule [[-Identity] <ComplianceRuleIdParameter>] [-Policy <PolicyIdParameter>] [<CommonParameters>]
25+
```
26+
27+
## DESCRIPTION
28+
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).
29+
30+
## EXAMPLES
31+
32+
### Example 1
33+
```powershell
34+
{{ Add example code here }}
35+
```
36+
37+
{{ Add example description here }}
38+
39+
## PARAMETERS
40+
41+
### -Identity
42+
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:
43+
44+
- Name
45+
- Distinguished name (DN)
46+
- GUID
47+
48+
```yaml
49+
Type: ComplianceRuleIdParameter
50+
Parameter Sets: (All)
51+
Aliases:
52+
Applicable: Security & Compliance
53+
54+
Required: False
55+
Position: 0
56+
Default value: None
57+
Accept pipeline input: True (ByPropertyName, ByValue)
58+
Accept wildcard characters: False
59+
```
60+
61+
### -Policy
62+
{{ Fill Policy Description }}
63+
64+
```yaml
65+
Type: PolicyIdParameter
66+
Parameter Sets: (All)
67+
Aliases:
68+
Applicable: Security & Compliance
69+
70+
Required: False
71+
Position: Named
72+
Default value: None
73+
Accept pipeline input: False
74+
Accept wildcard characters: False
75+
```
76+
77+
### CommonParameters
78+
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).
79+
80+
## INPUTS
81+
82+
## OUTPUTS
83+
84+
## NOTES
85+
86+
## RELATED LINKS

0 commit comments

Comments
 (0)