Hi all,
We set the following policy:
Microsoft Edge\Extensions\Control which extensions cannot be installed - Enabled - *
This to block all extensions which we do not whitelist.
Next to that we set the following setting:
Microsoft Edge\Extensions\Allow specific extensions to be installed - enabled - {GUID}
To whitelist all the guids we want to whitelist. This also includes guids from the Google Chrome webstore.
This works perfectly.
Now, what I didn't find, is a policy to control the following settings:
It would be nice to have control over those toggles.
Procmon didn't deliver any results, so I guess this is save somewhere in a config file now.
@Matthias Vandenberghe Hi Matthias. These two toggle are primarly for the end users:
a) Developer mode is only required if someone is developing an extension and wants to test it by sideloading the extension. We do not recommend, enabling/disabling this by policy, as it is a very sparse use case any way. Moreover, developers understand this as a similar option has been available in Google Chrome for a while. (Also note that if you set the policy "Control which extensions cannot be installed - Enabled to "*", it is implied that even developers cannot side load any extensions)
b) Allow extensions from other stores: is a setting for users to turn on, in case they want to install extensions from other stores such as Chrome Web Store. However since a large number of developers have already published their extensions to Microsoft Edge addons website (and more on the way), we expect that most users will not need it. Also, in case the toggle is turned off, and users go to install an extension from Chrome Web Store they see a prominent message asking them to turn this on:
Do you still think there is a need for a policy for "Allow extensions from other stores"? Are there users who are complaining that this workflow is an issue? Would be great to know exact user feedback so that we can fix the core issue as well.
