Oct 14 2020 07:28 AM
Oct 15 2020 01:41 AM
@Reza_Ameri-Archived Thanks for responding, but I believe what you described is for 'Classic' Edge and not for 'edge://flags', apologies, I should have been more explicit and stated that I'm referring to current Chromium based Edge (v79 and above).
Oct 15 2020 06:11 AM - edited Oct 15 2020 06:18 AMSolution
but you are correct, can't be confused with legacy Edge because the community and forum related to legacy Edge was closed a few months ago with lots of notices. everything here is about the new Microsoft Edge (Chromium based).
Also Microsoft hasn't embedded the new Edge browser's group policies into Windows 10 yet. so you need to install them manually from the business landing page of Edge:
once you install them, you can browser Microft Docs website for the thorough explanation of each policy.
there is one policy regarding URL blocking:
and it states that:
"Note that blocking internal 'edge://*' URLs isn't recommended - this may lead to unexpected errors."
you can test this out and see if it works for Edge://flags.
Oct 15 2020 08:20 AM
Try download and Configure Group Policies for Microsoft Edge:
Look into policies and if you won't find it, then you may share this through feedback option.
As workaround you may use following policy: