Skip to content

Update Add-VivaModuleFeaturePolicy.md #12665

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Apr 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions exchange/exchange-ps/exchange/Add-VivaModuleFeaturePolicy.md
Original file line number Diff line number Diff line change
Expand Up @@ -252,12 +252,14 @@ Accept wildcard characters: False
### -IsUserOptedInByDefault
This parameter is available in version 3.8.0-Preview2 or later of the module.

The IsUserOptedInByDefault parameter specifies whether user opted in by default by the policy. Valid values are:
The IsUserOptedInByDefault parameter specifies whether users are opted in by default by the policy. Valid values are:

- $true: User opted in by the policy.
- $false: User opted out by the policy.
- $true: By default, users are opted in by the policy if the user hasn't set a preference.
- $false: By default, users are opted out by the policy if the user hasn't set a preference.

Only features that allow admins to enable and disable user controls by policy can use this parameter. If the feature doesn't support admins toggling user controls, the default value applies. See the feature documentation for more information.
This parameter is optional and can be used to override the default user opt-in value set in the feature metadata.

This parameter can be set only when the IsUserControlEnabled parameter is set to $true.

```yaml
Type: Boolean
Expand Down