<PackageReference Include="Microsoft.Identity.Client" Version="4.85.1" />

Microsoft.Identity.Client.IPublicClientApplication

Represents public client applications - desktop and mobile applications.

Tells if the application can use the system web browser, therefore enabling single-sign-on with web applications. By default, MSAL will try to use a system browser on the mobile platforms, if it is available. See our documentation for more details.

This API is no longer recommended. If your application requires single sign-on (SSO) with the Windows OS's default account, please transition to using WAM, which provides similar functionality via the Windows broker (WAM). WAM does not require any setup for desktop apps to login with the Windows account.

Acquires a token non-interactively for the signed-in user in Windows via Integrated Windows Authentication. The account used in this overrides is pulled from the operating system as the current user principal name. This method does not look in the token cache, but stores the result in it. Before calling this method, use other methods such as AcquireTokenSilent to check the token cache.

Non-interactive request to acquire a token via username and password authentication.

Acquires a token without user interaction using username and password authentication. This method does not look in the token cache, but stores the result in it. Before calling this method, use other methods such as AcquireTokenSilent to check the token cache.

Acquires a token interactively for the specified scopes. Either a system browser, an embedded browser, or a broker will handle this request, depending on the version of .NET framework used and on configuration. For Microsoft Entra applications, a broker is recommended. See Windows Broker. This method does not look in the token cache, but stores the result in it. Before calling this method, use other methods such as AcquireTokenSilent to check the token cache. See Interactive Authentication.

Acquires a token on a device without a web browser by letting the user authenticate on another device. This method does not look in the token cache, but stores the result in it. Before calling this method, use other methods such as AcquireTokenSilent to check the token cache.