Skip to content

Commit a63d879

Browse files
authored
Merge pull request #26131 from msewaweru/freshness-request-differences
Freshness: Request differences
2 parents 0890a15 + 0185faf commit a63d879

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

concepts/migrate-azure-ad-graph-request-differences.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,8 @@ ms.author: ombongifaith
66
ms.reviewer: krbash
77
ms.localizationpriority: medium
88
ms.subservice: "entra-applications"
9-
ms.date: 01/12/2024
9+
ms.date: 01/21/2025
10+
1011
#Customer intent: As a developer, I want to understand how REST API endpoints differ between Azure AD Graph and Microsoft Graph, so that I can update my code accordingly as I migrate my app from Azure AD Graph to Microsoft Graph.
1112
---
1213

@@ -54,7 +55,7 @@ In addition to the primary key, some entities support an alternate key identifie
5455

5556
It's a best practice to only request the properties your app really needs. Use the `$select` query parameter, in GET requests, to customize the response to include only the properties that your app requires.
5657

57-
In some cases in Microsoft Graph, for example, the **GET** or **LIST** operations for **user** and **group** resources, only a subset of all properties are returned. These _default properties_ represent the most commonly used properties for the resources. On the other hand, Azure AD Graph returns the full set of all properties for the respective resource. Where the resource returns only the default properties, your app needs to explicitly request other properties using the `$select` query parameter.
58+
In some cases in Microsoft Graph, for example, the **GET** or **LIST** operations for **user** and **group** resources, only a subset of all properties are returned. These *default properties* represent the most commonly used properties for the resources. On the other hand, Azure AD Graph returns the full set of all properties for the respective resource. Where the resource returns only the default properties, your app needs to explicitly request other properties using the `$select` query parameter.
5859

5960
To illustrate the difference, use Graph Explorer to run the following requests and compare the different responses.
6061

@@ -72,7 +73,7 @@ https://graph.microsoft.com/v1.0/me?$select=displayName,streetAddress,city,state
7273
To learn more about:
7374

7475
- Default properties on user and group resources, see [users](/graph/api/resources/users) and [groups](/graph/api/resources/groups-overview)
75-
- The `$select` parameter and other supported ODATA query parameters, see [Use query parameters to customize responses](./query-parameters.md).
76+
- The `$select` parameter and other supported OData query parameters, see [Use query parameters to customize responses](./query-parameters.md).
7677
- Other recommended optimizations, see [Best practices](./best-practices-concept.md).
7778

7879
## Relationships and navigation properties

0 commit comments

Comments
 (0)