Forum Discussion
Chromium Edge Extension - ForceIntall
- Nov 26, 2019
Vijay1135 wrote:
I also wants to host extension in microsoft store (For Chromium Edge). How can i do this?there is still no word about it from the developers, last time they said they will let us know and post news about it once they create a portal and mechanism so that developers can publish their extensions on Microsoft extension store.
Updating the answer 2/19/2020 (it's been roughly 3 months since)
Here is a group policy you can use:
https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#extensioninstallforcelist
ExtensionInstallForcelist
Control which extensions are installed silently
Supported Versions: Microsoft Edge on Windows and Mac since version 77 or later
Description
Specifies extensions that are installed silently, without user interaction, and that the users can't uninstall or disable ("force-installed"). All permissions requested by the extensions are granted implicitly, without user interaction, including any additional permissions requested by future versions of the extension. Furthermore, permissions are granted for the enterprise.deviceAttributes and enterprise.platformKeys extension APIs. (These two APIs are only available to extensions that are force-installed.)
This policy takes precedence over a potentially conflicting ExtensionInstallBlocklist policy. When you take an extension off of the force-installed list it's automatically uninstalled by Microsoft Edge.
For Windows devices that aren't joined to a Microsoft Active Directory domain, forced installation is limited to extensions available in the Microsoft Store.
Note that users can modify the source code of any extension by using Developer Tools, potentially rendering the extension dysfunctional. If this is a concern, set the DeveloperToolsAvailability policy.
Use the following format to add an extension to the list:
[extensionID];[updateURL]
extensionID - the 32-letter string found on edge://extensions when in developer mode.
updateURL (optional) is the address of the Update Manifest XML document for the app or extension, as described at https://go.microsoft.com/fwlink/?linkid=2095043. If you don't set the updateURL, the Microsoft Store update URL is used (currently https://edge.microsoft.com/extensionwebstorebase/v1/crx). Note that the update URL set in this policy is only used for the initial installation; subsequent updates of the extension use the update URL indicated in the extension's manifest.
For example, gggmmkjegpiggikcnhidnjjhmicpibll;https://edge.microsoft.com/extensionwebstorebase/v1/crx installs the Microsoft Online app from the Microsoft Store "update" URL. For more information about hosting extensions, see: https://go.microsoft.com/fwlink/?linkid=2095044.
If you don't configure this policy, no extensions are installed automatically, and users can uninstall any extension in Microsoft Edge.
Note that this policy doesn't apply to InPrivate mode.
Hi,
force install is possible:
policy: control wich extension are installed silently (under extensions)
example for webex extension:
- Duser615Jul 23, 2020Copper ContributorHey
Sorry for opening a closed thread but the policy is a key that is configured in the Windows Registry right? I was digging around in the files for edge trying to find the folder and add a text file or something when I noticed they listed the key type as REG_SZ. I tried adding the key to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ExtensionInstallForcelist but nothing is happening. Probably needs a restart?
I'm being a bit paranoid but I just read this from the documentation too: For Windows devices that aren't joined to a Microsoft Active Directory domain, forced installation is limited to extensions available in the Microsoft Store.
I mean I don't know about any Microsoft Active Directory domain, so safe to say I'm not on one.- STRSOHJul 29, 2020Copper Contributor
Not sure if this pertains to your issue. But, I am on a domain with about 500 users. This morning we all lost an extension in edge. The only extension that we force install using a group policy.
The "fix" was to remove the Update URL portion from the policy. i.e. https://edge.microsoft.com/extensionwebstorebase/v1/crx
After a few moments, users started reporting that the extension had returned.
Try plugging only the APP ID in the extensions list.