Closed ricmestre closed 2 days ago
@ricmestre Ok so that was strange. I took the latest module version and your configuration and tried to reproduce the issue. At first (for about 5 times when creating), I didn't succeed and the configuration was applied successfully without any issues. But after some time, I got the exact same error message.
The fix is more than simple: Just prevent PowerShell from mangling down a single-element array to the element itself... That's what my PR at #4845 does, simply forcing PowerShell to always return an array. No idea how that didn't cause a ruckus earlier, but well.
Description of the issue
@FabienTschanz The changes you've been doing to the settings catalog messed up
IntuneSettingCatalogASRRulesPolicyWindows10
and I'm not able to deploy it anymore in my integration tests, the test I have forIntuneSettingCatalogCustomPolicyWindows10
succeeds but at this point I don't know if it's by chance or if it really works correctly.Microsoft 365 DSC Version
1.24.626.1
Which workloads are affected
Intune
The DSC configuration
Verbose logs showing the problem
Environment Information + PowerShell Version
No response