Does a token generated using ADAL to call our custom APIs, work even after AD Graph is deprecated - (which as of now is June 30, 2023)?

Shiva Naru 20 Reputation points Microsoft Vendor

We are using ADAL library's AuthenticationContext object to acquire token. The "Authority" we are using is "{tenant-Id}. The token is then used to call our custom APIs, not Azure AD API.

I know that ADAL is being deprecated on June 30, 2023.

My question is: Will the token that is generated using ADAL like above, stop working after the deprecation date? Please note, we are not calling Azure AD API. Just our own backend APIs which authenticate using the JWT token. I assume not but wanted to get a confirmation, if my assumption is correct.

Thank you,


Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
11,096 questions
Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,145 questions
{count} votes

Accepted answer
  1. Shweta Mathur 28,846 Reputation points Microsoft Employee

    Hi @Shiva Naru ,

    Thanks for reaching out.

    Your understanding is correct here.

    ADAL will continue to work even after the deprecation date, but it will no longer receive security updates or support.

    The underpinning services will continue working and applications that depend on ADAL should continue working; however, Applications, and the resources they access, are at increased security and reliability risk due to not having the latest updates, service configuration, and enhancements made available through the Microsoft Identity platform.

    We would recommend migrating to MSAL for better security and performance.

    Hope this will help.



    Please remember to "Accept Answer" if answer helped you.

    0 comments No comments

0 additional answers

Sort by: Most helpful