You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring
On release 1.23.809.1 the cmdlet Compare-M365DSCConfigurations was updated on PR #3526 to fix #3478, nevertheless due to a typo it actually made it worse since for instance running Assert-M365DSCBlueprint will now report drifts that clearly aren't.
Verbose logs showing the problem
Suggested solution to the issue
Fix typo in name of variable in M365DSCReport.psm1:L888
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
Win10
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.809.1 (later versions still have same issue)
The text was updated successfully, but these errors were encountered:
Details of the scenario you tried and the problem that is occurring
On release 1.23.809.1 the cmdlet Compare-M365DSCConfigurations was updated on PR #3526 to fix #3478, nevertheless due to a typo it actually made it worse since for instance running Assert-M365DSCBlueprint will now report drifts that clearly aren't.
Verbose logs showing the problem
Suggested solution to the issue
Fix typo in name of variable in M365DSCReport.psm1:L888
The DSC configuration that is used to reproduce the issue (as detailed as possible)
N/A
The operating system the target node is running
Win10
Version of the DSC module that was used ('dev' if using current dev branch)
1.23.809.1 (later versions still have same issue)
The text was updated successfully, but these errors were encountered: