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/Update-VivaModuleFeaturePolicy.md
+13-12Lines changed: 13 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,9 +15,9 @@ ms.reviewer:
15
15
## SYNOPSIS
16
16
This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module).
17
17
18
-
**Note**: While we are adding support for category policies in the Exchange Online PowerShell module v3.5.0-Preview1 or later, we have not yet released any categories in Viva. We will update when there are categories available.
18
+
**Note**: Support for categories is available in version 3.5.0-Preview1 or later of the module, but no categories are currently available in Viva. We'll update the documentation when categories are available.
19
19
20
-
Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a feature in a Viva module or a category in Viva. Note that:
20
+
Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a feature in a Viva module or a category in Viva.
21
21
22
22
- You can't update a policy for a particular user or group to include the entire tenant if a policy for the entire tenant already exists for the feature. Only one tenant-wide policy is supported.
23
23
- Policies assigned to a specific user or group take priority over the policy assigned to the entire tenant when determining whether a feature/category is enabled. If a user has multiple policies assigned for a feature/category (directly as a user or member of a group), the most restrictive policy applies.
@@ -31,7 +31,7 @@ For information about the parameter sets in the Syntax section below, see [Excha
**Note**: While we are adding support for category policies in the Exchange Online PowerShell module v3.5.0-Preview1 or later, we have not yet released any categories in Viva. We will update when there are categories available.
Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a feature in a Viva module or a category in Viva.
65
63
66
-
**Note**: While we are adding support for category policies in the Exchange Online PowerShell module v3.5.0-Preview1 or later, we have not yet released any categories in Viva. We will update when there are categories available.
64
+
Support for categories is available in version 3.5.0-Preview1 or later of the module.
67
65
68
66
This cmdlet updates the attributes of the policy that you specify. These attributes include:
69
67
@@ -80,8 +78,8 @@ You need to use the Connect-ExchangeOnline cmdlet to authenticate.
80
78
81
79
This cmdlet requires the .NET Framework 4.7.2 or later.
82
80
83
-
Currently, you need to be a member of the Global administrators role or the roles that have been permissioned at the feature level to run this cmdlet.
84
-
To learn more about permissioned roles at the feature level, see [Features Available for Feature Access Management](https://learn.microsoft.com/en-us/viva/feature-access-management#features-available-for-feature-access-management).
81
+
Currently, you need to be a member of the Global administrators role or the roles that have been assigned at the feature level to run this cmdlet.
82
+
To learn more about assigned roles at the feature level, see [Features Available for Feature Access Management](https://learn.microsoft.com/viva/feature-access-management#features-available-for-feature-access-management).
85
83
86
84
To learn more about administrator role permissions in Microsoft Entra ID, see [Role template IDs](https://learn.microsoft.com/entra/identity/role-based-access-control/permissions-reference#role-template-ids).
This example updates the name of the specified policy, makes it so the policy enables the category (effectively all features under the category), and updates who the policy applies to. The policy now applies **only** to the specified users and groups, overwriting the users and groups the policy used to apply to.
145
143
146
-
147
144
## PARAMETERS
148
145
149
146
### -CategoryId
150
-
**Note**: While we are adding support for category policies in the Exchange Online PowerShell module v3.5.0-Preview1 or later, we have not yet released any categories in Viva. We will update when there are categories available.
147
+
This parameter is available in version 3.5.0-Preview1 or later of the module.
148
+
149
+
**Note**: Currently, no categories are available in Viva. We'll update the documentation when categories are available.
151
150
152
151
The CategoryId parameter specifies the category of the policy that you want to update.
**Note**: While we are adding support for category policies in the Exchange Online PowerShell module v3.5.0-Preview1 or later, we have not yet released any categories in Viva. We will update when there are categories available.
287
+
This parameter is available in version 3.5.0-Preview1 or later of the module.
288
+
289
+
**Note**: Currently, no categories are available in Viva. We'll update the documentation when categories are available.
289
290
290
291
The IsCategoryEnabled parameter specifies whether the category is enabled by the updated policy. Valid values are:
0 commit comments