evening-computing-logo-60
Get in Touch

Why won’t Chrome ADMX templates import into Intune?

Chrome ADMX template imports in Microsoft Intune can fail even when the Chrome files are not damaged. In some cases, the problem is caused by a missing ADMX dependency that Intune needs before it can understand the Chrome template.

This is a technical guide for administrators and IT support staff who manage Windows devices with Microsoft Intune. It assumes you have access to the Intune admin centre and are able to import ADMX and ADML files. If you are not responsible for device management, the practical steps may not be suitable to follow yourself, but the explanation should still help you understand why the issue happens.

In simple terms, Chrome ADMX templates are policy definition files. They tell Intune which Google Chrome settings can be managed, such as password saving, browser sync, extension control, and browsing data behaviour. The ADML files are the matching language files that provide the readable text shown in the management interface.

This guide explains what to check when chrome.admx will not import into Intune, including errors such as NamespaceMissing:Microsoft.Policies.Windows or NamespaceMissing:Google.Policies. It covers the import order that usually works, why the Windows ADMX files may be required first, and what to check before creating the Chrome policy profile.

Browse this guide

Use the links below to jump to the section most relevant to your question.

Quick resolution checklist

Start with the import order before changing the Chrome files. In many cases, the failure is not caused by a faulty Chrome download, but by a missing dependency or mismatched language file.

    1. Delete any failed chrome.admx import attempt from Intune.
    2. Confirm that you are using the en-US ADML files.
    3. Import Windows.admx with Windows.adml first if Intune reports a missing Windows namespace.
    4. Import google.admx with google.adml.
    5. Import chrome.admx with chrome.adml.
    6. Wait until each imported template shows as available before importing the next one.
    7. Create the Chrome configuration profile from Imported Administrative Templates.
    8. Test the policy on one device before assigning it widely.

If the Chrome import still fails after these steps, check the exact error message. The missing namespace usually tells you which dependency Intune cannot find.

What Chrome ADMX templates are used for

Chrome ADMX templates are files that allow administrators to manage Google Chrome settings through tools such as Microsoft Intune or Group Policy. They do not install Chrome and they do not change the browser by themselves. They make Chrome policy settings available so that an administrator can configure and apply them to managed devices.

For example, Chrome ADMX templates can help an organisation control whether users can save passwords, sign in to Chrome, use browser sync, install extensions, or keep browsing data after the browser closes. On shared or public facing computers, these settings can reduce the chance that personal data, saved credentials, browser sessions, or unwanted extensions remain available to the next person using the device.

An ADMX file contains the policy definitions. The matching ADML file contains the readable language text shown in the management interface. Intune needs both files, and it also needs any parent templates that those files depend on.

Why Chrome ADMX imports can fail

Chrome ADMX imports can fail when Intune cannot understand one of the policy namespaces referenced by the template. A namespace is a named area of policy definitions. If a Chrome template refers to a namespace that Intune has not imported yet, the import may fail even though the Chrome ADMX and ADML files are the correct files.

The error may look like a Chrome problem, but the cause may be a missing Windows or Google policy namespace. This is why the import sequence matters. Intune may need the base Windows template first, then the Google parent template, and only then the Chrome template.

What the Windows ADMX dependency means

The Windows ADMX dependency matters because some third party ADMX files refer back to policy definitions that belong to Windows. If Intune cannot see those definitions, it cannot complete the import.

For Chrome, this can show as a missing namespace such as:

NamespaceMissing:Microsoft.Policies.Windows

This does not automatically mean that the Chrome ADMX file is corrupt. It usually means Intune needs the Windows ADMX and ADML files imported first so it can understand the referenced Windows policy namespace.

The Windows files are normally found on a Windows computer at:

C:\Windows\PolicyDefinitions\Windows.admx

and:

C:\Windows\PolicyDefinitions\en-US\Windows.adml

Use the en-US language file for Intune ADMX import. Do not use another language folder, even if the device or administrator normally uses British English.

Correct import order for Chrome ADMX files

The safest import order is to import dependency files first and product specific templates afterwards. This avoids Intune rejecting the Chrome template because a referenced namespace is missing.

Use this order:

    1. Windows.admx with Windows.adml
    2. google.admx with google.adml
    3. chrome.admx with chrome.adml

The Google files must be imported before the Chrome files because Chrome policy settings depend on the Google parent template. If this step is missed, Intune may show an error referring to NamespaceMissing:Google.Policies.

