updates documentation for Add-VivaModuleFeaturePolicy and Update-VivaModuleFeaturePolicy

Author: v-jimchang

exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md

@@ -23,6 +23,7 @@ Use the Add-VivaModuleFeaturePolicy cmdlet to add a new access policy for a spec
 - 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.
 - If a category is disabled by category policies, all features under the category are disabled regardless of the policies set at the feature level.
 - You can only update user controls at the feature policy level, not the category policy level.
+- A policy can not be added if the policy scope of the feature doesn't match with who has access to the policy being added. To see allowed policy scopes for this feature, use [this commandlet](https://learn.microsoft.com/en-us/powershell/module/exchange/get-vivamodulefeature).
 
 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.
 
@@ -278,6 +279,8 @@ Accept wildcard characters: False
 ### -Everyone
 The Everyone switch specifies that the policy applies to all users in the organization. You don't need to specify a value with this switch.
 
+Only use this parameter if the feature has the Tenant policy scope.
+
 Don't use this switch with the GroupIds or UserIds parameters.
 
 ```yaml
@@ -298,6 +301,8 @@ The GroupIds parameter specifies the email addresses or security group object ID
 
 You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.).
 
+Only use this parameter if the feature has the Group policy scope.
+
 To have the policy apply to all users in the organization, use the Everyone switch.
 
 **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.
@@ -359,6 +364,8 @@ The UserIds parameter specifies the user principal names (UPNs) of the users tha
 
 You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.).
 
+Only use this parameter if the feature has the User policy scope.
+
 To have the policy apply to all users in the organization, use the Everyone switch.
 
 ```yaml

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

@@ -22,6 +22,7 @@ Use the Update-VivaModuleFeaturePolicy cmdlet to update an access policy for a f
 - 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.
 - 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.
 - You can only update user controls at the feature policy level, not the category policy level.
+- 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).
 
 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.
 
@@ -246,6 +247,8 @@ The Everyone parameter specifies that the updated policy applies to all users in
 - $true: The policy applies to all users. This is the only useful value for this parameter.
 - $false: Don't use this value.
 
+Only use this parameter if the feature has the Tenant policy scope.
+
 If you don't want to update who the policy applies to, don't use this parameter.
 
 Don't use this parameter with the GroupIds or UserIds parameters.
@@ -272,6 +275,8 @@ The values that you specify for this parameter or the UserIds parameter replace
 
 You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.).
 
+Only use this parameter if the feature has the Group policy scope.
+
 To have the updated policy apply to all users in the organization, use the Everyone parameter with the value $true.
 
 **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.
@@ -405,6 +410,8 @@ The values that you specify for this parameter or the GroupIds parameter replace
 
 You can specify a maximum of 20 total users or groups (20 users and no groups, 10 users and 10 groups, etc.).
 
+Only use this parameter if the feature has the User policy scope.
+
 To have the updated policy apply to all users in the organization, use the Everyone parameter with the value $true.
 
 ```yaml