The part that comes next is not always the same, we need to follow some rules: This is default for managing applications using an ADMX file: Let`s split up the OMA-URI in seperate parts. Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Startup/HomepageLocation This is for example the OMA-URI to manage the Homepage Location But the OMA-URI for managing the settings consists of some information we need to collect ourselves from the Chrome ADMX file. How to build up the OMA-URIĪs with deploying the ADMX file, for the settings to manage we also need to know the OMA-URI which we need to use. In the next steps we add the settings we manage with Intune to the same policy.

The policy to deploy the ADMX file is ready.

On the Configuration Profiles tab click Create profile.

Sign-in to the Device Management Portal.

Now open a browser to sign-in to the Microsoft Intune portal. After downloading the bundle, locate the ADMX file and open the file with a text editor. The Chrome ADMX file can be downloaded as part Chrome Enterprise bundle. The second part of the policy is used to manage the settings of choice. The first part is used to deploy the Chrome ADMX file to the Intune managed device. Google Chrome can be managed using a custom configuration policy for Windows 10. In this new article, I show how the third-party Google Chrome browser can be managed using Microsoft Intune.

More recently I wrote an article about managing Edge for macOS settings using Intune. In the past, I wrote two articles about managing Internet Explorer settings with Microsoft Intune. Most of the settings don’t have to be configured anymore with custom OMA-URIs. Update March 2022: with the 2203 Intune release, Google Chrome settings are now available in the Intune portal as part of the Settings Catalog and Administrative Templates profiles.

Microsoft chrome