Allow JavaScript to use JIT on these sites
Verified with Microsoft Edge 157.0.4341.60 — updated on November 5, 2026 Supported on: Microsoft Edge version 93, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge\Content settings User Configuration\Administrative Templates\Microsoft Edge\Content settings Registry
Software\Policies\Microsoft\Edge Software\Policies\Microsoft\Edge Description
Allows you to set a list of site URL patterns that specify sites that are allowed to run JavaScript with JIT (Just In Time) compiler enabled. For detailed information on valid site URL patterns, see https://go.microsoft.com/fwlink/?linkid=2095322. Wildcards, *, are allowed. You can set policy exceptions for specific subdomains and entire sites. For example, a policy set only for subdomain.contoso.com applies to subdomain.contoso.com without affecting contoso.com. In some cases, when a subdomain can't be isolated from its parent site, it may inherit the policy set on the parent site. Exceptions also may not take effect for frames loaded in an existing tab until the site is opened in a new tab. On low-memory Android devices, site-specific exceptions may not be enforced. Instead, sites use the policy from 'DefaultJavaScriptJitSetting' (Control use of JavaScript JIT), if set, or default to the profile's JavaScript JIT setting. To enforce exceptions, Microsoft Edge may place sites or subdomains with settings that differ from the default in dedicated processes. This behavior can increase memory usage, especially on Android devices or when a wildcard pattern matches many subdomains, because each matching origin may be isolated separately. Isolated subdomains also can't use document.domain to access their parent site. Note: In version 155 and earlier, policy exceptions were enforced only at the site level (eTLD+1). A policy set only for subdomain.contoso.com didn't take effect, even for subdomain.contoso.com. The policy had to be set on contoso.com to apply to both contoso.com and subdomain.contoso.com. This policy applies on a frame-by-frame basis and isn't based only on the top-level origin URL. For example, if contoso.com is listed in the 'JavaScriptJitAllowedForSites' (Allow JavaScript to use JIT on these sites) policy, but contoso.com loads a frame that contains fabrikam.com, contoso.com has JavaScript JIT enabled. However, fabrikam.com uses the policy from 'DefaultJavaScriptJitSetting', if set, or defaults to JavaScript JIT enabled. Blocklist entries have higher priority than allowlist entries, and allowlist entries have higher priority than the configured default value. If you don't configure this policy for a site, the policy from 'DefaultJavaScriptJitSetting' applies to the site, if set. Otherwise, JavaScript JIT is enabled for the site. Example value: [*.]example.edu
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: Allow JavaScript to use JIT on these sites
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 93, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\JavaScriptJitAllowedForSites]
; List values: enter one value per line in the builder UI. More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Allow JavaScript to use JIT on these sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 93, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\JavaScriptJitAllowedForSites'
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: Allow JavaScript to use JIT on these sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 93, 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\JavaScriptJitAllowedForSites: 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: Allow JavaScript to use JIT on these sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 93, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\JavaScriptJitAllowedForSites'
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: Allow JavaScript to use JIT on these sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 93, 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: Allow JavaScript to use JIT on these sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 93, 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\JavaScriptJitAllowedForSites: 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: Allow JavaScript to use JIT on these sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 93, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\JavaScriptJitAllowedForSites'
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.