What I am saying is that installing the extension on a (test) system is not absolutely necessary, but I still recommend it.

Secondly, the update URL seems to be the same for all extensions, namely. Note: the URL of the Chrome extension also contains the extension's ID, so technically speaking you could copy it directly from the browser's address bar. You need to do this, otherwise you will not be able to retrieve the ID and update URL. The first thing to do, is to manually install the extension directly from the Chrome Web Store on your (test) system.

For example, the concatenated string of the extension ID and update URL for the Office Online extension version 1.5.2. These two values have to be entered as one string, but separated by a semicolon ( ). To be able to add an extension to a Group Policy, two values need to be known: the extension ID and an 'update' URL. Retrieve the extension ID and update URL of the Chrome extension

Enable and configure Chrome extensions in a Group Policy.

Retrieve the extension ID and the update URL of the Chrome extension.

This works great for individual users, but what if you want to deploy an extension to a large number of users in your organization? The solution is to deploy the extension via Group Policy.ĭeploying extensions via Group Policy consists of two parts:

Deploying Google Chrome extensions using Group PolicyĪ user can add extensions to the Chrome browser by downloading them from the Chrome Web Store:

Add extensions to chrome