Expand WAM to Web Account Manager in disambiguation note

Co-authored-by: Copilot <[email protected]>

Author: GrantMeStrength

hub/apps/develop/security/oauth2.md

@@ -1,7 +1,7 @@
 ---
 title: Implement OAuth 2.0 in Windows Apps
 description: Learn how to implement OAuth 2.0 authentication in Windows apps using Windows App SDK's OAuth2Manager API. Secure user authentication with step-by-step examples. Get started now.
-ms.date: 04/08/2026
+ms.date: 10/28/2025
 ms.topic: concept-article
 keywords: windows, winui, winrt, dotnet, security
 #customer intent: As a Windows app developer, I want to learn how to implement OAuth 2.0 in my app so that I can securely authenticate users and access protected resources.
@@ -12,7 +12,7 @@ keywords: windows, winui, winrt, dotnet, security
 The [OAuth2Manager](/windows/windows-app-sdk/api/winrt/microsoft.security.authentication.oauth.oauth2manager) in Windows App SDK enables desktop applications such as WinUI 3 to seamlessly perform OAuth 2.0 authorization on Windows. The **OAuth2Manager** API doesn't provide APIs for the implicit request and resource owner password credential because of the security concerns that entails. Use the authorization code grant type with Proof Key for Code Exchange (PKCE). For more information, see the [PKCE RFC](https://tools.ietf.org/html/rfc7636).
 
 > [!NOTE]
-> **OAuth2Manager** is designed for general OAuth 2.0 flows with any identity provider (GitHub, Google, custom, etc.) and always uses the system browser for the authorization step. If you specifically want to sign in with **Microsoft accounts or Entra ID (work/school) accounts** with **silent SSO** — using the account already signed in to Windows, with no browser prompt — use [MSAL.NET with the WAM broker](/entra/msal/dotnet/acquiring-tokens/desktop-mobile/wam) instead. WAM also provides Windows Hello integration and conditional access support that OAuth2Manager does not.
+> **OAuth2Manager** is designed for general OAuth 2.0 flows with any identity provider (GitHub, Google, custom, etc.) and always uses the system browser for the authorization step. If you specifically want to sign in with **Microsoft accounts or Entra ID (work/school) accounts** with **silent SSO** — using the account already signed in to Windows, with no browser prompt — use [MSAL.NET with the Web Account Manager (WAM) broker](/entra/msal/dotnet/acquiring-tokens/desktop-mobile/wam) instead. Web Account Manager also provides Windows Hello integration and conditional access support that OAuth2Manager does not.
 
 ## OAuth2Manager API in Windows App SDK