Microsoft Entra Id - Sign In Log API Latency

Question

Hello Team,

We had observed that, there is latency of Sign-In API almost 10 times (25s) as compared to other APIs(Directory and Provisioning). Do we have any specific reason for this, could you please let us know.

Audit Log Reference: Activity reports API overview - Microsoft Graph v1.0 | Microsoft Learn

Thanks,
Ravi P.

Answer 1

Hi @Ron Weasley , the latency of the Sign-In API in Microsoft Entra ID could be due to several reasons. One possible reason is that the Sign-In API may be processing a larger volume of requests compared to the other APIs, which can result in longer response times. Another reason could be that the Sign-In API is more complex and requires more processing time to retrieve the necessary data. Have you tried different queries to see if the results vary?

It's also possible that the latency is caused by network issues or other factors outside of the API itself. For example, if the network connection between your application and the API is slow or unreliable, this can result in longer response times.

To determine the root cause of the latency, you can try monitoring the performance of the API using tools such as Azure Monitor or Application Insights. These tools can help you identify any bottlenecks or performance issues that may be causing the latency. You can also try optimizing your application code to reduce the number of requests to the API or to improve the efficiency of the requests.

Please let me know if you have any questions and I can help you further.

If this answer helps you please mark "Accept Answer" so other users can reference it.

Thank you,

James

Answer 2

Hi , Dose Sign-In API for Entra ID has the large latency ,

1. Do we have any documentation around it.
2. Dose it has anything to do with Account/License configured.
3. Are there any settings around we can change to reduce the API latency

we are just trying to hit the Sign-In API in Microsoft Entra ID with single request. (Please see below example).

The latency goes on increasing as the number of results to be fetched goes on increasing ($top). i.e.

1. For $top=100 it takes about 6 sec to process the response.
2. For $top=1000 it takes about 30+ seconds.

Is it the expected behavior for Sign-In API to have such large latency.

https://graph.microsoft.com/v1.0/auditLogs/signIns?$filter=createdDateTime ge 2024-05-06T09:29:02Z and createdDateTime le 2024-06-10T09:29:02Z&$top=1000