Forum Discussion
Increasing Microsoft Graph Per-Mailbox Throttling Limits (PUT/POST/PATCH & Concurrency)
I am referring to the per-mailbox throttling limits documented here: https://learn.microsoft.com/en-us/graph/throttling-limits#limits-per-mailbox
Specifically:
- 150 MB limit for PUT/POST/PATCH requests within a 5-minute window
- 4 concurrent requests per mailbox
In a multi-tenant SaaS application scenario, these limits can become restrictive when processing large volumes of mailbox data.
I would like clarification on the following:
- Is it possible to request an increase in these per-mailbox limits through Microsoft (e.g., via support or a formal quota increase request)?
- Are there recommended architectural patterns or best practices to efficiently handle high-throughput scenarios while staying within these limits?
- Can tenant administrators (our customers) configure or influence these limits through Microsoft 365 admin settings?
Any official guidance or recommendations would be highly appreciated
1 Reply
There is no straightforward answer to this as a lot depends on the specifics what you are doing and how often it occurs. It also depends on the size of the tenant and the other things that are happening within that tenant (at Graph level). For instance, is this a continuous thing, is it in bursts is it for a migration scenario?
Also, are there other ways of doing this which wouldn't exhaust your endpoints? This isn't just about optimizing your Graph calls, but also looking at (native) alternatives such as Power Automate.
The best way to go about this would be to contact your TAM at Microsoft and also create a support request. If it is actually for your customer's tenants, have them do the same thing. Valid use cases are usually considered, and you might even get some tips along the way when working with the correct engineers.
If this is about data extraction, consider Microsoft Graph Data Connect as an alternative;
Microsoft Graph Data Connect overview - Microsoft Graph | Microsoft Learn
