Enable Ambient Authentication for profile types.
Verified with Google Chrome — updated on July 10, 2026 Supported on: Microsoft Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Google\Google Chrome User Configuration\Administrative Templates\Google\Google Chrome Registry
Software\Policies\Google\Chrome Software\Policies\Google\Chrome Other deployment channels
./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Miscellaneous/AmbientAuthenticationInPrivateModesEnabled OMA-URI published by Google. It requires the Chrome ADMX templates (chrome.admx, google.admx) to be imported in Intune first.
- Google Chrome (Linux) — since version 80
- Google Chrome (Mac) — since version 80
- Google Chrome (Windows) — since version 80
- Google ChromeOS (Google ChromeOS) — since version 80
Source: official Chrome policy list, version 157.0.8103.79 Chrome Enterprise policy page
Description
Configuring this policy will allow/disallow ambient authentication for Incognito and Guest profiles in Google Chrome. Ambient Authentication is http authentication with default credentials if explicit credentials are not provided via NTLM/Kerberos/Negotiate challenge/response schemes. Setting the RegularOnly (value 0), allows ambient authentication for Regular sessions only. Incognito and Guest sessions wouldn't be allowed to ambiently authenticate. Setting the IncognitoAndRegular (value 1), allows ambient authentication for Incognito and Regular sessions. Guest sessions wouldn't be allowed to ambiently authenticate. Setting the GuestAndRegular (value 2), allows ambient authentication for Guest and Regular sessions. Incognito sessions wouldn't be allowed to ambiently authenticate. Setting the All (value 3), allows ambient authentication for all sessions. Note that, ambient authentication is always allowed on regular profiles. In Google Chrome version 81 and later, if the policy is left not set, ambient authentication will be enabled in regular sessions only.
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: Enable Ambient Authentication for profile types.
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]
"AmbientAuthenticationInPrivateModesEnabled"=dword:00000000 More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Enable Ambient Authentication for profile types.
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'AmbientAuthenticationInPrivateModesEnabled' -Value 0 -Type DWord Intune XML
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/Chrome~Policy~googlechrome~Miscellaneous/AmbientAuthenticationInPrivateModesEnabled
Data type: String
Value:
<enabled/>
<data id="AmbientAuthenticationInPrivateModesEnabled" value="0"/> Intune Remediation
# === Detection script ===
# Exported from gporais.com
# Policy: Enable Ambient Authentication for profile types.
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft 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\Google\Chrome' -Name 'AmbientAuthenticationInPrivateModesEnabled' -Expected 0 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Enable Ambient Authentication for profile types.
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'AmbientAuthenticationInPrivateModesEnabled' -Value 0 -Type DWord SCCM scripts
# Exported from gporais.com
# Policy: Enable Ambient Authentication for profile types.
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft 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: Enable Ambient Authentication for profile types.
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft 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\Google\Chrome' -Name 'AmbientAuthenticationInPrivateModesEnabled' -Expected 0 -Kind DWord)
)
if ($checks -notcontains $false) {
Write-Output 'Compliant'
exit 0
}
Write-Output 'Non-compliant'
exit 1
# === Remediation script ===
# Exported from gporais.com
# Policy: Enable Ambient Authentication for profile types.
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Windows 7 or later
$path = 'HKLM:\Software\Policies\Google\Chrome'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'AmbientAuthenticationInPrivateModesEnabled' -Value 0 -Type DWord Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.