Explicitly allowed network ports
Verified with Microsoft Edge 152.0.4191.53 — updated on July 10, 2026
Supported on: Microsoft Edge version 91, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge User Configuration\Administrative Templates\Microsoft Edge Description
There's a list of restricted ports built into Microsoft Edge. Connections to these ports fail. This policy allows bypassing that list. The set of ports is defined as a comma-separated list that outgoing connections should be permitted on. Ports are restricted to prevent Microsoft Edge from being used as a vector to exploit various network vulnerabilities. Setting this policy exposes your network to attacks. This policy is intended as a temporary workaround for error code "ERR_UNSAFE_PORT" while migrating a service running on a blocked port to a standard port (for example, port 80 or 443). Malicious websites can easily detect that this policy is set. They also detect the ports for which this policy is set, and then they use that information to target attacks. Each port listed in this policy is labeled with a date until which that port can be unblocked. After that date, the port is restricted, regardless of whether it's specified by the value of this policy. Leaving the value empty or unset means that all restricted ports are blocked. Invalid port values set through this policy are ignored while valid ones are still applied. This policy overrides the "--explicitly-allowed-ports" command-line option. Policy options mapping: * 554 (554) = port 554 (can be unblocked until 2021/10/15) * 10080 (10080) = port 10080 (can be unblocked until 2022/04/01) * 6566 (6566) = port 6566 (can be unblocked until 2021/10/15) * 989 (989) = port 989 (can be unblocked until 2022/02/01) * 990 (990) = port 990 (can be unblocked until 2022/02/01) Use the preceding information when configuring this policy. Example value: 10080
Registry
Software\Policies\Microsoft\Edge Software\Policies\Microsoft\Edge 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: Explicitly allowed network ports
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 91, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\ExplicitlyAllowedNetworkPorts]
; List values: enter one value per line in the builder UI.More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Explicitly allowed network ports
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 91, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\ExplicitlyAllowedNetworkPorts'
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: Explicitly allowed network ports
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 91, 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\ExplicitlyAllowedNetworkPorts: 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: Explicitly allowed network ports
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 91, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\ExplicitlyAllowedNetworkPorts'
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: Explicitly allowed network ports
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 91, 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: Explicitly allowed network ports
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 91, 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\ExplicitlyAllowedNetworkPorts: 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: Explicitly allowed network ports
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 91, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\ExplicitlyAllowedNetworkPorts'
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.