With the rise of Microsoft Edge (particularly the Chromium-based version released in 2020), the concept of a “trusted site” has fundamentally fractured. It is no longer a single toggle or a zone-based security model. Instead, Edge now manages trust through a decentralized, granular, and context-aware system of permissions, enterprise policies, and smart screen heuristics.
Thus, “adding a trusted site” in modern Edge is less about securing the browser itself and more about enabling interoperability with dinosaur-era corporate applications. For modern websites rendered in Edge’s default Chromium engine, trust is not binary. There is no global “trust this domain” switch. Instead, trust is broken down into discrete capabilities. This is the Permissions API standard. edge add trusted sites
To manage these, Edge provides edge://settings/content —a comprehensive dashboard where you can view and revoke permissions on a per-site basis. This is the modern equivalent of the Trusted Sites list, but far more surgical. In an enterprise environment, “adding trusted sites” is rarely a user decision. It’s a matter of Group Policy Objects (GPO) or Microsoft Intune. Microsoft provides over 3,000 policies for Edge, but three categories directly address site trust: 1. Legacy Zone Mapping (for IE mode) Administrators use the InternetExplorerIntegrationSiteList policy to point Edge to an XML file that maps URLs to IE mode and, subsequently, to specific security zones. A typical entry: With the rise of Microsoft Edge (particularly the
Microsoft Edge (Chromium) does not use these zones for its own rendering engine. However, if your organization uses IE mode within Edge (a feature designed to run legacy IE-dependent apps), then the Trusted Sites zone comes roaring back to life. In IE mode, Edge spins up the Trident MSHTML engine, and that engine does respect the classic zone settings. Thus, “adding a trusted site” in modern Edge
With the rise of Microsoft Edge (particularly the Chromium-based version released in 2020), the concept of a “trusted site” has fundamentally fractured. It is no longer a single toggle or a zone-based security model. Instead, Edge now manages trust through a decentralized, granular, and context-aware system of permissions, enterprise policies, and smart screen heuristics.
Thus, “adding a trusted site” in modern Edge is less about securing the browser itself and more about enabling interoperability with dinosaur-era corporate applications. For modern websites rendered in Edge’s default Chromium engine, trust is not binary. There is no global “trust this domain” switch. Instead, trust is broken down into discrete capabilities. This is the Permissions API standard.
To manage these, Edge provides edge://settings/content —a comprehensive dashboard where you can view and revoke permissions on a per-site basis. This is the modern equivalent of the Trusted Sites list, but far more surgical. In an enterprise environment, “adding trusted sites” is rarely a user decision. It’s a matter of Group Policy Objects (GPO) or Microsoft Intune. Microsoft provides over 3,000 policies for Edge, but three categories directly address site trust: 1. Legacy Zone Mapping (for IE mode) Administrators use the InternetExplorerIntegrationSiteList policy to point Edge to an XML file that maps URLs to IE mode and, subsequently, to specific security zones. A typical entry:
Microsoft Edge (Chromium) does not use these zones for its own rendering engine. However, if your organization uses IE mode within Edge (a feature designed to run legacy IE-dependent apps), then the Trusted Sites zone comes roaring back to life. In IE mode, Edge spins up the Trident MSHTML engine, and that engine does respect the classic zone settings.
