Skip to content

Commit afc7f74

Browse files
authored
Merge pull request #26126 from msewaweru/freshness-migrate-graph-checklist
Freshness pass: Azure AD Graph migration planning checklist
2 parents a63d879 + ca54c8d commit afc7f74

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

concepts/migrate-azure-ad-graph-planning-checklist.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: krbash
77
ms.topic: quickstart
88
ms.localizationpriority: medium
99
ms.subservice: entra-applications
10-
ms.date: 01/12/2024
10+
ms.date: 01/20/2025
1111
#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?
1212
---
1313

@@ -17,26 +17,26 @@ Use the following checklist to plan your migration from Azure Active Directory (
1717

1818
## Step 1: Review the differences between the APIs
1919

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.
2121

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.
2323

24-
Specifically, look for differences in the following areas:
24+
Look for differences in the following areas:
2525

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
31-
- [Permissions](migrate-azure-ad-graph-permissions-differences.md)
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.
31+
- [Permissions](migrate-azure-ad-graph-permissions-differences.md).
3232

3333
## Step 2: Examine API use
3434

3535
[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.
3636

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.
3838

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.
4040

4141
## Step 3: Review app details
4242

@@ -46,7 +46,7 @@ For testing, use [Graph Explorer](https://aka.ms/ge) to experiment with API call
4646

4747
## Step 4: Deploy, test, and extend your app
4848

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.
5050

5151
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).
5252

0 commit comments

Comments
 (0)