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, change the endpoint, version, and resource name in your code, and everything should continue to work.
Nonetheless, there are differences. Certain resources, properties, methods, and core capabilities 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
- Permissions
Step 2: Examine API use
Examine the APIs used by your app, the permissions they require, and compare to the list of known differences.
For production, verify that the APIs your app needs are generally available in Microsoft Graph v1.0 and inspect whether they work like in Azure AD Graph or differently.
For testing, use Graph Explorer to experiment with API 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 verify the API behavior in a realistic environment.
Step 3: Review app details
- App registration and consent changes.
- 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 production, ensure you test thoroughly and stage your rollout to your customer audience.
After switching to Microsoft Graph, you unlock many more datasets and features that are defined in Major services and features in Microsoft Graph.