List of URL patterns for which developer tools are blocked
Verified with Microsoft Edge 157.0.4341.60 — updated on October 22, 2026 Supported on: Microsoft Edge version 148, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge User Configuration\Administrative Templates\Microsoft Edge Registry
Software\Policies\Microsoft\Edge Software\Policies\Microsoft\Edge Description
This policy specifies URL patterns where developer tools are blocked. For information about the URL format, see https://go.microsoft.com/fwlink/?linkid=2095322. 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 'DeveloperToolsAvailabilityAllowlist' (List of URL patterns where developer tools are allowed) policy, developer tools are blocked for targets whose URLs match a pattern in this blocklist. If a target's URL doesn't match, availability is determined by the 'DeveloperToolsAvailability' (Control where developer tools can be used) policy. For example, a subframe represented by a separate target can't be inspected if its URL matches this blocklist, while the main-page target remains inspectable if its URL isn't blocklisted and the fallback policy allows inspection. If you configure both this policy and the 'DeveloperToolsAvailabilityAllowlist' policy, the allowlist takes precedence. A target whose URL matches the allowlist is allowed, even if it also matches this policy. A target whose URL matches this policy but not the allowlist is blocked. If a target's URL matches neither list, the 'DeveloperToolsAvailability' policy determines availability. If you disable or don't configure this policy, developer tools availability is determined by the 'DeveloperToolsAvailabilityAllowlist' 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. 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: https://contoso.com contoso.com https://ssl.server.com contoso.com/bad_path https://server.contoso.com:8080/path .exact.hostname.com * file://*
Export Builder
BETAConfigure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.
These exports write the registry — this is not a managed GPO. ⓘ
Applying both scopes creates an ambiguous configuration (computer takes precedence over user). Only do this intentionally.
.reg file
Windows Registry Editor Version 5.00
; Exported from gporais.com
; Policy: List of URL patterns for which developer tools are blocked
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 148, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\DeveloperToolsAvailabilityBlocklist]
; List values: enter one value per line in the builder UI. More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: List of URL patterns for which developer tools are blocked
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 148, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\DeveloperToolsAvailabilityBlocklist'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI. Intune XML
No direct Policy CSP / OMA-URI mapping for this policy. Use the Intune Remediation tab, or ingest the ADMX in Intune. Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: List of URL patterns for which developer tools are blocked
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 148, Windows 7 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
# HKLM:\Software\Policies\Microsoft\Edge\DeveloperToolsAvailabilityBlocklist: List values: enter one value per line in the builder UI.
# No testable registry values are available for this state.
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: List of URL patterns for which developer tools are blocked
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 148, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\DeveloperToolsAvailabilityBlocklist'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI. SCCM scripts
# Exported from gporais.com
# Policy: List of URL patterns for which developer tools are blocked
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 148, Windows 7 or later
# SCCM Configuration Item guidance:
# Create a Configuration Item of type "Setting: Script".
# Discovery script: use the Detection script below.
# Remediation script: use the Remediation script below.
# Compliance rule: the Discovery script output equals 'Compliant'.
# === Detection script ===
# Exported from gporais.com
# Policy: List of URL patterns for which developer tools are blocked
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 148, Windows 7 or later
function Test-RegistryValue {
param(
[Parameter(Mandatory = $true)][string]$Path,
[Parameter(Mandatory = $true)][string]$Name,
[object]$Expected,
[ValidateSet('String', 'DWord', 'MultiString')][string]$Kind = 'String',
[switch]$Absent
)
try {
$item = Get-ItemProperty -LiteralPath $Path -Name $Name -ErrorAction Stop
} catch {
return $Absent.IsPresent
}
if ($Absent.IsPresent) { return $false }
$actual = $item.$Name
if ($Kind -eq 'DWord') { return ([int64]$actual) -eq ([int64]$Expected) }
if ($Kind -eq 'MultiString') {
$actualValues = @($actual)
$expectedValues = @($Expected)
if ($actualValues.Count -ne $expectedValues.Count) { return $false }
for ($i = 0; $i -lt $expectedValues.Count; $i++) {
if ([string]$actualValues[$i] -ne [string]$expectedValues[$i]) { return $false }
}
return $true
}
return [string]$actual -eq [string]$Expected
}
# HKLM:\Software\Policies\Microsoft\Edge\DeveloperToolsAvailabilityBlocklist: List values: enter one value per line in the builder UI.
# No testable registry values are available for this state.
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: List of URL patterns for which developer tools are blocked
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 148, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\DeveloperToolsAvailabilityBlocklist'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI. Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.