DeveloperToolsAvailability

Control where developer tools can be used

Supported versions

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

Description

Controls whether users can access developer tools in Microsoft Edge.

This policy also applies to direct Chrome DevTools Protocol (CDP) connections (for example, connections that use --remote-debugging-port or --remote-debugging-pipe) and CDP connections through the chrome.debugger extension API. The RemoteDebuggingAllowed policy controls whether users can use remote debugging. When remote debugging is allowed, this policy still controls which targets can be inspected.

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 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 policy is configured.

The DeveloperToolsAvailabilityAllowlist and DeveloperToolsAvailabilityBlocklist policies take precedence over this policy. Developer tools availability is determined by the first applicable rule below:

  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. Otherwise, if neither URL-list policy is configured, or if a URL matches neither list, this policy (DeveloperToolsAvailability) applies as the fallback.

On Android, this policy controls inspection of targets through remote debugging. It does not enable on-device developer tools.

Policy options mapping:

  • DeveloperToolsDisallowedForForceInstalledExtensions (0) = Block Edge DevTools on extensions installed by enterprise policy, allow in other contexts

  • DeveloperToolsAllowed (1) = Allow using Edge DevTools

  • DeveloperToolsDisallowed (2) = Don't allow using Edge DevTools

Use the preceding information when configuring this policy.

Policy options mapping:

Use this information when configuring this policy.

  • DeveloperToolsDisallowedForForceInstalledExtensions (0) = Block Edge DevTools on extensions installed by enterprise policy, allow in other contexts
  • DeveloperToolsAllowed (1) = Allow using Edge DevTools
  • DeveloperToolsDisallowed (2) = Don't allow using Edge DevTools

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 Edge DevTools

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>

Android information and settings

  • Preference Key name: DeveloperToolsAvailability
  • Example value:
2

See also

  • Last updated on