This article covers using the Custom Registry Keys policy to enforce browser extensions for Microsoft Edge on Windows devices.
Prerequisites
- You 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’
- Example:
- Forced installation is limited to extensions published in Microsoft Edge Add-ons for non-domain joined devices.
Creating the Custom Registry Policy
- Log in to the JumpCloud Admin Portal.
- Go to DEVICE MANAGEMENT > Policies.
- Click (+).
- On the Configure New Policy page select Windows.
- From the list, next to Advanced: Custom Registry Keys and click configure.
- Give the new policy a descriptive name.
- 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. - Assign this policy to the necessary devices or groups and confirm the policy was successfully applied via the Status tab.
- 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.
Registry Key Location |
Value Name |
Type |
Data |
---|---|---|---|
SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist | 1 | SZ | ndcileolkflehcjpmjnfbnaibdcgglog |
SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist | 2 | SZ | cnlefmmeadmemmdciolhbnfeacpdfbkd |
SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist | 3 | SZ | odfafepnkmbhccpbejgmiehpchacaeak |
Back to Top