The Legacy Web Application Dilemma
Modern enterprises operate predominantly in the cloud, utilizing fast, secure browsers like Google Chrome for 99% of their daily workflows. However, in heavily regulated industries (like healthcare, finance, or manufacturing), there is almost always a critical, decade-old internal web application that simply refuses to die.
This legacy application might require Java Applets, ActiveX controls, or Silverlight—technologies that modern Chrome brutally rejects for security reasons. Historically, IT administrators were forced to tell users, “Use Chrome for the internet, but if you need to open the HR portal, you must manually open Internet Explorer.”
This dual-browser workflow is frustrating for users and generates constant helpdesk tickets when employees inevitably attempt to open the legacy portal in Chrome and receive rendering errors.
With Internet Explorer officially dead and replaced by Microsoft Edge, Google created a definitive solution: Legacy Browser Support (LBS). By configuring LBS via enterprise policies, administrators can force Google Chrome to act as an intelligent router. When a user types the URL of the legacy application into Chrome, Chrome instantly realizes the site requires archaic technology. Chrome autonomously launches Microsoft Edge (configured in IE Mode) in the background, seamlessly handing the URL off without the user having to manually switch applications.
Step 1: The Architectural Requirements
Legacy Browser Support is not a simple toggle switch. It requires a highly orchestrated interplay between Google Chrome, Microsoft Edge, and Active Directory Group Policy (or Google Cloud Management).
- Google Chrome: You must have the Chrome Enterprise package installed.
- Legacy Browser Support Extension: Historically, this was a separate extension you had to push via GPO. In modern versions of Chrome (Version 74 and later), LBS is natively baked directly into the core browser code. You do not need to deploy a separate extension.
- Microsoft Edge (IE Mode): The destination browser (Edge) must be independently configured via Group Policy to actually support Internet Explorer mode. LBS simply acts as the bridge; Edge must do the heavy lifting of rendering the ActiveX controls.
Step 2: Deploying the Chrome ADMX Templates
To orchestrate the handoff, you must configure Chrome’s internal routing table using Active Directory Group Policy.
Download the latest Google Chrome Enterprise ADMX templates from the Google Enterprise portal and copy them into your Domain Controller’s Central Store (\\yourdomain.local\SYSVOL\yourdomain.local\Policies\PolicyDefinitions).
Open the Group Policy Management Console, create a new GPO named “Chrome_Legacy_Browser_Support”, and navigate to:
Computer Configuration > Policies > Administrative Templates > Google > Google Chrome > Legacy Browser Support
Step 3: Configuring the Alternative Browser
You must explicitly tell Chrome which browser to launch when it intercepts a legacy URL.
Locate the policy named Alternative browser to launch for configured websites.
Enable the policy. In the text box, you specify the exact executable path of Microsoft Edge. However, because Edge is often installed in varying locations depending on the OS architecture (32-bit vs. 64-bit), you should use environment variables.
Set the string to: ${ie}
(Note: While the variable is named ${ie} for historical reasons, on modern Windows 10/11 machines, Chrome interprets this as the system default legacy browser, which is now Microsoft Edge operating in IE Mode).
Step 4: Building the Site List (The Handoff Trigger)
This is the most critical step. You must give Chrome the exact list of URLs that trigger the autonomous handoff.
Locate the policy named Websites to open in the alternative browser.
Enable the policy and click Show. Here, you define the routing rules using a very specific syntax.
- To redirect an exact URL:
http://legacy.corp.local/hr-portal/ - To redirect an entire domain (including all subdomains):
corp.local - To redirect based on a specific path, regardless of the domain:
*/activex-plugin/*
If an employee types http://legacy.corp.local/hr-portal/ into their Chrome address bar and presses Enter, Chrome intercepts the request. The tab instantly displays a brief transition screen stating “Opening in Internet Explorer Mode”, and Microsoft Edge launches over the top of Chrome, loading the legacy site perfectly.
Step 5: The Reverse Handoff (Return to Chrome)
A highly polished deployment doesn’t just hand users off to the legacy browser; it prevents them from staying there.
If a user is inside the Edge IE Mode window and decides to check their Gmail, they might type gmail.com into the Edge address bar. You do not want them browsing the modern web in a legacy rendering engine.
You must configure the reverse routing.
In the same GPO folder, locate the policy named Websites that should not open in the alternative browser.
Enable it and add the wildcard character: *
This creates a strict architectural boundary. If a user is in Edge and clicks a link that points to anything other than the specific URLs you defined in Step 4, Edge will instantly hand the URL back to Chrome, ensuring the user is forced back into the secure, modern browser for all standard internet traffic.
Step 6: Troubleshooting the Handoff
If you force a group policy update (gpupdate /force) and the handoff fails, do not blindly edit the GPO. You must verify that Chrome successfully received the routing table.
On the affected client machine, open Google Chrome and navigate to:
chrome://policyLook for the BrowserSwitcherUrlList policy. If it is empty, the GPO failed to apply. If the URLs are present, navigate to the dedicated LBS diagnostic page:
chrome://browser-switch/internalsThis hidden page will show you the exact XML rules Chrome is parsing, and allows you to type a URL into a test box to mathematically verify whether Chrome will route it to the alternative browser or keep it in the native engine, allowing you to instantly debug complex wildcard routing rules.
Conclusion
Forcing employees to manually juggle multiple web browsers to access legacy infrastructure destroys productivity and guarantees helpdesk calls. By configuring Google Chrome Enterprise Legacy Browser Support, IT administrators construct an intelligent, invisible routing layer. Chrome acts as the secure primary portal for all traffic, autonomously delegating specific, archaic URLs to Microsoft Edge IE Mode only when mathematically required, bridging the gap between legacy code and modern security standards.