Improvement #10332
Updated by Navod Zoysa 11 months ago
Some ADMX policies are only supported on certain Windows OS versions or editions and currently we can get the oldest supported Windows OS version from the parsed ADMX files which is paired to the "supportedOn" key in the policy definition. The supported editions might need to be mapped manually to the policy definition.
For reference this is a policy that supports all editions of Windows 10/11 - https://learn.microsoft.com/en-us/windows/client-management/mdm/policy-csp-admx-appxruntime
When applying an unsupported policy, the device does not send an error response back and due to this the device operations log will show the POLICY_BUNDLE as completed. In order to avoid this situation the above mentioned solution was proposed.