How to fix delay data from Graph API?

Jackie Dinh 20 Reputation points
2025-07-01T05:54:14.1366667+00:00

Assuming the initial list has UserA, and then I successfully add UserB, then I will immediately get the user list back. This causes a problem because the Graph has not been updated with the latest data that includes both UserA and UserB. After adding, when I retrieve the detail immediately, it only shows UserA, but then if I get it again, it shows both UserA and UserB. Is there any way to fix this?

This is Graph API that I'm used:
var result = await graphClient.Groups["{group-id}"].Members.GetAsync();

Microsoft Teams | Development
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Flora-T 1,135 Reputation points Microsoft External Staff Moderator
    2025-07-01T12:43:59.1866667+00:00

    Hi @Jackie Dinh 

    Welcome to Microsoft Q&A Forum. 

    I understand how frustrating these kinds of issues can be, and I truly appreciate you taking the time to describe your scenario.

    Based on Microsoft documentation and community experience, brief delays after changes, such as adding or removing users, are expected in large-scale cloud systems like Microsoft Entra ID. These delays are by design to ensure consistency and reliability across distributed servers. It is acknowledged that short sync delays (a few seconds to minutes) are normal in such environments.

    To work around this, please try the following: after adding UserB, wait 5-10s before retrieving the member list.

    However, accessibility and user experience remain top priorities, and feedback like yours is essential to improving the platform. I strongly encourage you to share your input on the Microsoft Feedback Portal so the product team can review and consider your experience.

    I truly appreciate your patience and understanding. If you need any more clarification, please don’t hesitate to ask, I’m here to assist however I can.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


  2. Prasad-MSFT 9,071 Reputation points Microsoft External Staff Moderator
    2025-07-01T13:13:12.64+00:00

    This is a known behavior with Microsoft Graph API: directory changes (like adding/removing group members) are not always immediately reflected in subsequent read operations due to eventual consistency and backend replication delays.

    There is no way to force immediate consistency in Microsoft Graph. Use retry logic with a delay or subscribe to change notifications for a more robust solution. This is expected behavior for directory operations in Microsoft 365.

    Thanks, 

    Prasad Das

    ************************************************************************* 

    If the response is helpful, please click on "upvote" button. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.