New Microsoft Edge to replace Microsoft Edge Legacy with April’s Windows 10 Update Tuesday release

I agree with HotCakeX about the group policies that need to be updated via Edge in c:\windows\Policydefinitions by the Edge Setup rather than relying on the user to manually download and manage them. As Edge is deliberately seperated from the OS, and should be that way to prevent any inflicts we had with IE, the ADMX should not be part of Windows CU as this would only raise the complexity at MSFT, but I see no issue (from my point of view) that the MSI file or automatic update will update the admx templates locally, even then based on the release.

Microsoft365_MicrosoftEdge_Product MissyQ  what is your idea about this solving this task HotCakeX described.

I also hope that Edge could be rolled out to Windows Server 2016 and 2019 in favor remove IE as default browser but keep it in the OS by default for various reasons.

of course enterprises could manage this on their servers on their own, however there are different usecases why an admin needs a competent browser on Windows Server 2016/2019 LTSC.

Microsoft Support is one example, access to some areas like Update catalog, IIS, Certification Web Services are some others. 

I understand the conflict of interest to integrate a 3rd party software into the lifecycle of a LTSC product though. So just wanted point out that it is just inconsistent and even a security issue to bring Server vNext "2022" with Edge as default browser - which is a good decision, but leave alone all older OS not yet in extended support. Edge has his own Support, other than IE.