rencore.com (opens in a new tab) Start a trial (opens in a new tab)

Throttling by Microsoft 365

Last updated Scanning

AI summary

Microsoft 365 throttles applications that send too many requests to maintain service performance, causing requests to fail. Rencore Governance is built to work within these limits by sending requests at a steady, low rate throughout the day and pausing when needed, though throttling can occasionally occur with very large file libraries, drives, or audit logs. You can disable retrieval of specific data types to further reduce throttling risk if needed.

What is throttling?

Microsoft 365 uses throttling to maintain optimal performance and reliability of the service. Throttling limits the number of user or application requests or concurrent calls (by script or code) to prevent the overuse of resources.

That said, it is rare for a user to get throttled by Microsoft 365. The service is robust, and it is designed to handle high volumes.

For an application like Rencore Governance or any other 3rd party application that performs a larger amount of requests, throttling can occur if not handled properly.

What is throttling?

Common throttling scenarios

The most common causes of throttling of clients include:

  • A large number of requests across all applications in a tenant.
  • A large number of requests from a particular application across all tenants.

What happens when throttling occurs?

When a throttling threshold is exceeded, Microsoft 365 limits any further requests from that client/application for a period of time. When throttling occurs, Microsoft 365 returns the HTTP status code 429 (Too many requests), and the requests fail.

Microsoft Graph

“When a throttling threshold is exceeded, Microsoft Graph limits any further requests from that client for a period of time.” (Microsoft)

Microsoft SharePoint

“SharePoint Online uses throttling to maintain optimal performance and reliability of the SharePoint Online service. Throttling limits the number of API calls or operations within a time window to prevent overuse of resources.” (Microsoft)

A suggested wait time is returned in the response header of the failed request. Throttling behavior can depend on the type and number of requests. For example, if the application has a high volume of requests, all requests types are throttled. Threshold limits vary based on the request type. Therefore, you could encounter a scenario where writes are throttled but reads are still permitted.

How does Rencore Governance avoid throttling?

Rencore Governance is developed to work within the throttling limits by Microsoft. It reduces the load on the tenant by adjusting scan frequency, speed, and volume to remain below the limits.

Rencore uses a continuous scanning approach and scans your tenant in batches with partial scanning.

Microsoft limits how many requests an app can send. Rencore Governance stays under that limit: it sends requests at a steady, low rate throughout the day, without peaks. If Microsoft still asks it to slow down, it pauses for the time Microsoft gives, waits a little longer, then carries on.

Nothing already scanned is lost. Your Microsoft 365 tenant and your users notice nothing. Only the data in Rencore Governance takes longer to update.

Rencore’s approach has been successfully tested with very large Microsoft 365 tenants (over 250,000 users) and has seen throttling only happen in rare cases when retrieving:

  • file metadata from very large libraries in SharePoint.
  • file metadata from very large drives in OneDrive.
  • audit log information from Entra ID. If any of those entities are not relevant for the customer to be retrieved, they can also individually be disabled to further reduce the risk of throttling.

Resources

Handling of throttling according to MS:


Frequently asked questions

What happens when Microsoft 365 throttles requests from Rencore Governance?

Microsoft 365 limits further requests from the application for a period of time and returns HTTP status code 429 (Too many requests). The requests fail, and the response header contains a suggested wait time.

Will users in my Microsoft 365 tenant notice throttling caused by Rencore Governance?

No. Your Microsoft 365 tenant and your users notice nothing. If Rencore Governance has to slow down, only the data in Rencore Governance takes longer to update, and nothing already scanned is lost.

How does Rencore Governance stay below Microsoft throttling limits?

Rencore Governance adjusts scan frequency, speed, and volume, and scans your tenant in batches with partial scanning. It sends requests at a steady, low rate throughout the day without peaks. If Microsoft asks it to slow down, it pauses for the given time, waits a little longer, then carries on.

When can throttling still happen with Rencore Governance?

Throttling has only happened in rare cases, even in tenants with over 250,000 users. These cases involve retrieving file metadata from very large SharePoint libraries, file metadata from very large OneDrive drives, or audit log information from Entra ID.

Can I reduce the risk of throttling by turning off certain data retrieval?

Yes. If some entities are not relevant for you, they can be disabled individually to further reduce the risk of throttling.