Skip to main content

Deploy Chrome and Edge browser extensions with Level

Use a Windows automation to configure Chrome or Edge ExtensionInstallForcelist policy values, test on one device, and verify the browser policy.

Introduction

You can use a Windows automation to deploy a browser extension through the browser's enterprise policy. This article shows how to configure Chrome or Microsoft Edge with the ExtensionInstallForcelist policy by using Set registry key or Run script.

This workflow requires the extension vendor's supported extension ID and, when applicable, update manifest URL. Level does not validate the extension, its permissions, or the vendor's hosting and update requirements.

🖥️ PLATFORM NOTE: This procedure applies to Windows devices. Chrome and Edge policy behavior can vary by browser version, device management state, and extension distribution method. Follow the vendor's and browser maker's current requirements.

Before you begin

Confirm the following with the extension vendor and your browser administrator:

  • The exact 32-character extension ID.

  • Whether the extension is distributed through the Chrome Web Store, Microsoft Edge Add-ons, or a vendor-hosted update service.

  • The vendor-provided update manifest URL, if one is required. Do not invent or substitute an update URL.

  • Any browser-version, licensing, sign-in, domain-join, or network requirements.

  • Whether the extension requires additional policies, permissions, or companion software.

Test the configuration on one representative Windows device before assigning it to a larger group.

Choose the browser policy path

Use one of these registry paths as the Registry path in Level. Use the HKLM: hive prefix and the ExtensionInstallForcelist policy key:

  • Google Chrome: HKLM:\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist

  • Microsoft Edge: HKLM:\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist

Each extension is a String (REG_SZ) value. Number the value names sequentially, such as 1, 2, and 3. Set each value to the vendor-provided extension ID. If the browser policy requires an update URL, append it after a semicolon:

extension-id;https://vendor.example/update-manifest.xml

Use the exact ID and URL supplied for the target browser. For store-hosted extensions, the browser may use its default store update URL when no update URL is supplied, subject to the browser's current policy documentation.

Option 1: Set the registry value with Set Registry Key

  1. Create or open a Windows automation and add the Set registry key action from the System category.

  2. In Registry path, enter the Chrome or Edge path above.

  3. In Key name, enter a numbered value name such as 1.

  4. Set Value type to String.

  5. In Value, enter the vendor-provided extension ID, optionally followed by ; and the vendor-provided update manifest URL.

  6. Save the automation and run it on one test device.

For details about the action fields and registry path syntax, see Set Registry Key Action.

Option 2: Use Run Script

Use a saved PowerShell script when you need conditional logic, multiple policy values, validation, or a controlled rollback. Run the script in the account context required by your registry policy, and make sure it returns an appropriate exit code.

  1. Create or select a saved PowerShell script that writes the required REG_SZ values under the browser's ExtensionInstallForcelist key.

  2. Add the Run script action to the automation pipeline.

  3. Select the script, review its variables and execution context, and run it on one test device.

  4. Confirm the action succeeds before expanding the assignment.

For details about creating and selecting scripts, see Run Script Action.

⚠️ WARNING: Review registry scripts before running them at scale. A wrong extension ID, update URL, value name, or policy path can prevent the intended extension from installing or can apply an unintended browser policy.

Validate the installation

After the automation completes:

  1. Open the target browser on the test device.

  2. Open the browser's policy page: chrome://policy for Chrome or edge://policy for Edge.

  3. Select Reload policies if available.

  4. Confirm that ExtensionInstallForcelist appears with the expected numbered value and that the policy status does not show an error.

  5. Open the browser's extensions page and confirm the expected extension is installed and enabled according to the vendor's instructions.

  6. Check the automation result and any script output for failures.

If the policy page reports an error, compare the path, value type, numbered value name, extension ID, and update URL with the browser's current policy documentation and the vendor's instructions.

Remove or roll back the extension policy

Plan the rollback before broad deployment. Remove the specific numbered policy value using your approved policy-management method, or use a reviewed PowerShell script through Run Script to remove the value. Do not delete the whole browser policy key if other managed extensions use it.

After removal, run the automation on the test device again and reload the browser policies. The browser's behavior after a force-installed extension is removed depends on the browser and extension policy state. Follow the current Chrome or Edge policy documentation and the vendor's uninstall guidance, then verify the result in the policy page and extensions page.

Browser policy references

Related Articles
Did this answer your question?