Merge pull request #672 from ashok672/asram/update-msal.net-docs

MSAL.NET Docs update to mention third party IDPs are not supported

Author: bgavrilMS

msal-dotnet-articles/acquiring-tokens/desktop-mobile/wam.md

@@ -33,6 +33,9 @@ An authentication broker is an application that runs on a user’s machine that
 > [!IMPORTANT]
 > Use MSAL.NET 4.52.0 or higher to get broker support.
 
+> [!IMPORTANT]
+> WAM supports only Microsoft Entra ID and does not work with third-party identity providers (IDPs).
+
 WAM support is split across two packages:
 
 - [Microsoft.Identity.Client](https://www.nuget.org/packages/Microsoft.Identity.Client/) (i.e., MSAL) - core library for token acquisition.

msal-dotnet-articles/index.md

@@ -41,6 +41,13 @@ MSAL.NET supports multiple platforms, including [.NET](https://dotnet.microsoft.
 >- Mobile platforms do not allow confidential client flows. They are not meant to function as a backend and cannot store secrets securely.
 >- On public clients (mobile and desktop) the default browser and redirect URIs are different from platform to platform, and broker availability varies (details [in browser usage documentation](./acquiring-tokens/using-web-browsers.md)).
 
+> [!NOTE]
+> MSAL.NET is optimized for use with Microsoft Entra ID as the identity provider (IDP). 
+> While it is possible to use MSAL.NET with third-party IDPs that support OAuth 2.
+> 0—particularly when using embedded or system browsers((see [in browser usage documentation](./acquiring-tokens/using-web-browsers.md)))
+> —interoperability is not guaranteed. Microsoft does not provide support for issues arising from third-party IDP integrations. Such scenarios are considered
+> best-effort and may not be addressed.
+
 > [!NOTE]
 > MSAL.NET versions 4.61.0 and above do not provide support for Universal Windows Platform, Xamarin Android, and Xamarin iOS. Read more about the deprecation in [Announcing the Upcoming Deprecation of MSAL.NET for Xamarin and UWP](https://devblogs.microsoft.com/identity/uwp-xamarin-msal-net-deprecation/).