Share via

DeveloperToolsAvailability

Control where developer tools can be used

Supported versions

  • Windows: ≥ 77
  • macOS: ≥ 77
  • Android: Not supported
  • iOS: Not supported

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 Microsoft Edge 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 policy.

As of Microsoft Edge version 119, this policy also controls whether developer mode for Isolated Web Apps can be enabled.

As of Microsoft Edge version 128, this policy does not control developer mode on the extensions page if the ExtensionDeveloperModeSettings policy is configured.

Developer tools availability is determined in the following order of precedence:

  1. If a URL matches a pattern in DeveloperToolsAvailabilityAllowlist, 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, developer tools are blocked.
  4. If a URL is not covered by either list, this policy (DeveloperToolsAvailability) 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.

Policy options mapping:

Use this information when configuring this policy.

  • 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

Supported features

  • Can be mandatory: Yes
  • Can be recommended: No
  • Dynamic Policy Refresh: Yes
  • Per Profile: Yes
  • Applies to a profile that is signed in with a Microsoft account: No

Data type

  • Integer

Windows information and settings

Group Policy (ADMX) info

  • GP unique name: DeveloperToolsAvailability
  • GP name: Control where developer tools can be used
  • GP path (Mandatory): Administrative Templates/Microsoft Edge
  • GP path (Recommended): N/A
  • GP ADMX file name: MSEdge.admx

Example value

Don't allow using the developer tools

Registry settings

  • Path (Mandatory): SOFTWARE\Policies\Microsoft\Edge
  • Path (Recommended): N/A
  • Value name: DeveloperToolsAvailability
  • Value type: REG_DWORD

Example registry value

0x00000002

Mac information and settings

  • Preference Key name: DeveloperToolsAvailability
  • Example value:
<integer>2</integer>

See also

  • Last updated on