Update 10.01.2020: The docs article is updated with better information about which devices are targeted. https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-blocker-toolkit#overview
Update 27.12.2019: The Microsoft Edge team informed me, that they will only make Edge available in specific scenarios. For more information read the comment of Sean. Thanks for this update and hopefully the official docs will be updated soon.
Microsoft is planning to release the chromium based edge to customers around the 15. January. Most of us can’t wait on the release of this new version but as workplace engineers we also have to test, communicate and plan the rollout to end users. Therefore, we need some control over it. If you use WSUS or MEMCM/SCCM to deploy your updates, then you are just fine. But if you are using Windows Update for Business then you need to take action to control the rollout of the new Microsoft Edge. This preparation is just because it’s unclear what the general availability in the mentioned blog means and currently we do not know on which channels Microsoft will release the new version at this date. But for sure it’s good if you start testing your applications with the new version soon.
Why should you block the update?
The chromium based Edge brings a lot of cool new features but also a lot of new security settings. Therefore, it’s important, that you verify and configure all settings correctly from the beginning. This also includes compatibility settings and think about how favorites will be handled in the future.
Microsoft released a docs article which describes which registry keys are used to block the update. The toolkit contains also a cmd (Really a CMD!!!!) and a ADMX file to use GPO’s.
First I think we should use PowerShell scripts to set the registry key and not a CMD file. One reason is, that we are then also able to deploy it via Intune, which will be the main customer group because they use Windows Update for Business, but also regarding security. In this blog I will share how to deploy the setting with a PowerShell script.