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

Microsoft.Identity.Client.MsalError

public static class MsalError
Error code returned as a property in MsalException
public const string AccessDenied = "access_denied"

Access denied.

public const string AccessingWsMetadataExchangeFailed = "accessing_ws_metadata_exchange_failed"

Accessing WS Metadata Exchange Failed.

What happens?

You tried to use AcquireTokenByUsernamePassword and the account is a federated account.

Mitigation

None. The WS metadata was not found or does not correspond to what was expected.

public const string AccessTokenTypeMissing = "token_type_missing"

What happens?

The response from the token endpoint does not contain the token_type parameter.

Mitigation

This happens if the identity provider (AAD, B2C, ADFS, etc.) did not include the access token type in the token response. Verify the configuration of the identity provider.

public const string ActivityRequired = "activity_required"

On Android, you need to call AcquireTokenInteractiveParameterBuilder.WithParentActivityOrWindow(object) passing the activity. See https://aka.ms/msal-interactive-android

public const string AdfsNotSupportedWithBroker = "adfs_not_supported_with_broker"

What happens?

Broker is configured with an ADFS authority, however, it does not support ADFS environments.

Mitigation

Broker does not support ADFS environments.

public const string AndroidBrokerOperationFailed = "android_broker_operation_failed"

Failed To Complete Android Broker Operation

public const string AndroidBrokerSignatureVerificationFailed = "broker_signature_verification_failed"

Failed to validate android broker signature

public const string AuthenticationCanceledError = "authentication_canceled"

Authentication canceled.

What happens?

The user had canceled the authentication, for instance by closing the authentication dialog

Mitigation

None, you cannot get a token to call the protected API. You might want to inform the user

public const string AuthenticationFailed = "authentication_failed"

Authentication failed.

What happens?

The authentication failed. For instance the user did not enter the right password

Mitigation

Inform the user to retry.

public const string AuthenticationUiFailed = "authentication_ui_failed"

The request could not be performed because of an unknown failure in the UI flow.*

Mitigation

Inform the user.

public const string AuthenticationUiFailedError = "authentication_ui_failed"

The request could not be performed because of a failure in the UI flow.

What happens?

The library failed to invoke the Web View required to perform interactive authentication. The exception might include the reason

Mitigation

