1.9.0

Microsoft.Identity.Web 1.9.0

Performance improvements

In Microsoft.Identity.Web 1.9.0, we've done a lot of performance improvement. Part of these improvements, we've removed async to methods when they don't need to be async. Most are internal to Microsoft.Identity.Web and if you are using ASP.NET core, you should not be impacted. If you use ASP.NET, however, with MSAL.NET in hybrid scenarios, you'll see a new obsolete warning.

See for instance in: https://github.com/Azure-Samples/ms-identity-aspnet-webapp-openidconnect/blob/00bac85bd7215c44fef89a9b61ced744d06f9503/WebApp/Utils/MsalAppBuilder.cs#L68-L69

 IMsalTokenCacheProvider memoryTokenCacheProvider = CreateTokenCacheSerializer();
 await memoryTokenCacheProvider.InitializeAsync(clientapp.UserTokenCache);

you now want to use:

 IMsalTokenCacheProvider memoryTokenCacheProvider = CreateTokenCacheSerializer();
 memoryTokenCacheProvider.Initialize(clientapp.UserTokenCache);

Support for .NET Framework 4.6.2

Microsoft.Identity.Web now supports .NET Framework 4.6.2 in addition to .NET Framework 4.7.2.

Add support for Azure SDKs

The Azure SDKs use the notion TokenCredential. Microsoft.Identity.Web now exposes a TokenAcquisitionTokenCredential which can be used with the Azure SDKs. For instance, to access storage from a controller, you can inject a ITokenAcquisition and new-up a TokenAcquisitionTokenCredential.

Enable client capabilities - CAE