Microsoft Graph throttling behavior when processing driveItems in parallel

Question

When fetching driveItems across multiple SharePoint/OneDrive sites using Microsoft Graph,

1. Is throttling enforced per site/drive or shared across the app + tenant + SharePoint workload?
2. For parallel processing, are there any recommended concurrency limits or best practices to avoid throttling?
3. Does a throttling response (429 / 503) generally indicate a global workload-level limit (SharePoint/OneDrive) rather than an isolated site-level limit?

Answer 1

Hi @Yuvan Kesav A

Thank you for posting your question in the Microsoft Q&A forum. 

Based on Microsoft’s guidance, here are some clarifications for your questions: 

1.Throttling scope across sites, drives, and workloads

Throttling is not scoped to individual sites or drives. Microsoft Graph enforces multi‑layered limits, and SharePoint/OneDrive evaluate requests across several scopes simultaneously: 

-Tenant‑level 

-App + tenant combination 

-Service‑specific (SharePoint/OneDrive) 

This means that even if requests target different sites or drives, they often draw from the same backend quota bucket. 

Reference: Microsoft Graph service-specific throttling limits - Microsoft Graph | Microsoft Learn. 

2.Best practices for parallel processing and avoiding throttling

-Honor Retry‑After when receiving 429/503 responses. Ignoring it worsens throttling since rejected requests still count against quota. 

-Use $batch to combine multiple requests into a single call, reducing bursts of traffic. 

-Leverage delta queries and change notifications instead of repeatedly polling large datasets, which lowers overall request volume. 

References: 

• Microsoft Graph throttling guidance - Microsoft Graph | Microsoft Learn. 
• Graph API - how to avoid throttling. 

3.Meaning of throttling responses (429/503)

For SharePoint/OneDrive via Microsoft Graph: 

-429 (Too Many Requests): Indicates a rate limit exceeded, typically at the app‑tenant or workload level. 

-503 (Server Too Busy): Reflects service‑level load, often workload‑wide rather than site‑specific. 

This documentation Avoid getting throttled or blocked in SharePoint Online | Microsoft Learn confirms these codes represent service‑level throttling, not isolated site/drive limits. 

I hope this information is helpful. 

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.