Azure AD Graph app migration planning checklist
Use the following checklist to plan your migration from Azure Active Directory (Azure AD) Graph to Microsoft Graph.
Step 1: Review the differences between the APIs
In many respects, Microsoft Graph is similar to the earlier Azure AD Graph. In many cases, simply change the endpoint service name and version in your code, and everything should continue to work.
Nonetheless, there are differences. Certain resources, properties, methods, and core capabilities have changed.
Specifically, look for differences in the following areas:
- Request call syntax between the two services
- Feature differences, such as directory extensions, batching, differential queries, and so on
- Entity resource names and their types
- Properties of request and response objects
- Methods, including parameters and types
Step 2: Examine API use
Examine the APIs used by your app, the permissions they require, and compare to the list of known differences.
Verify that the APIs your app needs are generally available in Microsoft Graph v1.0 and that these APIs work the same way.
In some cases, new capabilities and features are designed to replace earlier approaches.
Use Graph Explorer to experiment with new calls and to develop new approaches. For best results, sign in using the credentials of a test user in a test tenant so that you see what the API does over important data sets.
Step 3: Review app details
- App registration and consent changes (which should be none).
- Token acquisition and authentication libraries.
- For .NET applications, use of client libraries.
Step 4: Deploy, test, and extend your app
Before updating your app for everyone, ensure you test thoroughly and stage your rollout to your customer audience.
Now you've made the switch to Microsoft Graph, it's never been easier for you to unlock many more datasets and features that are now at your fingertips. You can get a taste of what's possible by looking at some of the Major services and features in Microsoft Graph.
Microsoft authentication library (MSAL) is now the recommended authentication library for use with the Microsoft identity platform. If you're currently using the Azure Active Directory Authentication Library (ADAL), plan to switch to MSAL. See further guidance to migrate applications to the Microsoft Authentication Library (MSAL).
- Learn about request call syntax to start step 1: reviewing API differences.
Submit and view feedback for