Security baseline for Microsoft Edge v83

Published May 26 2020 08:00 AM 10.5K Views

Microsoft is pleased to announce the enterprise-ready release of the security baseline for v83 of Microsoft Edge.


We have reviewed the new settings in version 83 of Microsoft Edge and determined that no new security settings are required. The settings recommended in the version 80 baseline will continue to be the security baseline for version 83! This means we will not be releasing our typical package. We continue to welcome feedback through the Baselines Discussion site.


Version 83 of Microsoft Edge adds 19 new computer- and user-based settings. There are now 311 enforceable Computer Configuration policy settings and 286 User Configuration policy settings. Using our streamlined approach, our baseline remains at 12 Group Policy settings. We have attached a spreadsheet with the new settings to make it easier for you to find them.


The version 80 package continues to be available as part of the Security Compliance Toolkit. Like all our baseline packages, this package includes:

  • Importable GPOs
  • A script to apply the GPOs to local policy
  • A script to import the GPOs into Active Directory Group Policy
  • A spreadsheet documenting all recommended settings in spreadsheet form (minus the version 83 settings that are attached to this blog)
  • Policy Analyzer rules
  • GP Reports

In case you aren’t aware, all the available settings for Microsoft Edge are documented here.  Additionally, Microsoft Edge Update settings are documented here.


One ask to the community, we are trying to determine how often we should update the baseline package on the Download Center for Microsoft Edge if new security settings have not been added and would like your feedback.  Do you think we should update it quarterly, just to keep it fresh, or only when new settings get added?

New Contributor

@Rick_Munck Thanks very much.

Valued Contributor

Cool and thank you for sharing, it is very essentials for companies since browser plays key role in their day to day tasks.

Occasional Visitor

@Rick_Munck: Could you let me know if any tentative timelines when Edgev83 Security Baseline / Security Compliance Toolkit would be released and for Windows 10 2004 as well.


@SaiRG sorry not sure I understand the question regarding Edge v83, can you please clarify.  As for v2004 please see

Occasional Visitor

@Rick_Munck is it possible to get the chromium edge v83 baseline as a spreadsheet showing each policy with the recommended/default setting?


@mike_oke there have been no changes to the settings since version 80.  We provide the delta sheets in v81 - v83 that can be merged in if you are looking for the total settings available list but since there hasn't been a need to regenerate the package we have maintained this approach.  We are however looking to possibly refresh the entire package with version 85, regardless if there are new settings or not.  Will know more after we get v84 out the door.


When you update the Windows 10 baseline every 6 months - release this at the same time?  So update every 6 months?


Thanks @Jon Sabberton that makes sense and I like that approach.  So if no new security settings are added in an Edge version we will hold on refreshing the package until the next Windows release.  Let me run with that and see if we get buy-in for that approach.

New Contributor

Ive configured many policies but the one i do not see is the ability to "set sync as mandatory"


I want to avoid users having the need to turn it on or off on first launch.


E.g. i want them the GPO to skip this screen and turn ON by default:



Any ideas?


Occasional Contributor

@Davidj840 You can configure sync using the guidance from Microsoft Edge Browser Sync Settings (The settings to hide the first run experience are managed in conjunction with the 'HideFirstRunExperience' policy.) That will allow you to hide the 'launch experience' for your users. (In testing it has worked great for me.)


@Rick_Munck Updating it without any updates to the policies just makes work for AD teams and Security Operations Teams and ISSOs to review and manage for no benefit.

That being said, a reference link with the information and documenting the last update and policies with a “This covers the currently available configurations and recommendations for versions X to Y of Microsoft Edge and available Policies have not changed since version Z” would be useful.

Valued Contributor

Microsoft Edge keeps improving and we need to observe , but we prefer to receive updates through update interface and like see a message that new update is available. It would be better to have an application for this and it gets update.

We are also looking forward for more interactive discussion on Security baseline.

New Contributor

@TheOtherJosh thanks for this! Did you manage to get around the screen for whether the user wants to sync or not?


Id like to "enforce sync" so the user doesnt have a choice...





@TheOtherJosh we definitely dont want to cause churn for the sake of it which is why we are cautious on how to approach updates to the Edge baseline.  We were hoping this blog would be sufficient when there are no changes but it might not be the case...  We will continue to chew on this feedback and try to come up with something.


@Reza_Ameri-Archived we will not be making this into an app, sorry.  We divested from the old SCM for many reasons (an app being one of them).  This framework provide us and other teams (recent examples: Windows Update and Telemetry) the ability to release quicker and with far less dependencies.  Down the road maybe you will see an updated website with some indicators but for now we have this framework.

Valued Contributor

@Rick_Munck well I was actually referring to something similar to SCM, it was nice but as you said being app, we need to install it and it need SQL Server but with new download, it is quick and easy and could run on any device. However, it would have been nice if there was some sort of integrated app inside Windows Server or Configuration Manager and it gets regular updates.

Occasional Contributor

@Rick_Munck can we have a page on the technical documentation with a reference to the baselines recommendations, or a “the baseline recommendations are located at this download link and there have been no changes to the recommendations since X version”?


@TheOtherJosh what about at the bottom of this page ( for versioning?  Trying to keep it on a page we own so we don't have to cross teams...  Thoughts?


Just wondering if the location for the enterprise site mode list (IE mode) being located at an https:// location will be included in the baseline, if indeed it's recommended this way due to security? 

Version history
Last update:
‎May 26 2020 05:18 AM
Updated by: