Open in the explorer

OneAuth Authentication Flow Enforced for signin (deprecated)

Type
Computer and user
GPO path
Computer Configuration › Policies › Administrative Templates › Microsoft Edge › Identity and sign-in User Configuration › Policies › Administrative Templates › Microsoft Edge › Identity and sign-in
Supported on
Microsoft Edge version 93, Windows 7 or later
ADMX file
msedge.admx
Internal name
msedge/OneAuthAuthenticationEnforced

Explanation

DEPRECATED: This policy is deprecated. It is currently supported but will become obsolete in a future release.

Microsoft Edge will use OneAuth for sign-in on Windows without requiring this policy. The policy is deprecated starting in version 155 and is planned to become obsolete in version 161. No configuration change or replacement policy is needed to continue using OneAuth.

This policy allows users to decide whether to use the OneAuth library for sign-in and token fetch in Microsoft Edge on Windows 10 RS3 and later.

If you disable or don't configure this policy, sign-in process uses Windows Account Manager. Microsoft Edge would be able to use accounts you signed in to Windows, Microsoft Office, or other Microsoft applications for sign in, without the need for a password. Or, you can provide valid account and password to sign in, which are stored in Windows Account Manager for future usage. You can investigate all accounts stored in Windows Account Manager through Windows Settings -> Accounts -> Email and accounts page.

If you enable this policy, OneAuth authentication flow is used for account sign in. The OneAuth authentication flow has fewer dependencies and works without Windows shell. The account you use isn't stored in the Email and accounts page.

This policy only takes effect on Windows 10 RS3 and later. On Windows 10 earlier to RS3, OneAuth is used for authentication in Microsoft Edge by default.

Registry

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Edge
HKEY_CURRENT_USER\Software\Policies\Microsoft\Edge
Value name
OneAuthAuthenticationEnforced
StateValue written
EnabledREG_DWORD = 1
DisabledREG_DWORD = 0

PowerShell

PowerShell commands that write to the registry what the policy would write. Values in angle brackets (<…>) must be replaced.

Writing directly to the registry bypasses Group Policy: if a GPO manages this value, it will be rewritten at the next gpupdate; otherwise the value stays in place (the "tattooing" effect). Prefer a GPO or, locally, LGPO.exe. Run PowerShell as administrator for HKLM. Some policies need a restart or gpupdate /force.

Computer (HKLM)

Enable

# Enable: msedge/OneAuthAuthenticationEnforced
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'OneAuthAuthenticationEnforced' -Value 1 -Type DWord

Disable

# Disable: msedge/OneAuthAuthenticationEnforced
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
if (-not (Test-Path -Path $k)) { New-Item -Path $k -Force | Out-Null }
Set-ItemProperty -Path $k -Name 'OneAuthAuthenticationEnforced' -Value 0 -Type DWord

Revert to "Not configured"

# Revert to "Not configured": msedge/OneAuthAuthenticationEnforced
$k = 'HKLM:\Software\Policies\Microsoft\Edge'
Remove-ItemProperty -Path $k -Name 'OneAuthAuthenticationEnforced' -ErrorAction SilentlyContinue

User (HKCU)

Enable

Disable

Revert to "Not configured"

Application

Microsoft Edge (+ Edge Update, WebView2) (Microsoft) — November 2026 templates

Official templates downloaded on November 12, 2026.