Why delete an access package assignment via API take a long time than via UI

Question

Follow this article https://learn.microsoft.com/en-us/graph/api/entitlementmanagement-post-accesspackageassignmentrequests?view=graph-rest-beta&tabs=http#example-4-remove-an-assignment

I have successfully created a request to remove an access package assignment like the one below

the result is a request with the state is 'submitted' and the status is 'Accepted', but I monitoring that the assignment will be removed after more than 5 minutes of waiting. If I manually remove the assignment via UI the assignment will be removed very fast(less than 3 seconds) and the request status will be changed delivered very quickly. So the question is does removing the access package assignment via API request take more time than removing this one via UI manually? If not how to remove it via API call quickly, and which option or parameter will be included?

Answer 1

Hi @Tuan Le ,

While that sort of latency is not typical, the latency for these types of updates can depend on some factors that may not apply in the Azure portal. For example, the service load, latency in the network, or other factors specific to your environment.

Microsoft Graph does have some throttling limits as well that can be impacted by the request type, the scope of the request, and the current load and health of the service itself. https://learn.microsoft.com/en-us/graph/throttling-limits

If you are able to provide a fiddler trace it may be easier to isolate the exact cause of the latency.