The new Microsoft Edge: 10 rules to take control of your browser. The default settings for Microsoft's new browser could stand a little tweaking. Use Microsoft Translator in Microsoft Edge browser. The new Microsoft Edge supports translation for more than 60 languages. The browser will automatically prompt you to translate a webpage when when the page you're opening is in a language other than those listed under your preferred languages in settings.
Use the following information to configure Microsoft Edge policy settings on your Windows devices.
This article applies to Microsoft Edge version 77 or later.
You can use group policy objects (GPO) to configure policy settings for Microsoft Edge and managed Microsoft Edge updates on all versions of Windows. You can also provision policy through the registry for Windows devices that are joined to a Microsoft Active Directory domain, or Windows 10 Pro or Enterprise instances enrolled for device management in Microsoft Intune. To configure Microsoft Edge with group policy objects, you install administrative templates that add rules and settings for Microsoft Edge to the group policy Central Store in your Active Directory domain or to the Policy Definition template folder on individual computers and then configure the specific policies you want to set.
You can use Active Directory group policy to configure Microsoft Edge policy settings if you prefer to manage policy at the domain level. This enables you to manage policy settings globally, targeting different policy settings to specific OUs, or using WMI filters to apply settings only to users or computers returned by a particular query. If you want to configure policy on individual computers, you can apply policy settings that only affect the local device using the Local Group Policy Editor on the target computer.
Microsoft Edge supports both mandatory and recommended policies. Mandatory policies override user preferences and prevents the user from changing it, while recommended policy provide a default setting that may be overridden by the user. Most policies are mandatory only; a subset are mandatory and recommended. If both versions of a policy are set, the mandatory setting takes precedence.
You can use Microsoft Intune to configure Microsoft Edge policy settings. For more information, see Configure Microsoft Edge using Microsoft Intune.
There are two administrative templates for Microsoft Edge, both of which can be applied either at the computer or Active Directory domain level:
To get started, download and install the Microsoft Edge administrative template.
If you want to configure Microsoft Edge policy settings in Active Directory, download the files to a network location you can access from a domain controller or a workstation with the Remote Server Administration Tools (RSAT) installed. To configure on an individual computer, simply download the files to that computer.
When you add the administrative template files to the appropriate location, Microsoft Edge policy settings are immediately available in the Group Policy Editor.
Go to the Microsoft Edge Enterprise landing page to download the Microsoft Edge policy templates file (MicrosoftEdgePolicyTemplates.cab) and extract the contents.
On a domain controller or workstation with RSAT, browse to the PolicyDefinition folder (also known as the Central Store) on any domain controller for your domain. For older versions of Windows Server, you may need to create the PolicyDefinition folder. For more information, see How to create and manage the Central Store for Group Policy Administrative Templates in Windows.
Open MicrosoftEdgePolicyTemplates and go to windows > admx.
Copy the msedge.admx file to the PolicyDefinition folder. (Example: %systemroot%sysvoldomainpoliciesPolicyDefinitions)
In the admx folder, open the appropriate language folder. For example, if you’re in the U.S., open the en-US folder.
Copy the msedge.adml file to the matching language folder in the PolicyDefinition folder. Create the folder if it does not already exist. (Example: %systemroot%sysvoldomainpoliciesPolicyDefinitionsEN-US)
If your domain has more than one domain controller, the new ADMX files will be replicated to them at the next domain replication interval.
To confirm the files loaded correctly, open the Group Policy Management Editor from Windows Administrative Tools and expand Computer Configuration > Policies > Administrative Templates > Microsoft Edge. You should see one or more Microsoft Edge nodes as shown below.
You can set mandatory or recommended policies to configure Microsoft Edge with the Group Policy Editor for both Active Directory and individual computers. You can scope policy settings to either the Computer Configuration or User Configuration by selecting the appropriate node as described below.
To configure a mandatory policy, open the Group Policy Editor and go to (Computer Configuration or User Configuration) > Policies > Administrative Templates > Microsoft Edge.
To configure a recommended policy, open the Group Policy Editor and go to (Computer Configuration or User Configuration) > Policies > Administrative Templates > Microsoft Edge – Default Settings (users can override).
On a target client device, open Microsoft Edge and navigate to edge://policy to see all policies that are applied. If you applied policy settings on the local computer, policies should appear immediately. You may need to close and reopen Microsoft Edge if it was open while you were configuring policy settings.
For Active Directory group policy settings, policy settings are propagated to domain computers at a regular interval defined by your domain administrator, and target computers may not receive policy updates right away. To manually refresh Active Directory group policy settings on a target computer, execute the following command from a command prompt or PowerShell session on the target computer:
You may need to close and reopen Microsoft Edge before the new policies appear.
You can also use REGEDIT.exe on a target computer to view the registry settings that store group policy settings. These settings are located at the registry path HKLMSOFTWAREPoliciesMicrosoftEdge.
Learn how to access Microsoft Edge Legacy after installing the new version of Microsoft Edge.
This article applies to the Microsoft Edge Stable channel.
While most organizations will want to replace Microsoft Edge Legacy with the new version, there are some situations where users will need access to both versions. For example:
Running Microsoft Edge Legacy side-by-side with the new version of Microsoft Edge is not recommended for use in production. This configuration should only be used in specific cases where testing with both browser versions is required.
The Microsoft Edge Legacy desktop app will reach end of support on March 9, 2021 in favor of the new Microsoft Edge. This means that Microsoft Edge Legacy will not receive security updates after that date. This change is applicable to all experiences that run in the Microsoft Edge Legacy desktop app. Learn more.
Starting with Windows 10 version 20H2 Microsoft Edge Legacy is no longer included. Starting with this version of Windows 10 the side-by-side experience is not supported.
The procedures in this article apply to systems that have been updated with the latest security updates. When the new version of Microsoft Edge is installed, the old version (Microsoft Edge Legacy) will be hidden. By default, all attempts to launch the old version will redirect the user to the newly installed version of Microsoft Edge. This article describes how you can keep using Microsoft Edge Legacy after you install Microsoft Edge.
Before using the detailed instructions in this article, consider the following two steps to let your users run Microsoft Edge Legacy and the Microsoft Edge Beta channel side-by-side.
Prevent the automatic install of the Stable Channel of Microsoft Edge by Windows Update.
Use the Blocker Toolkit to disable automatic delivery of Microsoft Edge.
Install the Beta channel of the new version of Microsoft Edge.
Read Additional information for information about Registry Key settings.
This side-by-side solution is less complex and requires less management than the detailed solution described in this article. However, this solution does mean that you'll be running the Beta Channel rather than the Stable Channel.
Installing the Stable Channel of the next version of Microsoft Edge at the system-level will cause the current version (Microsoft Edge Legacy) to be hidden. If you want to let your users see both versions of Microsoft Edge side by side in Windows, you can enable this experience by setting the Allow Microsoft Edge Side by Side browser experience group policy to Enabled.
This group policy is documented here
Install the Policy Definitions from Microsoft Edge for Business.
Open the Group Policy Editor (gpedit.msc).
Under Computer Configuration, go to Administrative Templates>Microsoft Edge Update>Applications.
If you don't see the Microsoft Edge Update folder, verify that step 1 was completed correctly.
Under Applications, double-click 'Allow Microsoft Edge Side by Side browser experience'. See our best practice guidance before continuing to the next step.
Note Tourism geography notes.
By default, this group policy is set to 'Not configured', which results in Microsoft Edge Legacy being hidden when the new version of Microsoft Edge is installed.
Select Enabled and then click OK.
Setting this policy will set the following Registry Key to '00000001':
For the best experience, the Allow Microsoft Edge Side by Side browser experience should be enabled before the new version of Microsoft Edge is deployed to your users' devices.
If the group policy is enabled after Microsoft Edge is deployed, there are the following side effects and required actions:
Allow Microsoft Edge Side by Side browser experience won't take effect until after the installer for the new version of Microsoft Edge is run again.
The installer can be run directly or automatically when the new version of Microsoft Edge updates.
Microsoft Edge Legacy will need to be re-pinned to Start or the Taskbar because the pin is migrated when the new version of Microsoft Edge is deployed.
Sites that were pinned to Start or the Taskbar for Microsoft Edge Legacy will be migrated to the new version of Microsoft Edge.
After the systems are fully updated and the Stable channel of the next version of Microsoft Edge is installed, the following registry key and value is set:
This key is over-written every time the Microsoft Edge Stable channel is updated. As a best practice, we recommend that you DO NOT delete this key to allow users to access both versions of Microsoft Edge.