Open in the explorer

List of URL patterns where developer tools are allowed

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Microsoft Edge User Configuration › Policies › Administrative Templates › Microsoft Edge
Supported on
Microsoft Edge version 148, Windows 7 or later
ADMX file
msedge.admx
Internal name
msedge/DeveloperToolsAvailabilityAllowlist

Explanation

This policy controls where developer tools can be used in Microsoft Edge by specifying an allowlist of URL patterns.

Developer tools availability is evaluated for each target being inspected. URL patterns are matched against the target's URL, such as a page, a subframe represented by a separate target, an extension, or a web application. Frames that share a target follow that target's policy result.

If you configure this policy and don't configure the 'DeveloperToolsAvailabilityBlocklist' (List of URL patterns for which developer tools are blocked) policy, developer tools are available only for targets whose URLs match a pattern in this allowlist. If a target's URL doesn't match, developer tools are blocked for that target. For example, a subframe represented by a separate target can't be inspected if its URL isn't on the allowlist, but an allowlisted main-page target remains inspectable. For information about the URL format, see https://go.microsoft.com/fwlink/?linkid=2095322.

If you configure both this policy and the 'DeveloperToolsAvailabilityBlocklist' policy, this allowlist takes precedence. A target whose URL matches this allowlist is allowed even if it also matches the blocklist. A target whose URL matches the blocklist but not this allowlist is blocked. A target whose URL matches neither list is governed by the 'DeveloperToolsAvailability' (Control where developer tools can be used) policy.

If you disable or don't configure this policy, developer tools availability is determined by the 'DeveloperToolsAvailabilityBlocklist' and 'DeveloperToolsAvailability' policies.

This policy applies to developer tools, direct Chrome DevTools Protocol (CDP) connections (for example, using --remote-debugging-port or --remote-debugging-pipe), and CDP connections through the chrome.debugger extension API. The 'RemoteDebuggingAllowed' (Allow remote debugging) policy controls whether remote debugging can start. When remote debugging is allowed, this policy still restricts which targets can be inspected.

Blanket host wildcards (that is, "*" or "[*]") aren't allowed. To enable developer tools globally, use the 'DeveloperToolsAvailability' policy.

This policy supports up to 1,000 entries.

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

Example value:

contoso.com
https://ssl.server.com
contoso.com/good_path
https://server.contoso.com:8080/path
.exact.hostname.com
file://*

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge
HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge
Value name
not defined in the ADMX

Enable / disable values: not defined in the ADMX (see the options below).

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Computer (HKLM)

Enable

# Enable: msedge/DeveloperToolsAvailabilityAllowlist
$k = 'HKLM:\Software\Policies\Microsoft\Edge\DeveloperToolsAvailabilityAllowlist'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
# List of URL patterns where developer tools are allowed
# Non-additive list: existing values of the key are cleared first
if (Test-Path -Path $k) { (Get-Item -Path $k).Property | ForEach-Object { Remove-ItemProperty -Path $k -Name ([WildcardPattern]::Escape($_)) -ErrorAction SilentlyContinue } }
$values = @('<value1>', '<value2>')  # Replace the values with your own
$i = 1
foreach ($v in $values) { Set-ItemProperty -Path $k -Name ('' + $i) -Value $v -Type String; $i++ }

Disable

# Disable: msedge/DeveloperToolsAvailabilityAllowlist
# No value is written in the "Disabled" state (nothing defined in the ADMX)

Revert to "Not configured"

# Revert to "Not configured": msedge/DeveloperToolsAvailabilityAllowlist
$k = 'HKLM:\Software\Policies\Microsoft\Edge\DeveloperToolsAvailabilityAllowlist'
Remove-Item -Path $k -Recurse -Force -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Options (1)

LabelControlRegistry valueREG typeConstraints / details
List of URL patterns where developer tools are allowedDeveloperToolsAvailabilityAllowlistDescList (table)listSoftware\Policies\Microsoft\Edge\DeveloperToolsAvailabilityAllowlistValues named “” + numberREG_SZ (values under the key)

Application

Microsoft Edge (+ Edge Update, WebView2) (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.