|
1 | 1 | --- |
2 | 2 | title: 404 Error When Managing Objects Using Microsoft Graph |
3 | | -description: Provides a solution to a 404 error when you try to manage a Microsoft Entra object that's just created using Microsoft Graph. |
| 3 | +description: Provides a solution to a 404 error when you try to manage a Microsoft Entra object that was just created using Microsoft Graph. |
4 | 4 | ms.date: 01/07/2025 |
5 | 5 | ms.reviewer: kakapans, v-weizhu |
6 | 6 | ms.service: entra-id |
7 | 7 | ms.custom: sap:Problem with querying or provisioning resources |
8 | 8 | --- |
9 | 9 | # 404 error when managing objects using Microsoft Graph |
10 | 10 |
|
11 | | -This article provides a solution to a 404 (object not found) error that occurs when you try to manage a Microsoft Entra object that's just created using Microsoft Graph. |
| 11 | +This article provides a solution to a 404 (object not found) error that occurs when you try to manage a Microsoft Entra object that was just created using Microsoft Graph. |
12 | 12 |
|
13 | 13 | ## Symptoms |
14 | 14 |
|
15 | | -Assume that you create an object, such as a user, group, or application, in Microsoft Entra ID using Microsoft Graph. When trying to manage the object, such as get, update or patch it, shortly after its creation, you get a 404 (object not found) error. |
| 15 | +Suppose you create an object, such as a user, group, or application, in Microsoft Entra ID using Microsoft Graph. When trying to manage the object, such as getting, updating, or patching it, shortly after its creation, you receive a 404 (object not found) error. |
16 | 16 |
|
17 | 17 | ## Cause |
18 | 18 |
|
19 | | -[Microsoft Entra ID architecture](/entra/architecture/architecture) ensures that all data is replicated across geographically distributed data centers. This issue occurs due to a replication delay for the newly created object to be propagated across all data centers. It can take several minutes for this replication process to complete. |
| 19 | +The [Microsoft Entra ID architecture](/entra/architecture/architecture) ensures that all data is replicated across geographically distributed data centers. This issue occurs due to a replication delay in propagating the newly created object across all data centers. This replication process might take several minutes to complete. |
20 | 20 |
|
21 | | -As shown in the following diagram, when your application makes a request via Microsoft Graph to create a user in Microsoft Entra ID, the service begins the replication process and returns an object for that user, which includes the user's ID and other relevant data used in your request. If your application immediately attempts to update this user, it might connect with a replica that hasn't been updated with the new user object yet. Consequently, you receive a 404 error because the user isn't found on that replica. |
| 21 | +As shown in the following diagram, when your application makes a request via Microsoft Graph to create a user in Microsoft Entra ID, the service begins the replication process and returns an object for that user, which includes the user's ID and other relevant data used in your request. If your application immediately tries to update this user, it might connect to a replica that hasn't yet been updated with the new user object. So, you receive a 404 error because the user isn't found on that replica. |
22 | 22 |
|
23 | 23 | :::image type="content" source="media/404-not-found-error-manage-objects-microsoft-graph/404-not-found-error-diagram.png" alt-text="Diagram that explains the cause of the 404 error."::: |
24 | 24 |
|
25 | 25 | ## Solution |
26 | 26 |
|
27 | | -To resolve this issue, wait for some time and then retry the update request. If the 404 error still occurs upon retrying, increase your waiting time by doubling it before attempting again. By allowing sufficient time for replication, you can prevent further occurrences of this error. |
| 27 | +To resolve this issue, wait some time and retry the update request. If the 404 error still occurs after retrying, double your waiting time and try again. By allowing sufficient time for replication, you can prevent this error from happening again. |
28 | 28 |
|
29 | 29 | [!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)] |
0 commit comments