From 6028208d451cd30c4503e224cd408499e692bb76 Mon Sep 17 00:00:00 2001 From: v-jimchang Date: Wed, 14 Aug 2024 17:23:50 +0000 Subject: [PATCH 1/5] updates documentation for Add-VivaModuleFeaturePolicy and Update-VivaModuleFeaturePolicy --- .../exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md | 7 +++++++ .../exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md index 1cf7b09df1..c9bef566a1 100644 --- a/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md +++ b/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 diff --git a/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md index 637a4aa265..9e446238f5 100644 --- a/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md +++ b/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 From 91d0c781e2d57f56bd51a523550442bd390cda17 Mon Sep 17 00:00:00 2001 From: v-jimchang Date: Wed, 14 Aug 2024 10:44:19 -0700 Subject: [PATCH 2/5] Update Add-VivaModuleFeaturePolicy.md --- .../exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md index c9bef566a1..2a4aba6506 100644 --- a/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md @@ -23,7 +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 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. 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. @@ -279,8 +279,6 @@ 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 @@ -301,8 +299,6 @@ 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. @@ -364,8 +360,6 @@ 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 From ba3d1903335acbe244bb145b4d9a9ecfe52da55a Mon Sep 17 00:00:00 2001 From: v-jimchang Date: Wed, 14 Aug 2024 10:45:02 -0700 Subject: [PATCH 3/5] Update Update-VivaModuleFeaturePolicy.md --- .../exchange/Update-VivaModuleFeaturePolicy.md | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md index 9e446238f5..8a1e56d940 100644 --- a/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md @@ -22,7 +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 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. 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. @@ -247,8 +247,6 @@ 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. @@ -275,8 +273,6 @@ 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. @@ -410,8 +406,6 @@ 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 From a63b95f4ff957c334968f9cf7f0a0e79b86b241e Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Wed, 14 Aug 2024 11:00:00 -0700 Subject: [PATCH 4/5] Update Add-VivaModuleFeaturePolicy.md --- exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md index 2a4aba6506..08eb8d0914 100644 --- a/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md @@ -23,7 +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. -- 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. +- 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/powershell/module/exchange/get-vivamodulefeature) cmdlet. 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. From 773f18f6f0213376347f9e6f340032d5a5b750ea Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Wed, 14 Aug 2024 11:00:50 -0700 Subject: [PATCH 5/5] Update Update-VivaModuleFeaturePolicy.md --- exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md b/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md index 8a1e56d940..9d677d3db1 100644 --- a/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md +++ b/exchange/exchange-ps/exchange/Update-VivaModuleFeaturePolicy.md @@ -22,7 +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. -- 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. +- 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/powershell/module/exchange/get-vivamodulefeature) cmdlet. 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.