You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: concepts/migrate-azure-ad-graph-planning-checklist.md
+13-13Lines changed: 13 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ ms.reviewer: krbash
7
7
ms.topic: quickstart
8
8
ms.localizationpriority: medium
9
9
ms.subservice: entra-applications
10
-
ms.date: 01/12/2024
10
+
ms.date: 01/20/2025
11
11
#Customer intent: As a developer, what are some of the things I need to consider when migrating my app from Azure AD Graph to Microsoft Graph?
12
12
---
13
13
@@ -17,26 +17,26 @@ Use the following checklist to plan your migration from Azure Active Directory (
17
17
18
18
## Step 1: Review the differences between the APIs
19
19
20
-
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.
20
+
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.
21
21
22
-
Nonetheless, there are differences. Certain resources, properties, methods, and core capabilities changed.
22
+
However, there are differences where some resources, properties, methods, and core capabilities have changed.
23
23
24
-
Specifically, look for differences in the following areas:
24
+
Look for differences in the following areas:
25
25
26
-
-[Request call syntax](migrate-azure-ad-graph-request-differences.md) between the two services
27
-
-[Feature differences](migrate-azure-ad-graph-feature-differences.md), such as directory extensions, batching, differential queries, and so on
28
-
-[Entity resource names](migrate-azure-ad-graph-resource-differences.md) and their types
29
-
-[Properties](migrate-azure-ad-graph-property-differences.md) of request and response objects
30
-
-[Methods](migrate-azure-ad-graph-method-differences.md), including parameters and types
[Examine the APIs](migrate-azure-ad-graph-audit-api-use.md) used by your app, the permissions they require, and compare to the list of known differences.
36
36
37
-
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.
37
+
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.
38
38
39
-
For testing, use [Graph Explorer](https://aka.ms/ge) 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.
39
+
For testing, use [Graph Explorer](https://aka.ms/ge) 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.
40
40
41
41
## Step 3: Review app details
42
42
@@ -46,7 +46,7 @@ For testing, use [Graph Explorer](https://aka.ms/ge) to experiment with API call
46
46
47
47
## Step 4: Deploy, test, and extend your app
48
48
49
-
Before updating your app for production, ensure you test thoroughly and stage your rollout to your customer audience.
49
+
Before updating your app for production, thoroughly test it and stage the rollout to your customer audience.
50
50
51
51
After switching to Microsoft Graph, you unlock many more datasets and features that are defined in [Major services and features in Microsoft Graph](./overview-major-services.md).
0 commit comments