Known issues

MSAL throws a few types of exceptions, please see here.

Confidential Client

Please read the guide on High Availability

System.Security.Cryptography.CryptographicException: A device attached to the system is not functioning.

When running in a tight loop, the crypto sometimes API throws the exception above. We have experienced this on .NET classic version 4.6 and lower. .NET classic 4.6.1 and above, as well as .net core seems to have these APIs fixed.

The issue is mostly seen in Client Credential flow. Mitigation is to upgrade the framework or to break the tight loop.

Public Client

Android

On Android, an AndroidActivityNotFound exception is thrown when the device does not have a browser with tabs https://docs.microsoft.com/en-gb/azure/active-directory/develop/msal-net-system-browser-android-considerations#known-issues

iOS

Please see: https://docs.microsoft.com/en-gb/azure/active-directory/develop/msal-net-xamarin-ios-considerations#known-issues-with-ios-12-and-authentication

UWP

Most issues on UWP occur due to network problems, such as proxies that block the traffic etc. Integrated Windows Auth may also be blocked by admins. For more details see:

https://docs.microsoft.com/en-gb/azure/active-directory/develop/msal-net-uwp-considerations#troubleshooting

Desktop

On Desktop app, an StateMismatchError exception is thrown when the using a long Facebook ID (via B2C) https://docs.microsoft.com/en-gb/azure/active-directory/develop/msal-net-system-browser-android-considerations#known-issues. For more details, please refer: https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/StateMismatchError