Forum Discussion
How do I deploy custom (in-house) Chromium Edge extensions to my organization?
- Mar 31, 2020
Andrew Colombino - If you do not want to publish your extension to store (as hidden as well), the other option is to host the extension in a location within your network that is accessible to all users' devices & use the extension install source policy (which allows you to set the network location from where the extension can be picked up) along with force install policy to deploy the extension.
Here is the policy documentation for your reference:
Extension install sources - https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#extensioninstallsourcesForce install policy - https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#extensioninstallforcelist
Let us know if you have any other questions!
Thanks!
Kelly_YHi I'm not having any luck with this. I'm using the Nasa Picture of the day example code from yourhttps://github.com/MicrosoftEdge/MicrosoftEdge-Extensions-Demos/tree/master/extension-getting-started-part1/part1
I am able to load it unpacked, and it works when clicking on the extension icon. I then pack it and remove the unpacked version. Your document states that I should then be able to drag the resultant .crx file onto the edge://extensions screen and it look something like this:
When I try this with the crx created from your code I get a disabled extension and an error:
I'm on a domain-joined machine, I have Edge 89.0.774.77. My group policy options for Edge extensions are all set to not configured:
In the edge://extensions screen I have the following options enabled:
Your help is appreciated.
DeltaWasp Hi! Sorry to hear it's not working! I'm adding ashishpoddar from the Extension Team to the thread to take a look at the error. Thanks!
-Kelly
- ashishpoddarApr 26, 2021
Microsoft
Thanks for confirming, I have submitted a PR to update the documentation, the change should be live soon.
- DeltaWaspApr 26, 2021Brass ContributorI've done that in group policy, performed a gpupdate and can now succesfully drag the locally packaged crx file onto the edge://extensions page and I no longer get the error. I'd suggest updating your doc with that detail.
Thanks
Thanks - ashishpoddarApr 25, 2021
Microsoft
Hi
Can you please try by adding the extension ID (CRX ID) to the ExtensionInstallAllowList? https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#extensioninstallallowlist - DeltaWaspApr 22, 2021Brass ContributorHi any update?