After each import, wait until Intune shows the template as available before moving to the next file. If a template is still processing or has failed, importing the next dependent file may also fail.

Common import mistakes to check

Chrome ADMX import problems are often caused by small file selection mistakes. These are easy to miss because the file names look similar and the folder structure contains several language folders.

Check the following:

    1. The ADMX and ADML files must come from the same template download.
    2. The ADML file must match the ADMX file being imported.
    3. Use the en-US ADML folder.
    4. Do not use en-GB, uk-UA, or another language folder for Intune import.
    5. Review Microsoft’s current ADMX import requirements, but do not assume file size is the cause before checking the namespace error. In this case, the Chrome ADML file was larger than 1 MB and imported successfully after Windows.admx and Windows.adml were imported first.
    6. Import dependency templates before dependent templates.
    7. Delete failed imports before retrying the same template.
    8. Confirm that the imported template has become available before creating the configuration profile.

A common mistake is to import chrome.admx with the wrong chrome.adml file. Another common mistake is to import the Chrome template before importing the Windows or Google template that it depends on.

What to do after the templates import

Once the Chrome ADMX files are imported successfully, the next step is to create a configuration profile from the imported administrative templates. Importing the template only makes the settings available. It does not apply Chrome policy to devices by itself.

In Intune, create a new Windows configuration profile using Imported Administrative Templates. Then select the Chrome settings that are relevant to the devices you manage.

For public or shared training laptops, typical Chrome settings may include:

    1. Disable password saving.
    2. Disable Chrome sync.
    3. Disable or restrict browser sign in.
    4. Disable address and payment autofill.
    5. Clear selected browsing data when Chrome closes.
    6. Block external extensions where appropriate.
    7. Block all extensions by default unless a specific extension is required.

After assigning the policy, test on one device. Open Chrome and go to:

chrome://policy

Use Reload policies and confirm that the settings show as applied.

When a registry policy may be more practical

Imported ADMX templates are useful when you want to manage Chrome through visible policy settings in Intune. However, they are not always the quickest route for a small number of simple Chrome restrictions.

For a limited set of settings, a registry based Intune script may be more practical. Chrome can read machine policies from:

HKLM\SOFTWARE\Policies\Google\Chrome

This approach can be useful when the ADMX import is blocked by dependency issues, template availability, or repeated import failures that are not worth spending more time on for a small number of settings. It should still be tested carefully and documented, especially if the same organisation also uses imported administrative templates.

Do not mix several different Chrome management methods without recording which one is authoritative. If one setting is controlled by imported ADMX and another by registry script, keep a short internal note so future troubleshooting is easier.

Why this matters for managed browsers

Managed browsers are part of endpoint security. On business or training laptops, browsers can store passwords, cookies, form data, extension permissions, downloads, and session information. If those settings are not controlled, browser behaviour can undermine other device restrictions.

For example, an organisation may use Intune to manage the laptop, but still allow users to save passwords in Chrome or install browser extensions. That can create unnecessary risk, especially on shared or public facing devices.

Fixing the ADMX import issue is therefore not only an Intune administration task. It can be part of a wider browser management plan that includes password controls, extension controls, browser data cleanup, DNS filtering, and user profile management.

Supporting references

These references explain the behaviour described in this guide and should be used to verify the current Microsoft and Google guidance before making tenant wide changes.

Microsoft documentation on importing custom and third party ADMX templates in Intune.

Google Chrome Enterprise documentation on managing Chrome browser with Microsoft Intune imported administrative templates.

Microsoft Answers thread describing a Chrome and Google ADMX import issue where Windows.admx and Windows.adml had to be imported first because of the Microsoft.Policies.Windows dependency.

Peter van der Woude’s practical Intune and Chrome ADMX article, which describes the dependency relationship between Windows, Google, and Chrome templates.

Further Guidance and Support

This guide forms part of a broader layered security approach. For structured guidance on security and resilience planning, see our Security and Resilience page.

For information about practical implementation and ongoing support, you can review our IT services and local IT support coverage across London, Hertfordshire, and Essex.

Return to all guides

Author
Elías Sánchez
IT Support Consultant
Evening Computing
London, United Kingdom

This guide was prepared by Elías Sánchez with research and drafting assistance from AI tools. All technical content has been reviewed and adapted for clarity and accuracy.

Last reviewed
20 May 2026