Edge for Windows Windows 7 Service Pack 1 Windows 8.1 This update is not intended to target Enterprise devices. Specifically, this update targets devices that run Windows 7 SP1 or later versions and Windows 8.1 or later versions that are either Home, Professional, Ultimate, Starter, or Core editions. The new Microsoft Edge is based on Chromium and was released on January 15, 2020. It is compatible with all supported versions of Windows, and macOS. With speed, performance, best in class compatibility for websites and extensions, and built-in privacy and security features, it's the only browser you'll ever need. Try the new Microsoft Edge now. The Chromium-based Microsoft Edge web browser will only be made available on Windows 7 if the following is true: The SHA-2 update from September 23, 2019 or a later SHA-2 update needs to be installed and the system needs to have been restarted at least once. Microsoft Edge is mentioned in the fastest web browser for Windows. The 89.0.774.54 version of Microsoft Edge is provided as a free download on our website. This download was checked by our antivirus and was rated as safe.
Select a download
Before installing, please note:
These virtual machines expire after 90 days. We recommend setting a snapshot when you first install the virtual machine which you can roll back to later. Mac users will need to use a tool that supports zip64, like The Unarchiver, to unzip the files.
The password to your VM is 'Passw0rd!'
View installation instructions
Edge For Win 7 Download
The Microsoft Software License Terms for the Microsoft Edge and IE VMs are included in the release notes and supersede any conflicting Windows license terms included in the VMs. By downloading and using this software, you agree to these license terms.
-->This article explains how to configure Microsoft Edge on Windows 10 using Mobile Device Management (MDM) by means of ADMX Ingestion. This article also describes:
- How to create Open Mobile Alliance Uniform Resource Identifier (OMA-URI) for Microsoft Edge policies.
- How to configure Microsoft Edge in Intune using ADMX ingestion and custom OMA-URI.
Note
This article applies to Microsoft Edge version 77 or later.
Prerequisites
Windows 10, with the following minimum system requirements:
- Windows 10, version 1903 with KB4512941 and KB4517211 installed
- Windows 10, version 1809 with KB4512534 and KB4520062 installed
- Windows 10, version 1803 with KB4512509 and KB4519978 installed
- Windows 10, version 1709 with KB4516071 and KB4520006 installed
Overview
You can configure Microsoft Edge on Windows 10 using MDM with your preferred Enterprise Mobility Management (EMM) or MDM provider that supports ADMX Ingestion.
Configuring Microsoft Edge with MDM is a two part process:
Ingesting the Microsoft Edge ADMX file into your EMM or MDM provider. See your provider for instructions on how to ingest an ADMX file.
Note
For Microsoft Intune, see Configure Microsoft Edge in Intune using ADMX ingestion.
Creating an OMA-URI for a Microsoft Edge policy.
Create an OMA-URI for Microsoft Edge policies
The following sections describe how to create the OMA-URI path and look up and define the value in XML format for mandatory and recommended browser polices.
Before you get started download the Microsoft Edge policy templates file (MicrosoftEdgePolicyTemplates.cab) from the Microsoft Edge Enterprise landing page and extract the contents.
There are three steps for defining the OMA-URI:
Create the OMA-URI path
Use the following formula as a guide for creating the OMA-URI paths. ./Device/Vendor/MSFT/Policy/Config/<ADMXIngestName>~Policy~<ADMXNamespace>~<ADMXCategory>/<PolicyName>
| Parameter | Description |
|---|---|
| <ADMXIngestName> | Use 'Edge' or what you defined when ingesting the administrative template. For example, if you used './Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/MicrosoftEdge/Policy/EdgeAdmx', then use 'MicrosoftEdge'. The <ADMXIngestionName> must match what was used when you ingested the ADMX file. |
| <ADMXNamespace> | Either 'microsoft_edge' or 'microsoft_edge_recommended' depending on whether you're setting a mandatory or recommended policy. |
| <ADMXCategory> | The 'parentCategory' of the policy is defined in the ADMX file. Omit the <ADMXCategory> if the policy isn't grouped (No 'parentCategory' defined). |
| <PolicyName> | The policy name can be found in the Browser policy reference article. |
URI path example:
For this example, assume the <ADMXIngestName> node was named “Edge' and you're setting a mandatory policy. The URI path would be:./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~<ADMXCategory>/<PolicyName>
If the policy isn't in a group (for example, DiskCacheSize) remove '~<ADMXCategory>'. Replace <PolicyName> with the name of the policy, DiskCacheSize. The URI path would be:./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge/DiskCacheSize
If the policy is in a group, follow these steps:
- Open msedge.admx with any xml editor.
- Search for the policy name you want to set. For example, 'ExtensionInstallForceList'.
- Use the value of the ref attribute from the parentCategory element. For example, 'Extensions' from <parentCategory ref=' Extensions'/>.
- Replace
<ADMXCategory>with the ref attribute value to construct the URI path. The URI path would be:/Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~Extensions/ExtensionInstallForcelist
Specify the data type
The OMA-URI data type is always “String”.
Set the value for a browser policy
This section describes how to set the value, in XML format, for each data type. Go to Browser policy reference to look up the data type of the policy.
Note
For non-Boolean data types, the value always starts with <enabled/>.
Boolean data type
For policies that are Boolean types use <enabled/> or <disabled/>.
Integer data type
The value always needs to start with the <enabled/> element followed by <data value='[decimal value]'/>.
To find the value name and decimal value for a new tab page, use the following steps:
- Open msedge.admx with any xml editor.
- Search for the
<policy>element where the name attribute matches the policy name you want to set. For 'RestoreOnStartup', search forname='RestoreOnStartup'. - In the
<elements>node, find the value you want to set. - Use the value in the 'valueName' attribute in the
<elements>node. For 'RestoreOnStartup' the 'valueName' is 'RestoreOnStartup'. - Use the value in the 'value' attribute in the
<decimal>node. For 'RestoreOnStartup' to open the new tab page the value is '5'.
To open the new tab page on startup use:<enabled/> <data value='5'/>
List of strings data type
The value always needs to start with the <enabled/> element followed by <data value='[string 1];[string 2];[string 3]'/>.
Note
The 'id=' attribute name isn't the policy name, even though in most cases it matches the policy name. It's the <list> node id attribute value, which is found in the ADMX file.
To find the listID and define the value to block a URL, follow these steps:
Get Edge For Win7
- Open msedge.admx with any xml editor.
- Search for the
<policy>element where the name attribute matches the policy name you want to set. For 'URLBlocklist', search forname='URLBlocklist'. - Use the value in the 'id' attribute of the
<list> node for [listID]. - The 'value' is a list of URLs separated by a semicolon (;)
For example, to block access to contoso.com and https://ssl.server.com:<enabled/> <data value='contoso.com;https://ssl.server.com'/>
Dictionary or String data type
The value always needs to start with the <enabled/> followed by <data value='[string]'/> .
To find the textID and define the value set the locale, follow these steps:
- Open msedge.admx with any xml editor.
- Search for the
<policy>element where the name attribute matches the policy name you want to set. For 'ApplicationLocaleValue', search forname='ApplicationLocaleValue'. - Use the value in the 'id' attribute of the
<text>node for[textID]. - Set the 'value' to the culture code.
To set the locale to 'es-US' with the 'ApplicationLocaleValue' policy:<enabled/> <data value='es-US'/>
Create the OMA-URI for a recommended policies
Defining the URI path for recommended policies depends on the policy you want to configure.
To define the URI path for a recommended policy
Edge For Win 7 Install
Use the URI path formula (./Device/Vendor/MSFT/Policy/Config/<ADMXIngestName>~Policy~<ADMXNamespace>~<ADMXCategory>/<PolicyName>) and the following steps to define the URI path:
Open msedge.admx with any xml editor.
If the policy you want to configure isn't in a group, skip to step 4 and remove
~<ADMXCategory>from the path.If the policy you want to configure is in a group:
To look up the
<ADMXCategory>, search for the policy you want to set. When searching append '_recommended' to the policy name. For example, a search for 'RegisteredProtocolHandlers_recommended” has the following result:Copy the value of the ref attribute from the
<parentCategory>element. For 'ContentSettings', copy 'ContentSettings_recommended' from<parentCategory ref=' ContentSettings_recommended'/>.Replace
<ADMXCategory>with the ref attribute value to construct the URI path in the URI path formula.
The
<PolicyName>is the name of the policy with '_recommended' appended to it.
Edge For Win 7
OMA-URI path examples for recommended policies
The following table shows examples of OMA-URI paths for recommended policies.
| Policy | OMA-URI |
|---|---|
| RegisteredProtocolHandlers | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge_recommended~ContentSettings_recommended/RegisteredProtocolHandlers_recommended |
| PasswordManagerEnabled | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge_recommended~PasswordManager_recommended/PasswordManagerEnabled_recommended |
| PrintHeaderFooter | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge_recommended~Printing_recommended/PrintHeaderFooter_recommended |
| SmartScreenEnabled | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge_recommended~SmartScreen_recommended/SmartScreenEnabled_recommended |
| HomePageLocation | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge_recommended~Startup_recommended/HomepageLocation_recommended |
| ShowHomeButton | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge_recommended~Startup_recommended/ShowHomeButton_recommended |
| FavoritesBarEnabled | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge_recommended~/FavoritesBarEnabled_recommended |
OMA-URI examples
Edge For Win 7 Pro
OMA-URI examples with their URI path, type, and an example value.
Boolean data type examples
ShowHomeButton:
| Field | Value |
|---|---|
| Name | Microsoft Edge: ShowHomeButton |
| OMA-URI | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~Startup/ShowHomeButton |
| type | String |
| Value | <enabled/> |
DefaultSearchProviderEnabled:
| Field | Value |
|---|---|
| Name | Microsoft Edge: DefaultSearchProviderEnabled |
| OMA-URI | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~DefaultSearchProvider/DefaultSearchProviderEnabled |
| type | String |
| Value | <disable/> |
Integer data type examples
AutoImportAtFirstRun:
| Field | Value |
|---|---|
| Name | Microsoft Edge: AutoImportAtFirstRun |
| OMA-URI | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge/AutoImportAtFirstRun |
| type | String |
| Value | <enabled/><data value='1'/> |
DefaultImagesSetting:
| Field | Value |
|---|---|
| Name | Microsoft Edge: DefaultImagesSetting |
| OMA-URI | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~ContentSettings/DefaultImagesSetting |
| type | String |
| Value | <enabled/><data value='2'/> |
DiskCacheSize:
| Field | Value |
|---|---|
| Name | Microsoft Edge: DiskCacheSize |
| OMA-URI | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge/DiskCacheSize |
| type | String |
| Value | <enabled/><data value='1000000'/> |
List of strings data type examples
RestoreOnStartupURLS:
| Field | Value |
|---|---|
| Name | Microsoft Edge: RestoreOnStartupURLS |
| OMA-URI | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~Startup/RestoreOnStartupURLs |
| Type | String |
| Value | <enabled/><data value='1http://www.bing.com'/>For multiple list items: <enabled/><data value='1http://www.bing.com2http://www.microsoft.com'/> |
Edge For Win 7 64
ExtensionInstallForcelist:
| Field | Value |
|---|---|
| Name | Microsoft Edge: ExtensionInstallForcelist |
| OMA-URI | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~Extensions/ExtensionInstallForcelist |
| Type | String |
| Value | <enabled/><data value='1gbchcmhmhahfdphkhkmpfmihenigjmpp;https://extensionwebstorebase.edgesv.net/v1/crx'/> |
Dictionary and String data type example
ProxyMode:
| Field | Value |
|---|---|
| Name | Microsoft Edge: ProxyMode |
| OMA-URI | ./Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~ProxyMode/ProxyMode |
| Type | String |
| Value | <enabled/><data value='auto_detect'/> |
Configure Microsoft Edge in Intune using ADMX ingestion
The recommended way to configure Microsoft Edge with Microsoft Intune is to use the Administrative Templates profile as described in Configure Microsoft Edge policy settings with Microsoft Intune. If you want to evaluate a policy that is currently not available in the Microsoft Edge Administrative Templates in Intune you can configure Microsoft Edge using custom settings for Windows 10 devices in Intune.
This section describes how to:
Important
As a best practice, don’t use a custom OMA-URI profile and an Administration templates profile to configure the same Microsoft Edge setting in Intune. If you deploy the same policy using both a custom OMA-URI and an Administrative template profile, but with different values, users will get unpredictable results. We strongly recommend removing your OMA-URI profile before using an Administration templates profile.
Ingest the Microsoft Edge ADMX file into Intune
This section describes how to ingest the Microsoft Edge administrative template (msedge.admx file) into Intune.
Warning
Don't modify the ADMX file before ingesting the file.
To ingest the ADMX file, follow these steps:
Download the Microsoft Edge policy templates file (MicrosoftEdgePolicyTemplates.cab) from the Microsoft Edge Enterprise landing page and extract the contents. The file that you want to ingest is msedge.admx.
Sign in to the Microsoft Azure portal.
Select Intune from All Services, or search for Intune in the portal search box.
From Microsoft Intune - Overview, select Device configuration | Profiles.
On the top command bar, select + Create profile.
Provide the following profile information:
- Name: Enter a descriptive name. For this example, 'Microsoft Edge ADMX ingested configuration'.
- Description: Enter an optional description for the profile.
- Platform: Select 'Windows 10 and later'
- Profile type: Select 'Custom'
On Custom OMA-URI Settings, click Add to add an ADMX ingestion.
On Add Row, provide the following information:
Name: Enter a descriptive name. For this example, use 'Microsoft Edge ADMX ingestion'.
Description: Enter an optional description for the setting.
OMA-URI: Enter './Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/Edge/Policy/EdgeAdmx'
Data type: Select 'String'
Value: This input area appears after you select the Data type. Open the msedge.admx file from the Microsoft Edge policy templates file you extracted in step 1. Copy ALL the text from the msedge.admx file and paste it in the Value text area shown in the following screenshot.
Click OK.
On Custom OMA-URI Settings, click OK.
On Create profile, click Create. The next screenshot shows information about the newly created profile.
Set a policy using custom OMA-URI in Intune
Note
Before using the steps in this section you must complete the steps described in Ingest the Microsoft Edge ADMX file into Intune.
Sign in to the Microsoft Azure portal.
Select Intune from All Services, or search for Intune in the portal search box.
Go to Intune>Device configuration>Profiles.
Select the 'Microsoft Edge ADMX ingested configuration' profile or the name you used for the profile.
To add Microsoft Edge policy settings, you have to open Custom OMA-URI Settings. Under Manage, click Properties, and then click Settings.
On Custom OMA-URI Settings, click Add.
On Add Row, provide the following information:
Name: Enter a descriptive name. We suggest using the policy name you want to configure. For this example, use 'ShowHomeButton'.
Description (Optional): Enter a description for the setting.
OMA-URI: Enter the OMA-URI for the policy. Using the for 'ShowHomeButton' policy as an example, use this string: './Device/Vendor/MSFT/Policy/Config/Edge~Policy~microsoft_edge~Startup/ShowHomeButton'
Data type: Select the policy settings data type. For the 'ShowHomeButton' policy, use 'String'
Value: Enter the setting that you want to configure for the policy. For 'ShowHomeButton' example, enter '<enabled/>'. The following screenshot shows the settings for configuring a policy.
Click OK.
On Custom OMA-URI Settings, click OK.
On the 'Microsoft Edge ADMX ingested configuration - Properties' profile (or the name you used), click Save.
After the profile is created and the properties set, you have to assign the profile in Microsoft Intune.
Confirm that the policy was set
Use the following steps to confirm that the Microsoft Edge policy is using the profile you created. (Give Microsoft Intune time to propagate the policy to a device you assigned in the 'Microsoft Edge ADMX ingested configuration' profile example.)
Download Edge For Windows 7
- Open Microsoft Edge and go to edge://policy.
- On the Policies page, see if the policy you set in the profile is listed.
- If your policy isn't shown, see Diagnose MDM failures in Windows 10 or Troubleshoot a policy setting.
Troubleshoot a policy setting
If a Microsoft Edge policy isn’t taking effect, try the following steps:
Open the edge://policy page on the target device (a device you assigned the profile to in Microsoft Intune) and search for the policy. If the policy isn’t on the edge://policy page, try the following:
- Check that the policy is in the registry and is correct. On the target device open the Windows 10 Registry Editor (Windows key + r, enter “regedit” and then press Enter.) Check that the policy is correctly defined in the SoftwarePolicies MicrosoftEdge path. If you don’t find the policy in the expected path, then the policy wasn’t pushed to the device correctly.
- Check that the OMA-URI path is correct, and the value is a valid XML string. If either of these are incorrect the policy won’t be pushed to the target device.
For more trouble shooting tips, see Set up Microsoft Intune and Sync devices.
See also