Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
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 ways, Microsoft Graph resembles Azure AD Graph. Often, you can simply update the endpoint, version, and resource name in your code, and it should function as expected.
However, there are differences where some resources, properties, methods, and core capabilities have changed.
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, ensure that the APIs your app requires are generally available in Microsoft Graph v1.0 and verify if they function the same as in Azure AD Graph or have differences.
For testing, use Graph Explorer to experiment with API calls and develop new approaches. For best results, sign in with the credentials of a test user in a test tenant to 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, thoroughly test it and stage the 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.