Application Guard Container Proxy
Verified with Microsoft Edge 152.0.4191.53 — updated on July 12, 2026
Supported on: Microsoft Edge version 84, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge\Application Guard settings User Configuration\Administrative Templates\Microsoft Edge\Application Guard settings Description
Configures the proxy settings for Microsoft Edge Application Guard. If you enable this policy, Microsoft Edge Application Guard ignores other sources of proxy configurations. If you don't configure this policy, Microsoft Edge Application Guard uses the proxy configuration of the host. This policy doesn't affect the proxy configuration of Microsoft Edge outside of Application Guard (on the host). The ProxyMode field lets you specify the proxy server used by Microsoft Edge Application Guard. The ProxyPacUrl field is a URL to a proxy.pac file. This policy doesn't affect the proxy configuration of Microsoft Edge outside of Application Guard (on the host). The ProxyMode field lets you specify the proxy server that's used by Microsoft Edge Application Guard. The ProxyPacUrl field is a URL for a proxy .pac file. The ProxyServer field is a URL for the proxy server. If you choose the 'direct' value as 'ProxyMode', all the other fields are ignored. If you choose the 'auto_detect' value as 'ProxyMode', all the other fields are ignored. If you choose the 'fixed_servers' value as 'ProxyMode', the 'ProxyServer' field is used. If you choose the 'pac_script' value as 'ProxyMode', the 'ProxyPacUrl' field is used. For more information about identifying Application Guard traffic via dual proxy, see https://go.microsoft.com/fwlink/?linkid=2134653. Example value: { "ProxyMode": "direct", "ProxyPacUrl": "https://internal.site/example.pac", "ProxyServer": "123.123.123.123:8080" } Compact example value: {"ProxyMode": "direct", "ProxyPacUrl": "https://internal.site/example.pac", "ProxyServer": "123.123.123.123:8080"}
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: Application Guard Container Proxy
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 84, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]
"ApplicationGuardContainerProxy"=""More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Application Guard Container Proxy
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 84, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ApplicationGuardContainerProxy' -Value '' -Type StringIntune 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: Application Guard Container Proxy
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 84, 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
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Edge' -Name 'ApplicationGuardContainerProxy' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Application Guard Container Proxy
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 84, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ApplicationGuardContainerProxy' -Value '' -Type StringSCCM scripts
# Exported from gporais.com
# Policy: Application Guard Container Proxy
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 84, 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: Application Guard Container Proxy
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 84, 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
}
$checks = @(
(Test-RegistryValue -Path 'HKLM:\Software\Policies\Microsoft\Edge' -Name 'ApplicationGuardContainerProxy' -Expected '' -Kind String)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Application Guard Container Proxy
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 84, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'ApplicationGuardContainerProxy' -Value '' -Type StringBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.