We’re thrilled to share an important update: Entra ID app sign-in through Web Account Manager (WAM) now has the option to be powered by WebView2, the Chromium-based web control, starting with KB5072033 (OS Builds 26200.7462 and 26100.7462) or later. This release marks a significant step forward in delivering a secure, modern, and consistent sign-in experience across apps and services.
What is a WebView?
A WebView is a UI component that allows you to display web content (HTML, CSS, JavaScript) inside a native application. Instead of opening a full browser, a WebView embeds a browser engine within your app so you can render web pages or web-based UI directly in your application window.
Windows has many user experiences that use WebViews to gather web information and present it to users that look like native content. One common scenario for this is authentication flows, where a user is prompted for their username and provides credentials.
Why we made this change
Authentication is the front door to your digital world. As identity experiences evolve, we need a foundation that supports modern web standards, advanced security, and future-ready scenarios. WebView2 provides exactly that.
Key benefits
This update includes several benefits, including:
- Modern Standards: Built on Chromium, WebView2 supports the latest web technologies, enabling richer, more responsive sign-in interfaces and compatibility with modern frameworks like React and Fluent UI.
- Future-Ready Experiences: Unlocks advanced scenarios such as Passwordless sign-in, passkeys, and seamless integration with Conditional Access policies — all with fewer redirects and friction.
- Better Compatibility: Improves support for third-party identity providers and enterprise apps that rely on modern web frameworks, ensuring consistent experience across diverse environments.
Getting started
This transition is seamless for most users and apps. If you manage enterprise deployments:
- Ensure your environment meets WebView2 runtime requirements (including in recent Windows builds or available via evergreen installer).
- Customers that have already seen their auth flows work in Microsoft Edge-based browsers should work without any configuration change. If any issues are observed, please see:
o Microsoft Edge identity support and configuration | Microsoft Learn
o Configure browsers to use Windows Integrated Authentication (WIA) with AD FS | Microsoft Learn
- Visit https://learn.microsoft.com/ for detailed guidance on WebView2 integration and troubleshooting.
Enabling WebView2 in the Entra ID plugin
After installing KB5072033 (OS Builds 26200.7462 and 26100.7462) or later, enable the WebView2Integration registry key by using regedit, command line, or policy to configure a registry entry by updating the registry with:
Reg key location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AAD
Reg key value: WebView2Integration as a DWORD and assign it to “1” for WebView2 integration to be ON.
Note: If the AAD key does not exist, create it by right-clicking on Windows, selecting New > Key, and naming it AAD.
After applying the registry key, the device should be ready to use. Try authenticating or adding a work account in apps such as Teams, Feedback Hub, Office, or Edge.
Disabling WebView2 in the Entra ID plugin
Disable the WebView2Integration registry key by using the registry, command line, or policy to configure a registry entry by updating the registry with:
Reg key location: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\AAD
Reg key value: WebView2Integration as a DWORD and assign it to “0” for WebView2 integration to be OFF.
After applying the registry key, the device should be ready to use. Try authenticating or adding a work account in apps such as Teams, Feedback Hub, Office, or Edge.
Looking ahead
WebView2 will become the default framework for WAM authentication in an expected future Windows release, with the EdgeHTML WebView being deprecated. Therefore, we encourage users to deploy now and participate in the opt-in process, enable this experience in their environments, and make any necessary adjustments — such as updating proxy rules or modifying code in services involved in the logon process. Contact Customer Support Services if you'd like to provide feedback.
Moving to WebView2 is more than a technical upgrade — it’s a strategic investment in secure, user-friendly identity experiences. We’re committed to evolving Entra ID to meet the needs of modern organizations and developers.
Continue the conversation. Find best practices. Bookmark the Windows Tech Community, then follow us @MSWindowsITPro on X and on LinkedIn. Looking for support? Visit Windows on Microsoft Q&A.
Microsoft