If the exception includes the reason, you could inform the user. This might be, for instance, a browser implementing chrome tabs is missing on the Android phone (that's only an example: this exception can apply to other platforms as well)

public const string AuthorityHostMismatch = "authority_host_mismatch"

The cloud (authority URL host) defined at the application level cannot be different than the cloud at the request level.

What happens?

You did not define an authority at the application level, so it defaults to the public cloud (login.microsoft.com), but the authority at the request level is for a different cloud. Only the tenant can be changed at the request level.

Mitigation

Add .WithAuthority("https://login.windows-ppe.net/common) at the application level and specify the tenant at the request level: .WithAuthority("https://login.windows-ppe.net/1234-567-890-12345678).

public const string AuthorityTenantSpecifiedTwice = "authority_tenant_specified_twice"

What happens?

You specified a tenant twice - once in WithAuthority() and once using WithTenant()

Mitigation

Specify the tenant once.

public const string AuthorityTypeMismatch = "authority_type_mismatch"

What happens?

The authority configured at the application level is different than the authority configured at the request level

Mitigation

Ensure the same authority type is used

public const string AuthorityValidationFailed = "authority_validation_failed"

Authority validation failed.

What happens?

The validation of the authority failed. This might be because the authority is not compliant with the OIDC standard, or there might be a security issue

Mitigation

Use a different authority. If you are absolutely sure that you can trust the authority you can use the WithAuthority passing the validateAuthority parameter to false (not recommended)

public const string B2CAuthorityHostMismatch = "B2C_authority_host_mismatch"

The B2C authority host is not the same as the one used when creating the client application.

public const string BrokerApplicationRequired = "broker_application_required"

What happens?

A broker application is required, but one could not be found or communicated with.

Mitigation

Install a broker application, such as Authenticator, from the application store

public const string BrokerDoesNotSupportPop = "broker_does_not_support_pop"

What happens?

The request has broker enabled and Proof-of-Possession configured but the broker does not support Proof-of-Possession

Mitigation

only configure Proof-of-Possession for public clients on windows.

public const string BrokerNonceMismatch = "broker_nonce_mismatch"

Broker response nonce does not match the request nonce sent by MSAL.NET for iOS broker >= v6.3.19

public const string BrokerRequiredForPop = "broker_required_for_pop"

What happens?

The request has Proof-of-Possession configured but does not have broker enabled. Broker is required to use Proof-of-Possession on public clients

Mitigation

Enable the broker when Proof-of-Possession is configured.

public const string BrokerResponseHashMismatch = "broker_response_hash_mismatch"

Broker response hash did not match

public const string BrokerResponseReturnedError = "broker_response_returned_error"

Broker response returned an error

public const string CannotAccessUserInformationOrUserNotDomainJoined = "user_information_access_failed"

Cannot Access User Information or the user is not a user domain.

What happens?

You tried to use AcquireTokenByIntegratedWindowsAuth but the user is not a domain user (the machine is not domain or AAD joined)

public const string CannotInvokeBroker = "cannot_invoke_broker"

MSAL is not able to invoke the broker. Possible reasons are the broker is not installed on the user's device, or there were issues with the UiParent or CallerViewController being null. See https://aka.ms/msal-brokers

public const string CannotSwitchBetweenImdsVersionsForPreview = "cannot_switch_between_imds_versions_for_preview"

The system has already fallen back IMDS V1 and can only get Bearer tokens. It needs to be restarted to get mTLS PoP tokens.

public const string CertificateNotRsa = "certificate_not_rsa"

What happens?

The certificate provided is not of type RSA.

Mitigation

Please use an RSA certificate.

public const string CertWithoutPrivateKey = "cert_without_private_key"

What happens?

The certificate provided does not have a private key.

Mitigation

Ensure the certificate has a private key.

public const string ClientCredentialAuthenticationTypeMustBeDefined = "Client_Credentials_Required_In_Confidential_Client_Application"

What happens?

You configured MSAL confidential client authentication without an authentication type (Certificate, Secret, Client Assertion)

Mitigation

Either call ConfidentialClientApplicationBuilder.WithClientSecret, ConfidentialClientApplicationBuilder.WithCertificate, ConfidentialClientApplicationBuilder.WithClientAssertion

public const string ClientCredentialAuthenticationTypesAreMutuallyExclusive = "Client_Credential_Authentication_Types_Are_Mutually_Exclusive"

What happens?

You configured MSAL confidential client authentication with more than one authentication type (Certificate, Secret, Client Assertion)

public const string CodeExpired = "code_expired"

What happens?

In the context of Device code flow (See https://aka.ms/msal-net-device-code-flow), this error happens when the device code expired before the user signed-in on another device (this is usually after 15 mins).

Mitigation

None. Inform the user that they took too long to sign-in at the provided URL and enter the provided code.

public const string CombinedUserAppCacheNotSupported = "combined_user_app_cache_not_supported"

Using combined flat storage, like a file, to store both app and user tokens is not supported. Use a partitioned token cache (for ex. distributed cache like Redis) or separate files for app and user token caches. See https://aka.ms/msal-net-token-cache-serialization .

public const string CryptographicError = "cryptographic_error"

A cryptographic exception occurred when trying to use the provided certificate

public const string CurrentBrokerAccount = "current_broker_account"

This error code comes back from AcquireTokenSilent calls when the OperatingSystemAccount user is passed as the account parameter. Only some brokers (WAM) can login the current user.

Mitigation

On Windows, use the broker via .WithBroker(true), use a different account, or otherwise call AcquireTokenInteractive

public const string CustomMetadataInstanceOrUri = "custom_metadata_instance_or_uri"

What happens?

You have configured your own instance metadata using both an Uri and a string. Only one is supported.

Mitigation

Call WithInstanceDiscoveryMetadata only once. See https://aka.ms/msal-net-custom-instance-metadata for more details.

public const string CustomWebUiRedirectUriMismatch = "custom_webui_invalid_mismatch"

Error code used when the CustomWebUI has returned a URI, but it does not match the Authority and AbsolutePath of the configured redirect URI.

public const string CustomWebUiReturnedInvalidUri = "custom_webui_returned_invalid_uri"

Error code used when the ICustomWebUi has returned a URI, but it is invalid - it is either null or has no code. Consider throwing an exception if you are unable to intercept the URI containing the code.

public const string DefaultRedirectUriIsInvalid = "redirect_uri_validation_failed"

RedirectUri validation failed.

public const string DeviceCertificateNotFound = "device_certificate_not_found"

Device certificate not found.

public const string DuplicateQueryParameterError = "duplicate_query_parameter"

Duplicate query parameter was found in extraQueryParameters.

What happens?

You have used extraQueryParameter of overrides of token acquisition operations in public client and confidential client application and are passing a parameter which is already present in the URL (either because you had it in another way, or the library added it).

Mitigation [App Development]

RemoveAccount the duplicate parameter from the token acquisition override.

public const string EncodedTokenTooLong = "encoded_token_too_long"

Encoded token too long.

What happens

In a confidential client application call, the client assertion built by MSAL is longer than the max possible length for a JWT token.

public const string ExactlyOneScopeExpected = "exactly_one_scope_expected"

Exactly one scope is expected.

public const string ExperimentalFeature = "experimental_feature"

What happens?

You are trying to use a feature which was marked as experimental

Mitigation

When creating the PublicClientApplication or ConfidentialClientApplication, use .WithExperimentalFeatures() option. See https://aka.ms/msal-net-experimental-features for details.

public const string FailedToAcquireTokenSilentlyFromBroker = "failed_to_acquire_token_silently_from_broker"

Failed to acquire token silently. Used in broker scenarios.

What happens

you called AcquireTokenSilent or AcquireTokenSilent and your mobile (Xamarin) application leverages the broker (Microsoft Authenticator or Microsoft Company Portal), but the broker was not able to acquire the token silently.

Mitigation

Call AcquireTokenInteractive

public const string FailedToGetBrokerResponse = "failed_to_get_broker_response"

What happens?

You are trying to authenticate with the broker but MSAL is unable to read the response from the broker.

Mitigation

The currently installed broker may not support MSAL.Xamarin, you need to ensure that you have installed either Intune Company Portal (5.0.4689.0 or greater) or Microsoft Authenticator (6.2001.0140 or greater). see https://aka.ms/Brokered-Authentication-for-Android"

public const string FailedToRefreshToken = "failed_to_refresh_token"

Failed to refresh token.

What happens?

The token could not be refreshed. This can be because the user has not used the application for a long time. and therefore the refresh token maintained in the token cache has expired

Mitigation

If you are in a public client application, that supports interactivity, send an interactive request AcquireTokenInteractive. Otherwise, use a different method to acquire tokens.

public const string FederatedServiceReturnedError = "federated_service_returned_error"

Federated service returned error.

Mitigation

None. The federated service returned an error. You can try to look at the Body of the exception for a better understanding of the error and choose the mitigation

public const string ForceRefreshNotCompatibleWithTokenHash = "force_refresh_and_token_hash_not_compatible"

What happened?

The operation attempted to force a token refresh while also using a token hash. These two options are incompatible because forcing a refresh bypasses token caching, which conflicts with token hash validation.

Mitigation:

- Ensure that `force_refresh` is not set to `true` when using a token hash. - Review the request parameters to ensure they are not conflicting. - If token hashing is required, allow the cached token to be used instead of forcing a refresh.

public const string GetUserNameFailed = "get_user_name_failed"

Failed to get user name.

public const string HttpListenerError = "http_listener_error"

An HttpListenerException occurred while listening for the system browser to complete the login.

public const string HttpStatusCodeNotOk = "http_status_not_200"

ErrorCode used when the HTTP response returns something different from 200 (OK)

public const string HttpStatusNotFound = "not_found"

Error code used when the HTTP response returns HttpStatusCode.NotFound

public const string ImdsServiceError = "imds_service_error"

Represents the error code returned when an IMDS operation fails.

public const string InitializeProcessSecurityError = "initialize_process_security_error"

What happens?

Failure setting process security to enable WAM Account Picker in an elevated process.

Mitigation

For troubleshooting details, see https://aka.ms/msal-net-wam .

public const string IntegratedWindowsAuthenticationFailed = "integrated_windows_authentication_failed"

This can occur if there is an configuration issue in the ADFS environment where this is authenticating. See https://aka.ms/msal-net-iwa-troubleshooting for more details

public const string IntegratedWindowsAuthNotSupportedForManagedUser = "integrated_windows_auth_not_supported_managed_user"

Integrated Windows Auth is only supported for "federated" users

public const string InteractionRequired = "interaction_required"

Standard OAuth2 protocol error code. It indicates that the application needs to expose the UI to the user so the user can do an interactive log-in to get a token with updated claims.

Mitigation:

If your application is a IPublicClientApplication call AcquireTokenInteractive perform an interactive authentication. If your application is a ConfidentialClientApplication chances are that the Claims member of the exception is not empty. See Claims for the right mitigation

public const string InternalCacheDisabled = "internal_cache_disabled"

What happened?

A cache-dependent API was called, but MSAL's internal token cache is disabled via DisableInternalCacheOptions. This can occur with APIs such as AcquireTokenSilent and AcquireTokenInLongRunningProcess(...).

Mitigation

Use an authentication flow that does not depend on MSAL's internal cache, such as AcquireTokenByRefreshToken with the refresh token obtained from GetRefreshToken, or use another interactive flow, as appropriate for your application.

public const string InternalError = "internal_error"

Internal error

public const string InvalidAdalCacheMultipleRTs = "invalid_adal_cache"

What happens?

The ADAL cache is invalid as it contains multiple refresh token entries for one user.

Mitigation

Delete the ADAL cache. If you do not maintain an ADAL cache, this may be a bug in MSAL.

public const string InvalidAuthority = "invalid_authority"

Invalid authority

What happens

When the library attempts to discover the authority and get the endpoints it needs to acquire a token, it got an un-authorize HTTP code or an unexpected response

remediation

Check that the authority configured for the application, or passed on some overrides of token acquisition tokens supporting authority override is correct

public const string InvalidAuthorityType = "invalid_authority_type"

Invalid authority type. MSAL.NET does not know how to interact with the authority specified when the application was built.

Mitigation

Use a different authority

public const string InvalidAuthorizationUri = "invalid_authorization_uri"

An authorization Uri has been intercepted, but it cannot be parsed. See the log for more details.

public const string InvalidCertificate = "invalid_certificate"

The certificate received from the Imds server is invalid.

public const string InvalidClient = "invalid_client"

Azure AD service error indicating a configuration issue.

Mitigation

See error message for details, then take corrective action in the app registration portal See https://aka.ms/msal-net-invalid-client for details.

public const string InvalidClientAssertion = "invalid_client_assertion"

Returned when a WithClientAssertion delegate provides a null or empty JWT string.

Mitigation

Ensure the delegate returns a non‑empty, base‑64‑encoded JWT.

public const string InvalidClientCredentialConfiguration = "invalid_client_credential_configuration"

What happens?

You configured both a static certificate (WithCertificate(X509Certificate2)) and a dynamic certificate provider (WithCertificate(Func)).

Mitigation

Choose one approach for providing the client certificate.

public const string InvalidCredentialMaterial = "invalid_credential_material"

What happened?

The configured credential type is not compatible with the requested authentication mode. For example, a client secret cannot be used with mTLS Proof-of-Possession or SendCertificateOverMtls because mTLS requires a certificate to bind the token to the TLS transport.

Mitigation:

Use a certificate-based credential via WithCertificate(), or a delegate that returns a ClientSignedAssertion with a TokenBindingCertificate when mTLS Proof-of-Possession is required.

public const string InvalidGrantError = "invalid_grant"

Standard OAuth2 protocol error code. It indicates that the application needs to expose the UI to the user so that the user does an interactive action in order to get a new token.

Mitigation:

If your application is a IPublicClientApplication call AcquireTokenInteractive perform an interactive authentication. If your application is a ConfidentialClientApplication chances are that the Claims member of the exception is not empty. See Claims for the right mitigation

public const string InvalidInstance = "invalid_instance"

AAD service error indicating that the configured authority does not exist

public const string InvalidJsonClaimsFormat = "invalid_json_claims_format"

What happens?

You have configured a claims request, but the claims string is not in JSON format

Mitigation

Ensure that the claims parameter is valid JSON. Inspect the inner exception for details about JSON parsing.

public const string InvalidJwtError = "invalid_jwt"

JWT was invalid.

What happens?

The library expected a JWT (for instance a token from the cache, or received from the STS), but the format is invalid

Mitigation

Make sure that the token cache was not tampered

public const string InvalidManagedIdentityEndpoint = "invalid_managed_identity_endpoint"

Invalid managed identity endpoint.

public const string InvalidManagedIdentityIdType = "invalid_managed_identity_id_type"

The managed identity's source does not select a specific id type.

public const string InvalidManagedIdentityResponse = "invalid_managed_identity_response"

A required value is missing from the managed identity response.

public const string InvalidOwnerWindowType = "invalid_owner_window_type"

Invalid owner window type.

What happens?

You used "AcquireTokenInteractiveParameterBuilder.WithParentActivityOrWindow(object) but the parameter you passed is invalid.

Remediation

On .NET Standard, the expected object is an Activity on Android, a UIViewController on iOS, a NSWindow on MAC, and a IWin32Window or IntPr on Windows. If you are in a WPF application, you can use WindowInteropHelper(wpfControl).Handle to get the window handle associated with a WPF control

public const string InvalidRequest = "invalid_request"

Request is invalid.

What happens?

This can happen because you are using a token acquisition method which is not compatible with the authority. For instance: you called AcquireTokenByUsernamePassword but you used an authority ending with '/common' or '/consumers' as this requires a tenanted authority or '/organizations'.

Mitigation

Adjust the authority to the AcquireTokenXX method you use (don't use 'common' or 'consumers' with AcquireTokenByUsernamePassword AcquireTokenByIntegratedWindowsAuth

public const string InvalidTokenProviderResponseValue = "invalid_token_provider_response_value"

A required value is missing from the token provider response

public const string InvalidUserInstanceMetadata = "invalid-custom-instance-metadata"

What happens?

You have configured your own instance metadata, but the json provided seems to be invalid.

Mitigation

See https://aka.ms/msal-net-custom-instance-metadata for an example of a valid json that can be used.

public const string JsonParseError = "json_parse_failed"

JSON parsing failed.

What happens?

A JSON blob read from the token cache or received from the STS was not parseable. This can happen when reading the token cache, or receiving an IDToken from the STS.

Mitigation

Make sure that the token cache was not tampered

public const string LinuxXdgOpen = "linux_xdg_open_failed"

What happens?

MSAL tried to open the browser on Linux using the xdg-open, gnome-open, or kfmclient tools, but failed.

Mitigation

Make sure you can open a page using xdg-open tool. See https://aka.ms/msal-net-os-browser for details.

public const string LoopbackRedirectUri = "loopback_redirect_uri"

What happens?

The current redirect URL is not a loopback URL.

Mitigation

To use the OS browser, a loopback URL, with or without a port, must be configured both during app registration and when initializing the IPublicClientApplication object. See https://aka.ms/msal-net-os-browser for details.

public const string LoopbackResponseUriMismatch = "loopback_response_uri_mismatch"

What happens?

MSAL has intercepted a Uri possibly containing an authorization code, but it does not match the configured redirect URL.

Mitigation

If you are using an ICustomWebUi implementation, make sure the redirect URL matches the URL containing the auth code. If you are not using an ICustomWebUI, this could be a man-in-the middle attack.

public const string ManagedIdentityAllSourcesUnavailable = "managed_identity_all_sources_unavailable"

All managed identity sources are unavailable.

public const string ManagedIdentityRequestFailed = "managed_identity_request_failed"

Managed Identity error response was received.

public const string ManagedIdentityResponseParseFailure = "managed_identity_response_parse_failure"

Managed Identity error response was received.

public const string ManagedIdentityUnreachableNetwork = "managed_identity_unreachable_network"

Managed Identity endpoint is not reachable.

public const string MissingFederationMetadataUrl = "missing_federation_metadata_url"

Federation Metadata URL is missing for federated user.

public const string MissingManagedIdentityEnvVar = "missing_managed_identity_env_var"

The managed identity is missing a required environment variable.

public const string MissingPassiveAuthEndpoint = "missing_passive_auth_endpoint"

No passive auth endpoint was found in the OIDC configuration of the authority

What happens?

When the libraries go to the authority and get its open id connect configuration it expects to find a Passive Auth Endpoint entry, and could not find it.

remediation

Check that the authority configured for the application, or passed on some overrides of token acquisition tokens supporting authority override is correct

public const string MissingTenantedAuthority = "missing_tenanted_authority"

Missing Tenanted Authority. MSAL.NET requires a tenanted authority (i.e., an authority with a tenant ID) for mTLS to be specified when the application is built, but none was provided.

Mitigation

Ensure that a tenanted authority, which includes a specific tenant ID, is specified during the application configuration. For example, use "https://login.microsoftonline.com/{tenantId}" or a similar URL structure.

public const string MtlsBearerWithoutRegion = "mtls_bearer_without_region"

What happened?

mTLS Bearer is configured but a region was not specified.

Mitigation

Ensure that the AzureRegion configuration is set when using mTLS Bearer as it requires a regional endpoint.

public const string MtlsCertificateNotProvided = "mtls_certificate_not_provided"

What happened?

mTLS Proof of Possession (mTLS PoP) is configured but a certificate was not provided.

Mitigation

Ensure that a valid certificate is provided in the configuration when using mTLS PoP as it is required for secure authentication.

public const string MtlsNotSupportedForManagedIdentity = "mtls_not_supported_for_managed_identity"

What happened?

mTLS is not supported for managed identity authentication.

public const string MtlsPopNotSupportedForEnvironment = "mtls_pop_not_supported_for_environment"

What happened?

mTLS Proof of Possession (mTLS PoP) is not supported for the specified sovereign cloud environment.

Mitigation:

Use the supported alternative endpoint for the sovereign cloud environment.

public const string MtlsPopTokenNotSupportedinImdsV1 = "mtls_pop_token_not_supported_in_imds_v1"

mTLS PoP tokens are not supported in IMDS V1.

public const string MtlsPopWithoutRegion = "mtls_pop_without_region"

What happened?

mTLS Proof of Possession (mTLS PoP) is configured but a region was not specified.

Mitigation

Ensure that the AzureRegion configuration is set when using mTLS PoP as it requires a regional endpoint.

public const string MultipleAccountsForLoginHint = "multiple_accounts_for_login_hint"

This error code denotes that multiple accounts were found having the same login hint and MSAL cannot choose one. Please use WithAccount to specify the account

public const string MultipleTokensMatchedError = "multiple_matching_tokens_detected"

Multiple Tokens were matched.

What happens?

This exception happens in the case of applications managing several identities, when calling AcquireTokenSilent or one of its overrides and the user token cache contains multiple tokens for this client application and the specified Account, but from different authorities.

Mitigation [App Development]

specify the authority to use in the acquire token operation

public const string NetworkNotAvailableError = "network_not_available"

The request could not be performed because the network is down.

Mitigation [App development]

In the application you could either inform the user that there are network issues or retry later

public const string NoAccountForLoginHint = "no_account_for_login_hint"

This error code denotes that no account was found having the given login hint.

What happens?

AcquireTokenSilent or WithLoginHint was called with a loginHint parameter which does not match any account in GetAccountsAsync

Mitigation

If you are certain about the loginHint, call AcquireTokenInteractive

public const string NoAndroidBrokerAccountFound = "no_broker_account_found"

MSAL is not able to find a suitable account to use with broker

public const string NoAndroidBrokerInstalledOnDevice = "No_Broker_Installed_On_Device"

MSAL cannot find the broker application to authenticate accounts.

public const string NoClientId = "no_client_id"

What happens?

You haven't set a client ID.

Mitigation

Use the application ID (a GUID) from the application portal as client ID in this SDK

public const string NonceRequiredForPopOnPCA = "nonce_required_for_pop_on_pca"

What happens?

The request has Proof-of-Possession configured but does not have a nonce configured. A nonce is required for Proof-of-Possession on public clients

Mitigation

Provide a nonce when Proof-of-Possession is configured for public clients.

public const string NonHttpsRedirectNotSupported = "non_https_redirect_failed"

Non HTTPS redirects are not supported

What happens?

This error happens when the authorization flow, which collects user credentials, gets redirected to an page that is not supported, for example if the redirect occurs over http. This error does not trigger for the final redirect, which can be http://localhost, but for intermediary redirects.

Mitigation

This usually happens when using a federated directory which is not setup correctly.

public const string NonParsableOAuthError = "non_parsable_oauth_error"

An error response was returned by the OAuth2 server and it could not be parsed

public const string NoPromptFailedError = "no_prompt_failed"

One of two conditions was encountered: The Prompt.NoPrompt was passed in an interactive token call, but the constraint could not be honored because user interaction is required, for instance because the user needs to re-sign-in, give consent for more scopes, or perform multiple factor authentication. An error occurred during a silent web authentication that prevented the authentication flow from completing in a short enough time frame.

Remediation:

call AcquireTokenInteractive so that the user of your application signs-in and accepts consent.

public const string NoRedirectUri = "no_redirect_uri"

No Redirect URI.

What happens?

You need to provide a Reply URI / Redirect URI, but have not called WithRedirectUri

public const string NoTokensFoundError = "no_tokens_found"

No token was found in the token cache.

Mitigation:

If your application is a IPublicClientApplication call AcquireTokenInteractive so that the user of your application signs-in and accepts consent. If it's a web app you should have previously called IConfidentialClientApplication.AcquireTokenByAuthorizationCode as described in https://aka.ms/msal-net-authorization-code. You need to make sure that you have requested the right scopes. For details See https://github.com/Azure-Samples/ms-identity-aspnetcore-webapp-tutorial This error should not happen in web APIs

public const string NoUsernameOrAccountIDProvidedForSilentAndroidBrokerAuthentication = "no_username_or_accountid_provided_for_silent_android_broker_authentication"

Unable to query the Android account manager because no username or home account ID is provided in the silent authentication request.

public const string NullIntentReturnedFromAndroidBroker = "null_intent_returned_from_broker"

Null intent was returned so broker activity cannot be launched

public const string OboCacheKeyNotInCacheError = "obo_cache_key_not_in_cache_error"

What happens?

The token cache does not contain a token with an OBO cache key that matches the longRunningProcessSessionKey passed into AcquireTokenInLongRunningProcess.

Mitigation

Call InitiateLongRunningProcessInWebApi with this longRunningProcessSessionKey first or call AcquireTokenInLongRunningProcess with an already used longRunningProcessSessionKey.

public const string ParsingWsMetadataExchangeFailed = "parsing_ws_metadata_exchange_failed"

Parsing WS Metadata Exchange Failed.

public const string ParsingWsTrustResponseFailed = "parsing_wstrust_response_failed"

You can get this error when using AcquireTokenByUsernamePassword In the case of a Federated user (that is owned by a federated IdP, as opposed to a managed user owned in an Azure AD tenant) ID3242: The security token could not be authenticated or authorized. The user does not exist or has entered the wrong password

public const string PasswordRequiredForManagedUserError = "password_required_for_managed_user"

Password is required for managed user.

What happens?

If can got this error when using AcquireTokenByUsernamePassword and you (or the user) did not provide a password.

public const string PlatformNotSupported = "platform_not_supported"

The library is loaded on a platform which is not supported.

public const string RedirectUriValidationFailed = "redirect_uri_validation_failed"

RedirectUri validation failed.

What happens?

The redirect URI / reply URI is invalid

How to fix

Pass a valid redirect URI.

public const string RegionalAndAuthorityOverride = "authority_override_regional"

What happens?

You configured WithAuthority at the request level, and also WithAzureRegion. This is not supported when the environment changes from application to request.

Mitigation

Use WithTenantId at the request level instead.

public const string RegionalAuthorityValidation = "regional_authority_validation"

What happens?

You configured both Regional Authority and Authority Validation. Authority validation is not currently supported for regional authorities.

Mitigation

Set the validateAuthority flag to false to use Azure Regional authority. Do not disable authority validation if you read the authority from an untrusted source, for example from the WWWAuthenticate header of an HTTP request that resulted in a 401 response.

public const string RegionDiscoveryFailed = "region_discovery_failed"

Region discovery failed.

public const string RegionDiscoveryNotEnabled = "region_discovery_unavailable"

What happens?

WithAzureRegion is set to true

Mitigation

Region discovery cannot be performed for ADFS authority.

public const string RegionDiscoveryWithCustomInstanceMetadata = "region_discovery_with_custom_instance_metadata"

What happens?

You have configured both Region Discovery and Custom Instance Metadata. Custom metadata supersedes region discovery.

Mitigation

Configure either Region Discovery or Custom Instance Discovery Metadata.

public const string RegionRequiredForMtlsPop = "region_required_for_mtls_pop"

What happened?

mTLS Proof of Possession (mTLS PoP) requires a specific Azure region to be specified.

Mitigation:

Ensure that the AzureRegion configuration is set when using mTLS PoP as it requires a regional endpoint.

public const string RequestThrottled = "request_throttled"

Service returned HTTP error code 429 which indicates the request has been throttled. For more details see https://aka.ms/msal-net-throttling

public const string RequestTimeout = "request_timeout"

The HTTP Request to the STS timed out.

Mitigation

you can retry after a delay.

public const string RopcDoesNotSupportMsaAccounts = "ropc_not_supported_for_msa"

Resource Owner Password Credential (ROPC) grant attempted with an MSA (Microsoft personal) account. ROPC does not support MSA accounts. See https://aka.ms/msal-net-ropc for details.

public const string ScopesRequired = "scopes_required_client_credentials"

What happens?

No scopes have been requested

Mitigation

At least one scope must be specified for this authentication flow

public const string ServiceNotAvailable = "service_not_available"

Service is unavailable and returned HTTP error code within the range of 500-599

Mitigation

you can retry after a delay.

public const string SetCiamAuthorityAtRequestLevelNotSupported = "set_ciam_authority_at_request_level_not_supported"

Setting the CIAM authority (ex. "{tenantName}.ciamlogin.com") at the request level is not supported. The CIAM authority must be set during application creation.

public const string SSHCertUsedAsHttpHeader = "ssh_cert_used_as_http_header"

What happens?

You have configured MSAL to request SSH certificates from AAD, and you are trying to format an HTTP authentication header.

Mitigation

SSH certificates should not used as Bearer tokens. Developers are responsible for sending the certificates to the target machines.

public const string StateMismatchError = "state_mismatch"

State returned from the STS was different from the one sent by the library

What happens?

The library sends to the STS a state associated to a request, and expects the reply to be consistent. This errors indicates that the reply is not associated with the request. This could indicate an attempt to replay a response

Mitigation

None

public const string StaticCacheWithExternalSerialization = "static_cache_with_external_serialization"

What happens?

You configured MSAL cache serialization at the same time with a static internal cache via WithCacheOptions These are mutually exclusive.

Mitigation

Use only one option. Web site and web API scenarios should rely on external cache serialization, as internal cache serialization cannot scale. See https://aka.ms/msal-net-cca-token-cache-serialization

public const string SystemWebviewOptionsNotApplicable = "embedded_webview_not_compatible_default_browser"

What happens?

You configured MSAL interactive authentication to use an embedded WebView and you also configured SystemWebViewOptions. These are mutually exclusive.

Mitigation

Either set WithUseEmbeddedWebView to true or do not use WithSystemWebViewOptions

public const string TelemetryConfigOrTelemetryCallback = "telemetry_config_or_telemetry_callback"

What happens?

You have configured both a telemetry callback and a telemetry config.

Mitigation

Only one telemetry mechanism can be configured.

public const string TenantDiscoveryFailedError = "tenant_discovery_failed"

Tenant discovery failed.

What happens?

While reading the OpenId configuration associated with the authority, the Authorize endpoint, or Token endpoint, or the Issuer was not found

Mitigation

This indicates and authority which is not Open ID Connect compliant. Specify a different authority in the constructor of the application, or the token acquisition override ///

public const string TenantOverrideNonAad = "tenant_override_non_aad"

What happens?

You configured WithTenant at the request level, but the application is using a non-AAD authority These are mutually exclusive.

Mitigation

WithTenantId can only be used in conjunction with AAD authorities.

public const string TokenCacheNullError = "token_cache_null"

This error code comes back from AcquireTokenSilent calls when the user cache had not been set in the application constructor. This should never happen in MSAL.NET 3.x as the cache is created by the application

public const string TokenTypeMismatch = "token_type_mismatch"

What happens?

You asked for one type of token, but did not receive it.

Mitigation

This happens if the Identity Provider (AAD, B2C, ADFS etc.) does not support / implement the requested token type. In case of ADFS, consider upgrading to the latest version.

public const string UapCannotFindDomainUser = "user_information_access_failed"

Cannot access the user from the OS (UWP)

What happens

You called AcquireTokenByIntegratedWindowsAuth, but the domain user name could not be found.

Mitigation

This might be because you need to add more capabilities to your UWP application in the Package.appxmanifest. See https://aka.ms/msal-net-uwp

public const string UapCannotFindUpn = "uap_cannot_find_upn"

Cannot get the user from the OS (UWP)

What happens

You called AcquireTokenByIntegratedWindowsAuth, but the domain user name could not be found.

Mitigation

This might be because you need to add more capabilities to your UWP application in the Package.appxmanifest. See https://aka.ms/msal-net-uwp

public const string UnableToParseAuthenticationHeader = "unable_to_parse_authentication_header"

MSAL is unable to parse the authentication header returned from the endpoint. This can be a result of a malformed header returned in either the WWW-Authenticate or the Authentication-Info collections.

public const string UnauthorizedClient = "unauthorized_client"

The client is unauthorized to access resource. This commonly happens when Mobile App Management (MAM) policies are enabled. MSAL will throw an exception in that case with protection_policy_required sub-error.

Mitigation

Catch the exception and use the properties in it to obtain the right parameters from Intune SDK. IntuneAppProtectionPolicyRequiredException

public const string UnknownBrokerError = "unknown_broker_error"

Unknown broker error occurred.

Mitigation

None. You might want to inform the end user.

public const string UnknownError = "unknown_error"

Unknown Error occurred.

Mitigation

None. You might want to inform the end user.

public const string UnknownManagedIdentityError = "unknown_managed_identity_error"

Unknown error response received.

public const string UnknownUser = "unknown_user"

What happens

You can get this error when using AcquireTokenByUsernamePassword The user is not known by the IdP

Mitigation

Inform the user. The login that the user provided might be incorrect (for instance empty)

public const string UnknownUserType = "unknown_user_type"

What happens

You can get this error when using AcquireTokenByUsernamePassword The user is not recognized as a managed user, or a federated user. Azure AD was not able to identify the IdP that needs to process the user

Mitigation

Inform the user. the login that the user provided might be incorrect.

public const string UpnRequired = "upn_required"

loginHint should be a UPN

What happens?

An override of a token acquisition operation was called in IPublicClientApplication which takes a loginHint as a parameters, but this login hint was not using the UserPrincipalName (UPN) format, e.g. john.doe@contoso.com expected by the service

Remediation

Make sure in your code that you enforce loginHint to be a UPN

public const string UserAssertionNullError = "user_assertion_null"

This error code comes back from AcquireTokenOnBehalfOf calls when a null user assertion is passed as the UserAssertion parameter.

Mitigation

Pass a valid value for user assertion

public const string UserAssignedManagedIdentityNotConfigurableAtRuntime = "user_assigned_managed_identity_not_configurable_at_runtime"

User assigned managed identity is not configurable at runtime for service fabric.

public const string UserAssignedManagedIdentityNotSupported = "user_assigned_managed_identity_not_supported"

User assigned managed identity is not supported for this source.

public const string UserMismatch = "user_mismatch"

User Mismatch.

public const string UserNullError = "user_null"

This error code comes back from AcquireTokenSilent calls when a null user is passed as the account parameter. This can be because you have called AcquireTokenSilent with an account parameter set to accounts.FirstOrDefault() but accounts is empty.

Mitigation

Pass a different account, or otherwise call AcquireTokenInteractive

public const string UserRealmDiscoveryFailed = "user_realm_discovery_failed"

User Realm Discovery Failed.

public const string ValidateAuthorityOrCustomMetadata = "validate_authority_or_custom_instance_metadata"

What happens?

You have configured your own instance metadata, and have also set validate authority to true. These are mutually exclusive.

Mitigation

Set the validate authority flag to false. See https://aka.ms/msal-net-custom-instance-metadata for more details.

public const string WABError = "wab_error"

What happens?

Windows Authentication Broker, which handles the interaction between the user and AAD, has failed.

Mitigation

See the error message for more details.

public const string WamFailedToSignout = "wam_failed_to_signout"

WAM Signout failed.

public const string WamInteractiveError = "wam_interactive_error"

WAM service exception that can occur when calling AcquireTokenInteractive

public const string WamNoB2C = "wam_no_b2c"

The Windows broker (WAM) is only supported in conjunction with "work and school" accounts and with Microsoft accounts.

public const string WamPickerError = "wam_interactive_picker_error"

WAM service exception that can occur when calling AcquireTokenInteractive and the account picker pops up

public const string WamScopesRequired = "scopes_required_wam"

What happens?

No scopes have been requested

Mitigation

At least one scope must be specified for MSAL Runtime WAM

public const string WamUiThread = "wam_ui_thread_only"

When calling AcquireTokenInteractive with the WAM broker, the call must be made from the UI thread.

public const string WebView2LoaderNotFound = "webview2loader_not_found"

What happens?

The embedded WebView2 browser cannot be started because a runtime component cannot be loaded.

Mitigation

For troubleshooting details, see https://aka.ms/msal-net-webview2 .

public const string WebView2NotInstalled = "webview2_runtime_not_installed"

What happens?

The embedded browser cannot be started because a runtime component is missing.

Mitigation

The embedded browser needs WebView2 runtime to be installed. An end user of the app can download and install the WebView2 runtime from https://go.microsoft.com/fwlink/p/?LinkId=2124703 and restart the app. The app developer can get the distributable version of the WebView2 runtime.

public const string WebviewUnavailable = "no_system_webview"

The selected WebView is not available on this platform. You can switch to a different WebView using WithUseEmbeddedWebView. See https://aka.ms/msal-net-os-browser for details

public const string WsTrustEndpointNotFoundInMetadataDocument = "wstrust_endpoint_not_found"

WS-Trust Endpoint Not Found in Metadata Document.