Skip to content
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

TeamsCallingPolicy: Export causes error with validateset for BusyOnBusyEnabledType Param #2271

Closed
andikrueger opened this issue Sep 12, 2022 · 1 comment · Fixed by #2284 or #2285
Closed
Labels
Bug Something isn't working Teams

Comments

@andikrueger
Copy link
Collaborator

Details of the scenario you tried and the problem that is occurring

Running an export of TeamsCallingPolicies causes an issue with the configuration. The BusyOnBusyEnabledType param gets a value that is not part of the params validateset.

Verbose logs showing the problem

image

Suggested solution to the issue

Fix the validateset to support this addtional value or add a output transformation to include proper values for this resource and the powershell cmdlets used.

This is part of the docs for the Set-CSTeamsCallingPolicy:

-BusyOnBusyEnabledType
Setting this parameter lets you configure how incoming calls are handled when a user is already in a call or conference or has a call placed on hold. Valid options are: Enabled, Unanswered, and Disabled. When set to Enabled, new or incoming calls will be rejected with a busy signal. When set to Unanswered, the user's unanswered settings will take effect, such as routing to voicemail or forwarding to another user. Note: UserOverride option value is not available for use currently, if set it will be read as setting the value to Disabled

Version of the DSC module that was used ('dev' if using current dev branch)

1.22.831.1

@andikrueger andikrueger added Bug Something isn't working Teams labels Sep 12, 2022
@NikCharlebois
Copy link
Collaborator

The Set-TargetResource will accept the UserOverride value, therefore adding it to the validate set.

NikCharlebois added a commit to NikCharlebois/Microsoft365DSC that referenced this issue Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Teams
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants