Niels Kok

Results 6 comments of Niels Kok

> If I'm not mistaken, the normal way to address a profile and its creation is by defining every last configurable property of it. For the security baselines, because they...

> new Windows 23H2 Security Baseline ist part of (Get)-MgBetaDeviceManagementConfigurationPolicy True, and the new versions will also be available in settings catalog. So, I think we can close this one.

I added these lines to the policy: ![SCR-20240318-pppf](https://github.com/microsoft/Microsoft365DSC/assets/47400512/57b5b59c-4177-45a9-b863-553dd7e3de50) It looks like it deployed: ![SCR-20240318-ppxg](https://github.com/microsoft/Microsoft365DSC/assets/47400512/dea5162e-40e0-42f9-9b4b-066a96a3da7d) But, It throws this error: ![image](https://github.com/microsoft/Microsoft365DSC/assets/47400512/81ac6989-44cc-4930-bffe-6dd6913026da) Thanks.

It does set the setting: ![SCR-20240318-qkxy](https://github.com/microsoft/Microsoft365DSC/assets/47400512/d51021c8-edef-41ed-96a4-b9ae232b3415) But, why does it throw the error? Thanks!

this is no longer needed. I solved this in a new version of MIcrosoft 365 Dsc.