Troubleshoot: Force Install Browser Extensions for MS Edge

This article covers using the Custom Registry Keys policy to enforce browser extensions for Microsoft Edge.

Prerequisite

Before creating the custom policy, you will need the IDs of the browser extensions you will be installing on your endpoints. This ID can be found in the extension URL, and is unique to the extension.

• Example: https://microsoftedge.microsoft.com/addons/detail/adobe-acrobat-pdf-edit-/elhekieabhbkpmcefcoobjddigjcaadp?hl=en-US
  • The ID you would use to install the Adobe Acrobat browser extension is ‘elhekieabhbkpmcefcoobjddigjcaadp’

Creating the Custom Registry Policy

1. From the Admin Console, create a new policy and select Advanced: Custom Registry Keys.
2. Give the new policy a descriptive name.
3. Using the table below as an example, add as many browser extensions as needed to the SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist location in the registry.
4. Assign this policy to the necessary devices or groups and confirm the policy was successfully applied via the Status tab.
5. Once applied, any extensions installed via this policy will be visible in the browser’s Extensions page, and will be labeled as managed by your organization. These extensions cannot be removed by the end user.