Error Details
| Fact | Value | Source |
|---|---|---|
| Exact error string | 429 Too Many Requests — The user, app or site has exceeded the request rate limit. | SharePoint admin centre > Reports > SharePoint usage |
| Affected build range | SharePoint Online / Microsoft 365 | Microsoft documentation |
| Registry key involved | N/A - no registry key for this issue | Not applicable |
| Relevant service/endpoint URL | https://admin.microsoft.com/sharepoint/admin/reports/usage | SharePoint admin centre |
| Log line signature | Correlation ID in 429 response header | ULS logs |
Log Files to Check
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\LOGS\W3SVC<#>
What This Error Actually Means
The HTTP status code "429 Too Many Requests" is raised by SharePoint Online's resource management layer when a client (such as a browser, application, or flow) has exceeded the request rate limit imposed on it. This error indicates that the user, app, or site in question has made too many requests within a short period of time, causing the system to throttle further requests until the Retry-After header's specified interval is observed. The exact message returned by SharePoint Online is "429 Too Many Requests — The user, app or site has exceeded the request rate limit." This error is designed to prevent overloading the server and ensuring fair usage across all users.Affected Versions and Scope
This issue affects all versions of SharePoint Online within Microsoft 365. It applies universally across all tenants regardless of their specific build or configuration, as throttling limits are a feature of the service itself rather than an optional component that can be disabled or altered by tenant administrators. However, certain configurations and usage patterns may make some sites more prone to hitting these limits compared to others.Where To Look First: Logs and Event IDs
To diagnose this issue, you should first look at the SharePoint admin center's reports section for any high error rates in site usage under 'Files'. Additionally, Azure Monitor or Application Insights can be used if your client application is instrumented to capture dependency traces. For PowerShell diagnostics, connect to your tenant using PnP PowerShell withConnect-PnPOnline -Url "https://tenant.sharepoint.com" -Interactive. Then run Get-PnPTenantSite -Detailed | Select-Object Url,StorageUsed to identify high-traffic sites that may be nearing their quota and experiencing elevated 429 rates.
Root Causes
Power Automate Flows or Power Apps Polling at Sub-Minute Intervals
One common cause of this error is when a Power Automate flow or Power App polls SharePoint more frequently than once per minute without implementing exponential backoff. To identify if this is the issue, check your flows and apps for any that are configured to make requests too quickly.
Custom SPFx Web Parts Making Too Many REST Calls
Another cause can be custom SPFx web parts making excessive REST API calls during page loads. This often occurs when a web part attempts to load large amounts of data or interacts with multiple lists and libraries simultaneously, leading to throttling due to the high volume of requests.
Migration Tools Running Too Many Concurrent Threads
Migration tools like ShareGate or AvePoint can also trigger this error if they are configured to run too many threads concurrently. Each thread makes numerous API calls which collectively exceed the rate limit imposed by SharePoint Online, leading to throttling.
Fix Procedure
To address the issue of excessive requests and mitigate 429 errors, follow these steps:
1. Connect to your tenant using PnP PowerShell: Connect-PnPOnline -Url "https://tenant.sharepoint.com" -Interactive.
2. Identify high-traffic sites by running Get-PnPTenantSite -Detailed | Select-Object Url,StorageUsed. Focus on sites with elevated 429 rates.
3. Review and adjust Power Automate flows to implement exponential backoff using the Wait for Duration action.
4. For custom SPFx web parts, optimize REST API calls by reducing the number of simultaneous requests or batching them together.
5. Configure migration tools to run fewer concurrent threads or distribute tasks across multiple sessions.
Error Code Variants
| HTTP Status Code | Description | Distinguishing Features |
|---|---|---|
403 Forbidden |
User lacks necessary permissions to access the resource. | No Retry-After header is present, and error messages indicate permission issues rather than rate limiting. |
503 Service Unavailable |
The server is temporarily overloaded or down for maintenance. | Error message indicates temporary unavailability of the service, not exceeding request limits. |
Verification
After implementing changes to reduce excessive requests, verify that the issue has been resolved by checking the SharePoint admin center's reports section again for any high error rates in site usage. Additionally, use PowerShell cmdlets likeGet-PnPUnifiedAuditLog -ContentType SharePoint -StartTime (Get-Date).AddDays(-7) to review recent audit logs and confirm that no 429 errors are being recorded.
Prevention
To prevent recurrence of this issue, establish policies for Power Automate flows and custom SPFx web parts that enforce a maximum number of concurrent requests or implement exponential backoff. Additionally, configure migration tools to run fewer threads concurrently and monitor high-traffic sites regularly using PowerShell cmdlets likeGet-PnPTenantSite -Detailed | Select-Object Url,StorageUsed.
Be cautious when modifying site permissions via PowerShell as this can break enrolled devices if not done correctly.
A non-obvious diagnostic shortcut is to use the Unified Audit Log in SharePoint admin center > Reports > Usage > SharePoint for detailed insights into access and permission changes that may correlate with 429 errors.