Skip to content

Commit 76371f9

Browse files
chrisdachrisda
committed
FeatureConfig
1 parent 325e11c commit 76371f9

File tree

6 files changed

+674
-0
lines changed

6 files changed

+674
-0
lines changed

‎exchange/exchange-ps/exchange/Get-FeatureConfiguration.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/get-featureconfiguration
4+
applicable: Security & Compliance
5+
title: Get-FeatureConfiguration
6+
schema: 2.0.0
7+
---
8+
9+
# Get-FeatureConfiguration
10+
11+
## SYNOPSIS
12+
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
13+
14+
Use the Get-FeatureConfiguration cmdlet to view Discovery policies.
15+
16+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
17+
18+
## SYNTAX
19+
20+
```
21+
Get-FeatureConfiguration [[-Identity] <Microsoft.Office.CompliancePolicy.Tasks.PolicyIdParameter>]
22+
[-Confirm]
23+
[-WhatIf]
24+
[<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 Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920).
29+
30+
## EXAMPLES
31+
32+
### Example 1
33+
```powershell
34+
Get-FeatureConfiguration | Format-Table Name,Mode
35+
```
36+
37+
This example returns a summary list of all Discovery policies in the organization.
38+
39+
### Example 2
40+
```powershell
41+
Get-FeatureConfiguration -Identity "Engineering Group"
42+
```
43+
44+
This example returns detailed information about the specified Discovery policy.
45+
46+
## PARAMETERS
47+
48+
### -Identity
49+
The Identity policy specifies the Discovery policy that you want to view. You can use any value that uniquely identifies the policy. For example:
50+
51+
- Name
52+
- Distinguished name (DN)
53+
- GUID
54+
55+
```yaml
56+
Type: Microsoft.Office.CompliancePolicy.Tasks.PolicyIdParameter
57+
Parameter Sets: (All)
58+
Aliases:
59+
Applicable: Security & Compliance
60+
61+
Required: False
62+
Position: 1
63+
Default value: None
64+
Accept pipeline input: True (ByPropertyName, ByValue)
65+
Accept wildcard characters: False
66+
```
67+
68+
### -Confirm
69+
This parameter is reserved for internal Microsoft use.
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+
This parameter is reserved for internal Microsoft use.
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/New-FeatureConfiguration.md‎

Lines changed: 188 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,188 @@
1+
---
2+
external help file: Microsoft.Exchange.TransportMailflow-Help.xml
3+
online version: https://learn.microsoft.com/powershell/module/exchange/new-featureconfiguration
4+
applicable: Security & Compliance
5+
title: New-FeatureConfiguration
6+
schema: 2.0.0
7+
---
8+
9+
# New-FeatureConfiguration
10+
11+
## SYNOPSIS
12+
13+
## SYNTAX
14+
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
15+
16+
Use the New-FeatureConfiguration cmdlet to create Discovery policies.
17+
18+
For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
19+
20+
```
21+
New-FeatureConfiguration [-Name] <String> -Mode <Microsoft.Office.CompliancePolicy.Tasks.PolicyMode> -Scenario <Microsoft.Office.CompliancePolicy.Tasks.FeatureConfigurationScenario> -ScenarioConfig <String>
22+
[-Comment <String>]
23+
[-Confirm]
24+
[-Locations <String>]
25+
[-WhatIf]
26+
[<CommonParameters>]
27+
```
28+
29+
## DESCRIPTION
30+
To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in Security & Compliance](https://go.microsoft.com/fwlink/p/?LinkId=511920).
31+
32+
## EXAMPLES
33+
34+
### Example 1
35+
```powershell
36+
{{ Add example code here }}
37+
```
38+
39+
{{ Add example description here }}
40+
41+
## PARAMETERS
42+
43+
### -Name
44+
The Name parameter specifies the unique name for the Discovery policy. The maximum length is 64 characters. If the value contains spaces, enclose the value in quotation marks (").
45+
46+
```yaml
47+
Type: String
48+
Parameter Sets: (All)
49+
Aliases:
50+
Applicable: Security & Compliance
51+
52+
Required: True
53+
Position: 1
54+
Default value: None
55+
Accept pipeline input: False
56+
Accept wildcard characters: False
57+
```
58+
59+
### -Comment
60+
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".
61+
62+
```yaml
63+
Type: String
64+
Parameter Sets: (All)
65+
Aliases:
66+
Applicable: Security & Compliance
67+
68+
Required: False
69+
Position: Named
70+
Default value: None
71+
Accept pipeline input: False
72+
Accept wildcard characters: False
73+
```
74+
75+
### -Confirm
76+
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.
77+
78+
- 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`.
79+
- 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.
80+
81+
```yaml
82+
Type: SwitchParameter
83+
Parameter Sets: (All)
84+
Aliases: cf
85+
Applicable: Security & Compliance
86+
87+
Required: False
88+
Position: Named
89+
Default value: None
90+
Accept pipeline input: False
91+
Accept wildcard characters: False
92+
```
93+
94+
### -Locations
95+
{{ Fill Locations Description }}
96+
97+
```yaml
98+
Type: String
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+
### -Mode
111+
The Mode parameter specifies the action and notification level of the Discovery policy. Valid values are:
112+
113+
- Enable: The policy is enabled for actions and notifications. This is the default value.
114+
- Disable: The policy is disabled.
115+
- TestWithNotifications: Simulation mode where no actions are taken, but notifications **are** sent.
116+
- TestWithoutNotifications: Simulation mode where no actions are taken, and no notifications are sent.
117+
118+
```yaml
119+
Type: Microsoft.Office.CompliancePolicy.Tasks.PolicyMode
120+
Parameter Sets: (All)
121+
Aliases:
122+
Applicable: Security & Compliance
123+
124+
Required: True
125+
Position: Named
126+
Default value: None
127+
Accept pipeline input: False
128+
Accept wildcard characters: False
129+
```
130+
131+
### -Scenario
132+
The Scenario parameter specifies the scenario for the Discovery policy. Currently, the only valid value is KnowYourData.
133+
134+
```yaml
135+
Type: icrosoft.Office.CompliancePolicy.Tasks.FeatureConfigurationScenario
136+
Parameter Sets: (All)
137+
Aliases:
138+
Applicable: Security & Compliance
139+
140+
Required: True
141+
Position: Named
142+
Default value: None
143+
Accept pipeline input: False
144+
Accept wildcard characters: False
145+
```
146+
147+
### -ScenarioConfig
148+
{{ Fill ScenarioConfig Description }}
149+
150+
```yaml
151+
Type: String
152+
Parameter Sets: (All)
153+
Aliases:
154+
Applicable: Security & Compliance
155+
156+
Required: True
157+
Position: Named
158+
Default value: None
159+
Accept pipeline input: False
160+
Accept wildcard characters: False
161+
```
162+
163+
### -WhatIf
164+
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch.
165+
166+
```yaml
167+
Type: SwitchParameter
168+
Parameter Sets: (All)
169+
Aliases: wi
170+
Applicable: Security & Compliance
171+
172+
Required: False
173+
Position: Named
174+
Default value: None
175+
Accept pipeline input: False
176+
Accept wildcard characters: False
177+
```
178+
179+
### CommonParameters
180+
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).
181+
182+
## INPUTS
183+
184+
## OUTPUTS
185+
186+
## NOTES
187+
188+
## RELATED LINKS

0 commit comments

Comments
 (0)