Additional Microsoft Entra services and features related to identity, access, and network security
Reduce the Audit or Sign-in logs query to smaller date-range chunks; Microsoft documents this exact portal symptom as HTTP 429 throttling that varies with current system demand, rather than necessarily indicating excessive activity from your tenant.^1^
Immediate workaround
- Open Microsoft Entra admin center → Entra ID → Monitoring & health → Audit logs or Sign-in logs.
- Change the date filter to a shorter period—for example, reduce a month to seven days, then one day if necessary.
- Run each successive date range separately until the required period is covered.
- Download each successful result using Download → CSV or JSON. At least Reports Reader is required to access and download these logs.^2^
There is no fixed date range guaranteed to work: the successful range can vary by tenant and current service demand. Repeatedly submitting the same large query is therefore unlikely to help while throttling continues.
Check whether this is a current Microsoft incident
A matching multi-tenant Entra sign-in-log problem was previously confirmed by Microsoft engineering and subsequently marked resolved. That confirms that this message can result from a service-side incident, but it does not establish that the current occurrence is the same incident.^3^
Check the tenant-specific dashboard:
- Open Microsoft 365 admin center → Health → Service health.
- Review Active issues Microsoft is working on.
- Check Issue history for the period when the problem began.
- If no relevant Entra incident appears, select Report an issue.
Service Health is tenant-aware and is more authoritative for determining whether Microsoft has identified an incident affecting your organization.^4^
Prevent recurring portal-query throttling
If these logs are required regularly for security investigations, stream them to Log Analytics rather than relying on large portal queries:
- Sign in with at least Security Administrator.
- Go to Entra ID → Monitoring & health → Diagnostic settings.
- Create or edit a diagnostic setting.
- Select the required audit and sign-in log categories.
- Select Send to Log Analytics workspace, choose the workspace, and save.
- Query future events through Entra ID → Monitoring & health → Log Analytics.
Microsoft specifically recommends Log Analytics to avoid throttling affecting Entra admin center and Microsoft Graph activity-log queries.^1^ Diagnostic settings collect events after configuration; they do not recover historical events that were never routed there.
Escalate the persistent failure
Because this has continued for two weeks, open a support request if no matching Service Health advisory exists:
- In the Entra admin center, select Diagnose and solve problems.
- Run Self-Service Support and describe the Audit/Sign-in log HTTP 429 behavior.
- Choose Create a support request if it remains unresolved.
- Include:
- UTC start time and frequency
- Affected Audit and Sign-in log blades
- Date ranges that succeed and fail
- Whether multiple administrators, users, or tenants are affected
- Screenshots and browser network traces showing HTTP 429
- Correlation/request/session IDs shown by the portal
A Service Support Administrator can create an Entra support request, and Microsoft may collect Entra audit, sign-in, configuration, and service-health telemetry during investigation.^5^ ^6^
References