Ouvrir dans l'explorateur

Control where developer tools can be used

Cette stratégie n'a pas de traduction française dans les modèles de l'éditeur ; le texte original est en anglais.

Type
Ordinateur et utilisateur
Chemin GPO
Configuration ordinateur › Stratégies › Modèles d'administration › Microsoft Edge Configuration utilisateur › Stratégies › Modèles d'administration › Microsoft Edge EN : Computer Configuration › Policies › Administrative Templates › Microsoft EdgeEN : User Configuration › Policies › Administrative Templates › Microsoft Edge
Pris en charge sur
Microsoft Edge version 77, Windows 7 or later
Fichier ADMX
msedge.admx
Nom interne
msedge/DeveloperToolsAvailability

Explication

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' (Allow remote debugging) 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' (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.

The 'DeveloperToolsAvailabilityAllowlist' (List of URL patterns where developer tools are allowed) and 'DeveloperToolsAvailabilityBlocklist' (List of URL patterns for which developer tools are blocked) 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' (Control where developer tools can be used)) 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.

Registre

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge
HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge
Nom de la valeur
non défini dans l'ADMX

Valeurs d'activation / désactivation : non défini dans l'ADMX (voir les options ci-dessous).

PowerShell

Commandes PowerShell qui écrivent dans le registre ce que la stratégie écrirait. Les valeurs entre chevrons (<…>) sont à remplacer.

Écrire directement dans le registre contourne la stratégie de groupe : si une GPO gère cette valeur, elle sera réécrite au prochain gpupdate ; sinon la valeur reste en place (effet « tatouage »). Préférez une GPO ou, en local, LGPO.exe. Exécutez PowerShell en administrateur pour HKLM. Certaines stratégies demandent un redémarrage ou gpupdate /force.

Ordinateur (HKLM)

Activer

# Activer : msedge/DeveloperToolsAvailability
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# Control where developer tools can be used
# Options possibles :
#   Block Edge DevTools on extensions installed by enterprise policy, allow in other contexts = 0
#   Allow using Edge DevTools = 1
#   Don't allow using Edge DevTools = 2
Set-ItemProperty -Path $k -Name 'DeveloperToolsAvailability' -Value 0 -Type DWord

Désactiver

# Désactiver : msedge/DeveloperToolsAvailability
# Aucune valeur n'est écrite à l'état « Désactivé » (rien de défini dans l'ADMX)

Revenir à « Non configuré »

# Revenir à « Non configuré » : msedge/DeveloperToolsAvailability
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
Remove-ItemProperty -Path $k -Name 'DeveloperToolsAvailability' -ErrorAction SilentlyContinue

Utilisateur (HKCU)

Activer

Désactiver

Revenir à « Non configuré »

Options (1)

LibelléContrôleValeur de registreType REGContraintes / détails
Control where developer tools can be usedDeveloperToolsAvailabilityListe déroulanteenumDeveloperToolsAvailabilityREG_DWORD
LibelléValeur
Block Edge DevTools on extensions installed by enterprise policy, allow in other contextsREG_DWORD = 0
Allow using Edge DevToolsREG_DWORD = 1
Don't allow using Edge DevToolsREG_DWORD = 2

Application

Microsoft Edge (+ Edge Update, WebView2) (Microsoft) — modèles de novembre 2026

Modèles officiels téléchargés le 12 novembre 2026.