Modern web browsers are designed to actively warn users when they navigate to a website or internal resource that is not secured with HTTPS. Microsoft Edge will display prominent “Not Secure” badges in the address bar or even full-page interstitial warnings for insecure origins. While this is critical for protecting general consumers from phishing and man-in-the-middle attacks on the public internet, it can be incredibly disruptive in highly controlled, isolated enterprise environments. If your organization relies on legacy internal applications, IoT device management interfaces, or testing servers that operate strictly over HTTP within a secure intranet, these constant warnings train users to suffer from “warning fatigue” and generate unnecessary helpdesk tickets.
This guide explains how to completely disable Insecure Origin Warnings system-wide in Microsoft Edge using Group Policy, allowing users to access legacy internal HTTP sites without being bombarded by security alerts.
Disable Insecure Origin Warnings via Group Policy
To enforce a strict policy that suppresses these specific UI warnings without breaking the browser’s ability to actually use HTTP, we must deploy an administrative template. Note that this requires Windows 11 Pro, Enterprise, or Education editions.
- Log into Windows 11 with an Administrator account.
- Press the Windows Key + R to open the Run dialogue box.
- Type
gpedit.mscand press Enter to launch the Local Group Policy Editor. - In the left-hand navigation pane, navigate precisely to this path:
Computer Configuration > Administrative Templates > Microsoft Edge - In the right-hand pane, locate the policy named Prevent rendering of insecure content warnings (or similar phrasing depending on your exact ADMX version; you may also need to configure Insecure origins treated as secure to whitelist specific internal IPs/domains).
- For a global suppression (if the specific global policy is available in your template), double-click it and select Enabled.
- Alternatively (and more securely): Locate the policy Insecure origins treated as secure, enable it, and input your specific intranet subnets (e.g.,
http://10.0.0.0/8) so only internal HTTP traffic bypasses the warning. - Click Apply, then click OK.
Verify the Configuration Lockdown
Group Policy changes require the browser to read the registry upon its next launch. Close all active instances of Microsoft Edge.
To verify the restriction is active, reopen Microsoft Edge and navigate to a known HTTP-only internal resource (e.g., an older router configuration page). The page will load immediately without throwing a full-screen interstitial warning requiring the user to click “Continue to site (unsafe).” Furthermore, the address bar will simply display the URL without aggressively flashing a red “Not Secure” badge. You have successfully streamlined access to legacy internal infrastructure.