MS graph api to list the sensitivity labels returning the stale sensitivity labels

Vimal Dhaduk 20 Reputation points
2024-10-16T14:14:01.9866667+00:00

We are using the MS graph api to get the sensitivity label. API url: https://graph.microsoft.com/beta/me/security/informationProtection/sensitivityLabels Documentation: https://video2.skills-academy.com/en-us/graph/api/security-informationprotection-list-sensitivitylabels?view=graph-rest-beta&tabs=http We configured the sensitivity labels for the information protection and published the policy for all users in the tenant. We are using the EntraID app to authorize and get the token to call the MS Graph api. When user User1 uses MS graph api by her token, she received the stale labels While user User2 got the latest label. We made sure that labels are published after 48 hours, The user User1 was getting the stale data and at the same time when User2 hit the api with his token, he received the latest labels. After 2 hours user User1 was getting the latest labels. I am wondering two users in the same tenant using their own token getting one getting the latest and another one getting the stale data, without doing anything it fixed and both user getting the latest labels. This is a real concerns. Is there any issue from Microsoft needs to check and verify?

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
12,266 questions
Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,222 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Prathista Ilango 0 Reputation points Microsoft Employee
    2024-11-06T10:09:25.4766667+00:00

    Hello Vimal,
    This behavior might be due to the caching mechanism used by Microsoft Graph API, which could result in some delay before changes are reflected. Possibly, one of the user's requests was served from a cached response (resulting in stale label), while the other user got it from the data source (resulting in latest label).

    I see you have already waited for 48 hours but at times, if your tenant spans multiple regions or availability zones, replication delays can sometimes lead to inconsistency in API responses.

    Hope that clarifies. If this is not a one-off occurrence and seems to happen consistently with predictable delay, I would suggest getting in touch with Microsoft Support.

    If you found the information above helpful, please Accept the answer. This will assist others in the community who encounter a similar issue, enabling them to quickly find the solution and benefit from the guidance provided.

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.