Forum Discussion
Solved
GPO for "Allow extensions from other store"
You can manually enable the option to get extensions from other stores. https://techcommunity.microsoft.com/t5/Discussions/Extensions-Chrome-or-Microsoft-Store/m-p/469515/highlight/true#M1602 Is ...
not so sure what kind of workaround works for you now?
As long as it isn't enabled manually, by the user, no extensions will be available, including the forced ones. That's basically why that GPO is required.
ashishpoddar
Microsoft
Microsoftjanusro1 Force installed extensions do not require the setting "Allow extensions from other stores" hence having this policy is not a blocker for enterprise installed extensions.
Let me know if you have any further questions
ashishpoddar Thank you for providing this information.
Is there a way to self-host the extensions that i want to force-install? I want to implement an extension in an air-gapped network where the extension stores aren't available.
Unfortunately, the documentation is incomplete in that regard.
- ashishpoddarWe have hosted this documentation here https://docs.microsoft.com/en-us/deployedge/microsoft-edge-manage-extensions-webstore check it out and let us know your feedback.
- ashishpoddar
smokie128 We are yet to update our documentation for the same. However the Chromium guidelines apply. Here are some high level pointers.
- Create crx file of extension and host it to shared directory (manifest.json file of extension should not contain "key" attribute and should have update_url attribute pointing to correct place). The shared location should not require any authentication else force install will fail.
- Creates updates.xml file with crx file hosted url, version and extension id. (Check this link for details: (https://developer.chrome.com/apps/autoupdate)
- Set up extensionInstallsources policy to whitelist hosted url. (https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#extensions)
- Set up extenionInstallForcelist policy to forceinstall extension. (https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#extensions)
Let me know if this works.
I was able to get everything working as intended in this way.
Anyone else doing this should be aware that this changes the extension ID's, which can lead to problems with extensions that use Native Messaging (e.g. KeePassXC-Browser) - in this case you'd have to add the correct extension ID into the Native Messaging JSON file as an allowed source.
- ashishpoddar
Not yet, it is still not prioritized. Currently we are looking to sync this setting so that it works seamlessly against multiple devices. That feature should be launched along with Extensions sync.
