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

TeamsMeetingPolicy: NewMeetingRecordingExpirationDays does not allow "-1" #3889

Closed
heizkoerperchen opened this issue Nov 14, 2023 · 1 comment
Labels
Bug Something isn't working Teams V1.23.1108.1 Version 1.23.1108.1

Comments

@heizkoerperchen
Copy link

Description of the issue

As documentation is stating
image

and also an actual export is containing, it's possible to set the value for the parameter NewMeetingRecordingExpirationDays in TeamsMeetingPolicies to "-1" which means "never".
Unfortunately the data type for this parameter within Microsoft365DSC is set to UInt32 which only can contain values between 0 and 4294967295. This is leading to an error that "-1" is not in the range of UInt32.

Microsoft 365 DSC Version

V1.23.1108.1

Which workloads are affected

Teams

The DSC configuration

No response

Verbose logs showing the problem

No response

Environment Information + PowerShell Version

No response

@andikrueger andikrueger added Bug Something isn't working Teams V1.23.1108.1 Version 1.23.1108.1 labels Nov 15, 2023
@malauter
Copy link
Member

Duplicate of #4090
Will be fixed with #4093

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 V1.23.1108.1 Version 1.23.1108.1
Projects
None yet
Development

No branches or pull requests

3 participants