Skip to content

Commit efb97bb

Browse files
authored
Merge pull request #12624 from brenle/patch-7
Update Remove-FeatureConfiguration.md
2 parents 993c683 + 65b1d37 commit efb97bb

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

exchange/exchange-ps/exchange/Remove-FeatureConfiguration.md

+6-4
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,13 @@ schema: 2.0.0
99
# Remove-FeatureConfiguration
1010

1111
## SYNOPSIS
12-
**Note**: Currently, this cmdlet is available only in Private Preview.
12+
**Note**: This cmdlet is available in Public Preview.
1313

1414
This cmdlet is available only in Security & Compliance PowerShell. For more information, see [Security & Compliance PowerShell](https://learn.microsoft.com/powershell/exchange/scc-powershell).
1515

16-
Use the Remove-FeatureConfiguration cmdlet to remove Discovery policies.
16+
Use the Remove-FeatureConfiguration cmdlet to remove Microsoft Purview feature configurations within your organization, including:
17+
- Collection policies
18+
- Endpoint DLP trust container
1719

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

@@ -38,12 +40,12 @@ To use this cmdlet in Security & Compliance PowerShell, you need to be assigned
3840
Remove-FeatureConfiguration -Identity "Engineering Group"
3941
```
4042

41-
This example removes the specified Discovery policy.
43+
This example removes the specified feature configuration.
4244

4345
## PARAMETERS
4446

4547
### -Identity
46-
The Identity policy specifies the Discovery policy that you want to remove. You can use any value that uniquely identifies the policy. For example:
48+
The Identity policy specifies the feature configuration that you want to remove. You can use any value that uniquely identifies the configuration. For example:
4749

4850
- Name
4951
- Distinguished name (DN)

0 commit comments

Comments
 (0)