Skip to content

Commit ba3d190

Browse files
authored
Update Update-VivaModuleFeaturePolicy.md
1 parent 91d0c78 commit ba3d190

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a f
2222
- 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.
2323
- 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.
2424
- You can only update user controls at the feature policy level, not the category policy level.
25-
- A policy can not be updated if the policy scope of the feature doesn't match with who has access to the policy being updated. To see allowed policy scopes for this feature, use [this commandlet](https://learn.microsoft.com/en-us/powershell/module/exchange/get-vivamodulefeature).
25+
- Some features only support policies that apply to the entire tenant, not specific users or groups. You can refer to supported policy scopes for a feature using the [Get-VivaModuleFeature](https://learn.microsoft.com/en-us/powershell/module/exchange/get-vivamodulefeature) cmdlet.
2626

2727
Some features include the option for user controls (user opt out). Refer to the feature documentation to see if user controls are available for the feature that you intend to set a policy for.
2828

@@ -247,8 +247,6 @@ The Everyone parameter specifies that the updated policy applies to all users in
247247
- $true: The policy applies to all users. This is the only useful value for this parameter.
248248
- $false: Don't use this value.
249249

250-
Only use this parameter if the feature has the Tenant policy scope.
251-
252250
If you don't want to update who the policy applies to, don't use this parameter.
253251

254252
Don't use this parameter with the GroupIds or UserIds parameters.
@@ -275,8 +273,6 @@ The values that you specify for this parameter or the UserIds parameter replace
275273

276274
You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.).
277275

278-
Only use this parameter if the feature has the Group policy scope.
279-
280276
To have the updated policy apply to all users in the organization, use the Everyone parameter with the value $true.
281277

282278
**Note**: In v3.5.1-Preview2 or later of the module, this parameter supports security group object IDs (GUIDs). Previous versions of the module accept only email addresses for this parameter.
@@ -410,8 +406,6 @@ The values that you specify for this parameter or the GroupIds parameter replace
410406

411407
You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.).
412408

413-
Only use this parameter if the feature has the User policy scope.
414-
415409
To have the updated policy apply to all users in the organization, use the Everyone parameter with the value $true.
416410

417411
```yaml

0 commit comments

Comments
 (0)