Differences between MSAL JS and ADAL JS

Both Microsoft Authentication Library for JavaScript (MSAL.js) and Azure AD Authentication Library for JavaScript (ADAL.js) are used to authenticate Azure AD entities and request tokens from Azure AD. Up until now, most developers have worked with Azure AD for developers (v1.0) to authenticate Azure AD identities (work and school accounts) by requesting tokens using ADAL. Now, using MSAL.js, you can authenticate a broader set of Microsoft identities (Azure AD identities and Microsoft accounts, and social and local accounts through Azure AD B2C) through Microsoft identity platform (v2.0).

This article describes how to choose between the Microsoft Authentication Library for JavaScript (MSAL.js) and Azure AD Authentication Library for JavaScript (ADAL.js) and compares the two libraries.

Choosing between ADAL.js and MSAL.js

In most cases you want to use the Microsoft identity platform and MSAL.js, which is the latest generation of Microsoft authentication libraries. Using MSAL.js, you acquire tokens for users signing in to your application with Azure AD (work and school accounts), Microsoft (personal) accounts (MSA), or Azure AD B2C.

If you are already familiar with the v1.0 endpoint (and ADAL.js), you might want to read What's different about the v2.0 endpoint?.

However, you still need to use ADAL.js if your application needs to sign in users with earlier versions of Active Directory Federation Services (ADFS).

Key differences in authentication with MSAL.js

Core API

  • ADAL.js uses AuthenticationContext as the representation of an instance of your application's connection to the authorization server or identity provider through an authority URL. On the contrary, MSAL.js API is designed around user agent client application(a form of public client application in which the client code is executed in a user-agent such as a web browser). It provides the UserAgentApplication class to represent an instance of the application's authentication context with the authorization server. For more details, see Initialize using MSAL.js.

  • In ADAL.js, the methods to acquire tokens are associated with a single authority set in the AuthenticationContext. In MSAL.js, the acquire token requests can take different authority values than what is set in the UserAgentApplication. This allows MSAL.js to acquire and cache tokens separately for multiple tenants and user accounts in the same application.

  • The method to acquire and renew tokens silently without prompting users is named acquireToken in ADAL.js. In MSAL.js, this method is named acquireTokenSilent to be more descriptive of this functionality.

Authority value common

In v1.0, using the https://login.microsoftonline.com/common authority will allow users to sign in with any Azure AD account (for any organization).

In v2.0, using the https://login.microsoftonline.com/common authority, will allow users to sign in with any Azure AD organization account or a Microsoft personal account (MSA). To restrict the sign in to only Azure AD accounts (same behavior as with ADAL.js), you need to use https://login.microsoftonline.com/organizations. For details, see the authority config option in Initialize using MSAL.js.

Scopes for acquiring tokens

  • Scope instead of resource parameter in authentication requests to acquire tokens

    v2.0 protocol uses scopes instead of resource in the requests. In other words, when your application needs to request tokens with permissions for a resource such as MS Graph, the difference in values passed to the library methods is as follows:

    v1.0: resource=https://graph.microsoft.com

    v2.0: scope = https://graph.microsoft.com/User.Read

    You can request scopes for any resource API using the URI of the API in this format: appidURI/scope For example: https://mytenant.onmicrosoft.com/myapi/api.read

    Only for the MS Graph API, a scope value user.read maps to https://graph.microsoft.com/User.Read and can be used interchangeably.

    var request = {
        scopes = ["User.Read"];
  • Dynamic scopes for incremental consent.

    When building applications using v1.0, you needed to register the full set of permissions(static scopes) required by the application for the user to consent to at the time of login. In v2.0, you can use the scope parameter to request the permissions at the time you want them. These are called dynamic scopes. This allows the user to provide incremental consent to scopes. So if at the beginning you just want the user to sign in to your application and you don’t need any kind of access, you can do so. If later you need the ability to read the calendar of the user, you can then request the calendar scope in the acquireToken methods and get the user's consent. For example:

    var request = {
        scopes = ["https://graph.microsoft.com/User.Read", "https://graph.microsoft.com/Calendar.Read"];
  • Scopes for V1.0 APIs

    When getting tokens for V1.0 APIs using MSAL.js, you can request all the static scopes registered on the API by appending .default to the App ID URI of the API as scope. For example:

    var request = {
        scopes = [ appidURI + "/.default"];

Next steps

For more information, refer to v1.0 and v2.0 comparison.