How to Configure Edge Enterprise Site List and Internet Explorer (IE) Mode in Microsoft Edge

While modern web standards have universally converged around Chromium and WebKit rendering engines, enterprise IT environments routinely host legacy internal web applications, intranet portals, and specialized industrial hardware interfaces originally engineered for Internet Explorer. Many of these mission-critical legacy systems depend on deprecated technologies such as ActiveX controls, Java applets, or custom IE Document Modes (such as IE5 Quirks or IE7 mode) that cannot run within modern rendering pipelines.

Following the official retirement of the standalone Internet Explorer 11 desktop application, Microsoft introduced Internet Explorer (IE) Mode inside Microsoft Edge. Powered by the dual-engine architecture of Edge, modern websites render using the high-performance Chromium engine, while designated enterprise URLs automatically invoke the underlying Trident (MSHTML) engine within the same browser tab without user intervention. This technical guide explains how to author Enterprise Mode Site List XML schemas, deploy cloud-managed site lists via the Microsoft 365 admin center, and enforce IE mode using Group Policy.

Dual-Engine Architecture Overview

Understanding how Edge determines rendering pipelines prevents intranet compatibility issues:

Engine	Underlying Runtime	Target Applications
Chromium Engine	Modern V8 JavaScript and Blink renderer.	Standard internet browsing, modern SaaS platforms, HTML5, WebGL.
Trident (MSHTML) Engine	Native mshtml.dll legacy engine.	Enterprise intranet portals requiring ActiveX, VBScript, and legacy Document Modes.

Step 1: Authoring the Enterprise Mode Site List XML

Edge determines which internal web portals run in Trident mode by parsing a standardized XML document (schema v.2):

1. Create an XML file named sites.xml using a text editor.
2. Structure the document adhering to Enterprise Mode schema v.2:

   <site-list version="2">
     <site url="intranet.company.local">
       <compat-mode>IE11</compat-mode>
       <open-in>IE11</open-in>
     </site>
     <site url="erp.legacy.local/accounting">
       <compat-mode>IE7</compat-mode>
       <open-in>IE11</open-in>
     </site>
   </site-list>

3. Tag Attributes Decoded:
   • <compat-mode> — Specifies document emulation mode (IE11, IE8Enterprise, IE7, or Default).
   • <open-in> — Specifies where the URL renders (IE11 renders inside Edge using the Trident tab overlay; msedge forces modern Chromium).
4. Host this XML file on a secure internal web server (e.g., https://config.company.com/sites.xml) or store it in an accessible network UNC share.

Step 2: Configuring IE Mode via Group Policy (GPO)

For domain-joined Windows 11 enterprise workstations, deploy IE Mode using Microsoft Edge administrative templates (ADMX):

1. Open Group Policy Management (gpmc.msc) or the Local Group Policy Editor (gpedit.msc).
2. Navigate to:

   Computer Configuration > Administrative Templates > Microsoft Edge

3. Configure the primary policy: Configure Internet Explorer integration:
   • Double-click the policy, select Enabled.
   • In the dropdown under Options, select Internet Explorer mode.
   • Click OK.
4. Configure the site list pointer: Configure the Enterprise Mode Site List:
   • Double-click the policy, select Enabled.
   • In the Options field, enter the URL or UNC path to your hosted XML file (e.g., https://config.company.com/sites.xml).
   • Click OK.
5. Execute gpupdate /force in an elevated terminal to apply policy changes immediately.

Step 3: Managing Cloud Site Lists via Microsoft 365 Admin Center

Modern cloud-first organizations can bypass on-premises XML hosting by using the Microsoft Edge Cloud Site List service:

1. Sign in to the Microsoft 365 admin center.
2. In the navigation menu, select Settings > Microsoft Edge (or open Microsoft Endpoint Manager).
3. Select Site lists and click Create a site list.
4. Add legacy URLs, choose the desired compatibility mode (e.g., IE8 Enterprise Mode), and click Publish.
5. Copy the unique Site List ID.
6. In your Intune Configuration Profile or Group Policy, configure the policy Configure the Enterprise Mode Cloud Site List and paste the Site List ID. Edge downloads updates directly from Microsoft cloud infrastructure.

Step 4: Testing and Verifying IE Mode in Microsoft Edge

To audit whether Edge properly identifies site lists and applies Trident rendering:

1. Open Microsoft Edge on a client workstation.
2. In the address bar, navigate to:

   edge://compat/enterprise

3. This diagnostic console displays:
   • The current site list version and URL.
   • Click Force update to immediately pull the latest XML without waiting for the default 65-second poll cycle.
4. Navigate to your designated legacy URL (e.g., http://intranet.company.local).
5. Notice the Internet Explorer logo icon appearing on the left side of the Edge address bar. Clicking the icon reveals: “This page is open in Internet Explorer mode” along with compatibility details.

Operational Best Practices

• Keep URLs Specific: Define domain sub-paths (e.g., portal.domain.com/legacyapp/) rather than entire root domains whenever possible, ensuring modern pages within the same domain continue leveraging fast Chromium rendering.
• ActiveX Control Whitelisting: If your legacy application uses ActiveX controls, ensure Windows Defender SmartScreen and user account control policies do not silently block unsigned internal controls on intranet zones.