Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article describes implementation and operational limits for Microsoft Graph connectors. Keep these limits in mind when designing connectors.
| Limit type | Limit |
|---|---|
| Properties that can be defined in a schema, characterizing the data ingested through a connection | 128 |
| Limit type | Limit |
|---|---|
| External groups per Microsoft 365 tenant | 100,000 |
| Requests allowed per second (requests/sec) in the group administration throttling threshold | 1,000 |
| External groups per user for search query | 10,000 |
| Limit type | Limit |
|---|---|
| Item size; this limit applies to the request body when ingesting and indexing an item | 4 MB |
| Number of activities; this is the throttling threshold per activities call | 20 activities |
| Property size | N/A |
Note: The 4 MB item size limit refers to the total size of parsed text content that is typically 10% of the original file size for common formats (for example, docx, ppt, and PDF). To contextualize, 4 MB equals 4,000,000 bytes that translates to approximately 600K-700K words or 1,400 pages (averaging 500 words per page).
When a throttling threshold is exceeded, Microsoft Graph limits any further requests from that client for a period of time. When throttling occurs, Microsoft Graph returns HTTP status code 429 (Too many requests), and the requests fail. 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 you have a high volume of requests, all request 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.