Migrate applications to the Microsoft Authentication Library (MSAL)
If any of your applications use the Azure Active Directory Authentication Library (ADAL) for authentication and authorization functionality, it's time to migrate them to the Microsoft Authentication Library (MSAL).
- All Microsoft support and development for ADAL, including security fixes, ends in December, 2022.
- There are no ADAL feature releases or new platform version releases planned prior to December, 2022.
- No new features have been added to ADAL since June 30, 2020.
If you choose not to migrate to MSAL before ADAL support ends in December, 2022, you put your app's security at risk. Existing apps that use ADAL will continue to work after the end-of-support date, but Microsoft will no longer release security fixes on ADAL.
Why switch to MSAL?
MSAL provides multiple benefits over ADAL, including the following features:
|Security fixes beyond December, 2022|
|Proactively refresh and revoke tokens based on policy or critical events for Microsoft Graph and other APIs that support Continuous Access Evaluation (CAE).|
|Standards compliant with OAuth v2.0 and OpenID Connect (OIDC)|
|User accounts and experiences|
|Azure Active Directory (Azure AD) accounts|
|Microsoft account (MSA)|
|Azure AD B2C accounts|
|Best single sign-on experience|
|Proactive token renewal|
AD FS support in MSAL.NET
You can use MSAL.NET, MSAL Java, and MSAL Python to get tokens from Active Directory Federation Services (AD FS) 2019 or later. Earlier versions of AD FS, including AD FS 2016, are unsupported by MSAL.
If you need to continue using AD FS, you should upgrade to AD FS 2019 or later before you update your applications from ADAL to MSAL.
How to migrate to MSAL
Before you start the migration, you need to identify which of your apps are using ADAL for authentication. Follow the steps in this article to get a list by using the Azure portal:
After identifying your apps that use ADAL, migrate them to MSAL depending on your application type as illustrated below.
Single-page app (SPA)
If you have questions about migrating your app from ADAL to MSAL, here are some options:
- Post your question on Microsoft Q&A and tag it with
- Open an issue in the library's GitHub repository. See the Languages and frameworks section of the MSAL overview article for links to each library's repo.
If you partnered with an Independent Software Vendor (ISV) in the development of your application, we recommend that you contact them directly to understand their migration journey to MSAL.
For more information about MSAL, including usage information and which libraries are available for different programming languages and application types, see:
Submit and view feedback for