List of proxy servers that allow all HTTP authentication schemes
Verified with Microsoft Edge 157.0.4341.60 — updated on November 5, 2026 Supported on: Microsoft Edge version 157, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge\HTTP authentication User Configuration\Administrative Templates\Microsoft Edge\HTTP authentication Registry
Software\Policies\Microsoft\Edge Software\Policies\Microsoft\Edge Description
Set this policy to specify which proxy servers allow all the HTTP authentication schemes Microsoft Edge supports, regardless of the 'AuthSchemes' (Supported authentication schemes) policy. Format the proxy server pattern according to the URL blocklist filter format (https://go.microsoft.com/fwlink/?linkid=2095322). Up to 1,000 exceptions can be defined. Invalid patterns are ignored. Wildcards are allowed for the host component (for example, '*:8080' matches all proxies on port 8080). A hostname (for example, 'proxy.example.com') also matches its subdomains. To match a host exactly and exclude its subdomains, prepend it with a dot (for example, '.proxy.example.com'). If you configure this policy with an empty list, no exceptions apply to proxy authentication. If you don't configure this policy, in versions earlier than 161, exceptions in 'AllHttpAuthSchemesAllowedForOrigins' (List of origins that allow all HTTP authentication) also apply to proxy authentication. Starting in version 161, those exceptions don't apply to proxy authentication. For proxy servers that match an applicable exception, all supported HTTP authentication schemes are allowed. For proxy servers that don't match an applicable exception, only the schemes specified in 'AuthSchemes' are supported. If that policy isn't configured, the default schemes are supported instead. Example value: https://proxy.example.com:8443 proxy.example.com:8080 *.corp.example.com:8080
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 proxy servers that allow all HTTP authentication schemes
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 157, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge\AllHttpAuthSchemesAllowedForProxies]
; List values: enter one value per line in the builder UI. More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: List of proxy servers that allow all HTTP authentication schemes
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 157, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\AllHttpAuthSchemesAllowedForProxies'
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 proxy servers that allow all HTTP authentication schemes
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 157, 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\AllHttpAuthSchemesAllowedForProxies: 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 proxy servers that allow all HTTP authentication schemes
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 157, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\AllHttpAuthSchemesAllowedForProxies'
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 proxy servers that allow all HTTP authentication schemes
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 157, 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 proxy servers that allow all HTTP authentication schemes
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 157, 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\AllHttpAuthSchemesAllowedForProxies: 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 proxy servers that allow all HTTP authentication schemes
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 157, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge\AllHttpAuthSchemesAllowedForProxies'
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.