At first glance, the phrase “add trusted sites” feels like a relic. For decades, system administrators and power users navigated the labyrinthine Internet Options control panel in Internet Explorer (IE) to designate specific URLs as “trusted.” The goal was simple: lower security barriers for known, safe internal or corporate sites while maintaining high walls for the rest of the web.
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: At first glance, the phrase “add trusted sites”