en-US edge computer user

Specifies whether to allow websites to make requests to any network endpoint in an insecure manner. (obsolete)

Verified with Microsoft Edge 152.0.4191.53 — updated on July 10, 2026

Microsoft Edge 152.0.4191.53

Supported on: Microsoft Edge version 92-137, Windows 7 or later

Path in the GPO console

Computer Configuration\Administrative Templates\Microsoft Edge\Private Network Request Settings

Description

OBSOLETE: This policy is obsolete and doesn't work after Microsoft Edge 137. Controls whether websites are allowed to make requests to more-private network endpoints. When this policy is enabled, all Private Network Access checks are disabled for all origins. This may allow attackers to perform cross-site request forgery (CSRF) attacks on private network servers. When this policy is disabled or not configured, the default behavior for requests to more-private network endpoints depend on the user's personal configuration for the BlockInsecurePrivateNetworkRequests, PrivateNetworkAccessSendPreflights, and PrivateNetworkAccessRespectPreflightResults feature flags. These flags may be controlled by experimentation or set via the command line. This policy relates to the Private Network Access specification. See https://wicg.github.io/private-network-access/ for more details. A network endpoint is more private than another if: 1) Its IP address is localhost and the other isn't. 2) Its IP address is private and the other is public. In the future, depending on spec evolution, this policy might apply to all cross-origin requests directed at private IPs or localhost. When this policy enabled, websites are allowed to make requests to any network endpoint, subject to other cross-origin checks. This policy is obsolete. The previous blanket override has been replaced by the permission-based Local Network Access model, which blocks cross-space requests until users grant explicit consent.

Registry

HKLM Software\Policies\Microsoft\Edge
HKCU Software\Policies\Microsoft\Edge

Value name: InsecurePrivateNetworkRequestsAllowed

Enabled: InsecurePrivateNetworkRequestsAllowed = 1

Disabled: InsecurePrivateNetworkRequestsAllowed = 0

Export Builder

BETA

Configure 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.

Scope

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: Specifies whether to allow websites to make requests to any network endpoint in an insecure manner. (obsolete)
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 92-137, Windows 7 or later

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]
"InsecurePrivateNetworkRequestsAllowed"=dword:00000001
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Specifies whether to allow websites to make requests to any network endpoint in an insecure manner. (obsolete)
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 92-137, Windows 7 or later

$path = 'HKLM:\Software\Policies\Microsoft\Edge'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'InsecurePrivateNetworkRequestsAllowed' -Value 1 -Type DWord

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview