Block AutoFill data types for specific sites
Verified with Microsoft Edge 154.0.4258.53 — updated on September 24, 2026 Supported on: Microsoft Edge version 154, Windows 7 or later
Path in the GPO console
Computer Configuration\Administrative Templates\Microsoft Edge User Configuration\Administrative Templates\Microsoft Edge Registry
Software\Policies\Microsoft\Edge Software\Policies\Microsoft\Edge Description
Setting this policy allows you to specify which AutoFill data types are blocked on specific URL patterns. The policy is structured as a list of dictionaries. Each dictionary must contain: * "url_pattern": A content setting URL pattern for the main frame (for example, "https://[*.]example.com"). * "blocked_types": A list of strings representing the categories of AutoFill data to block. The supported values for "blocked_types" are: * "contact_info": Blocks filling and saving of contact information. * "payments": Blocks filling and saving of credit cards and payment methods. * "identity_docs": Blocks filling and saving of identity documents (for example, passports, driver's licenses, and national IDs). * "travel": Blocks filling and saving of travel information (for example, flight reservations and vehicle registrations). * "shopping": Blocks filling and saving of shopping information (for example, online orders and shipments). * "all": Blocks filling and saving of all AutoFill data types. If a data type is blocked for a site, both the generation of suggestions and the prompt to save or import new data of that type are disabled on that site. If a URL matches multiple pattern entries in the list, the blocked types from all matching entries are combined. Invalid URL patterns in the list are ignored. If you don't configure this policy, no AutoFill data types are blocked by domain. For detailed information on valid URL patterns, see https://go.microsoft.com/fwlink/?linkid=2095322. The wildcard * is supported and matches any URL with any scheme, port, and path. Example value: [ { "url_pattern": "https://[*.]example.com", "blocked_types": [ "contact_info", "payments" ] }, { "url_pattern": "https://another-example.com", "blocked_types": [ "payments" ] }, { "url_pattern": "*", "blocked_types": [ "identity_docs" ] } ]
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: Block AutoFill data types for specific sites
; State: Enabled
; Scope: Computer (HKLM)
; Supported on: Microsoft Edge version 154, Windows 7 or later
[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge]
"AutofillSettings"=""More formats (PowerShell, Intune, SCCM)
PowerShell
# Exported from gporais.com
# Policy: Block AutoFill data types for specific sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 154, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'AutofillSettings' -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: Block AutoFill data types for specific sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 154, 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 'AutofillSettings' -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: Block AutoFill data types for specific sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 154, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'AutofillSettings' -Value '' -Type StringSCCM scripts
# Exported from gporais.com
# Policy: Block AutoFill data types for specific sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 154, 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: Block AutoFill data types for specific sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 154, 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 'AutofillSettings' -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: Block AutoFill data types for specific sites
# State: Enabled
# Scope: Computer (HKLM)
# Supported on: Microsoft Edge version 154, Windows 7 or later
$path = 'HKLM:\Software\Policies\Microsoft\Edge'
New-Item -Path $path -Force | Out-Null
Set-ItemProperty -Path $path -Name 'AutofillSettings' -Value '' -Type StringBuilding a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.