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

TeamsUpdateManagementPolicy: Reports on irrelevant property "UpdateTimeOfDay" #2062

Closed
magnusatteamsrocks opened this issue Jul 5, 2022 · 1 comment · Fixed by #2095 or #2123
Closed
Labels
Bug Something isn't working Teams

Comments

@magnusatteamsrocks
Copy link

ISSUE DESCRIPTION (this template):
Please provide information regarding your issue under each header below.
Write N/A under any headers that do not apply to your issue, or if the
information is not available.

NOTE! Sensitive information should be obfuscated.

PLEASE KEEP THE HEADERS.

You may remove this comment block, and the other comment blocks,
but please keep the headers.

-->

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

After adding the TeamsUpdateManagementPolicy the delta report will show, for every update policy, that a resource has been configured differently because the UpdateTimeOfDay property has changed. It seems this property changes every day by default, which makes it look like there is a configuration change every day, which is not the case.

Verbose logs showing the problem

Suggested solution to the issue

Remove the UpdateTimeOfDay property from the resource.

The DSC configuration that is used to reproduce the issue (as detailed as possible)

# insert configuration here

The operating system the target node is running

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

1.22.629.1

@malauter malauter added Bug Something isn't working Teams labels Jul 5, 2022
@NikCharlebois
Copy link
Collaborator

As a fix, we will move from having the property be extracted as:

2022-07-13T18:00:00Z

To simply being extracted as hour:

18:00:00

This will fix the discrepancy issue.

NikCharlebois added a commit to NikCharlebois/Microsoft365DSC that referenced this issue Jul 13, 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.

3 participants