Control where developer tools can be used

Supported on: Microsoft Edge version 77, Windows 7 or later

Registry

HKLM Software\Policies\Microsoft\Edge
HKCU Software\Policies\Microsoft\Edge

Options

DeveloperToolsAvailability enum
  • Block the developer tools on extensions installed by enterprise policy, allow in other contexts -> 0
  • Allow using the developer tools -> 1
  • Don't allow using the developer tools -> 2

Description

Controls whether users can access developer tools in Microsoft Edge. If you set this policy to 'DeveloperToolsDisallowedForForceInstalledExtensions' (default), users can access developer tools and the JavaScript console, except in the context of extensions installed by enterprise policy. If you set this policy to 'DeveloperToolsAllowed', users can access developer tools and the JavaScript console in all contexts, including extensions installed by enterprise policy. If you set this policy to 'DeveloperToolsDisallowed', users cannot access developer tools or inspect website elements. Keyboard shortcuts, menu options, and context menu entries that open developer tools or the JavaScript console are disabled. As of version 99, this policy also controls access to the 'View page source' feature. If you set this policy to 'DeveloperToolsDisallowed', users cannot view page source through keyboard shortcuts or the context menu. To fully block source viewing, add 'view-source:*' to the 'URLBlocklist' (Block access to a list of URLs) policy. As of version 119, this policy also controls whether developer mode for Isolated Web Apps can be enabled. As of version 128, this policy does not control developer mode on the extensions page if the 'ExtensionDeveloperModeSettings' (Control the availability of developer mode on extensions page) policy is configured. Developer tools availability is determined in the following order of precedence: 1. If a URL matches a pattern in 'DeveloperToolsAvailabilityAllowlist' (List of URL patterns for which developer tools are allowed to be opened), developer tools are allowed. 2. If the allowlist is configured and the blocklist is not, URLs not on the allowlist are blocked. 3. If a URL matches a pattern in 'DeveloperToolsAvailabilityBlocklist' (List of URL patterns for which developer tools are blocked), developer tools are blocked. 4. If a URL is not covered by either list, this policy ('DeveloperToolsAvailability' (Control where developer tools can be used)) applies. Policy options mapping: * DeveloperToolsDisallowedForForceInstalledExtensions (0) = Block the developer tools on extensions installed by enterprise policy, allow in other contexts * DeveloperToolsAllowed (1) = Allow using the developer tools * DeveloperToolsDisallowed (2) = Don't allow using the developer tools Use the preceding information when configuring this policy.