OneAuth Authentication Flow Enforced for signin (deprecated)

Policy ID
OneAuthAuthenticationEnforced
Scope
Computer Configuration, User Configuration
Supported on
Microsoft Edge version 93, Windows 7 or later
Source
Microsoft Edge Policy Templates (version 155.0.4283.45)
Category
Microsoft Edge › Identity and sign-in

Description

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

ComputerHKEY_LOCAL_MACHINE
  • OneAuthAuthenticationEnforcedREG_DWORD
UserHKEY_CURRENT_USER
  • OneAuthAuthenticationEnforcedREG_DWORD

Other policies in the same category

View all policies in this category (17)