Scan bucket
Also known as: parallel scanning
A scan bucket is a group of connectors that never scan at the same time because they share the same Microsoft APIs. Connectors from different buckets scan in parallel.
Rencore Governance runs one connector per bucket at a time. This keeps scans fast without making connectors compete for the same request quota, which would trigger Microsoft throttling.
Buckets decide which connectors scan side by side. You do not configure them, but they explain why a connector can wait for another one before it starts.
For example, OneDrive and SharePoint share a bucket, so a long SharePoint scan delays the OneDrive scan, while Teams and Power Apps can scan at the same time.
Default buckets
| Bucket | Connectors |
|---|---|
| 1 | Microsoft 365, Teams, Entra ID, Planner |
| 2 | Power Apps, Power Automate |
| 3 | Power BI, Viva Engage, Exchange, Copilot Studio, Microsoft 365 Copilot |
| 4 | OneDrive, SharePoint |
| 5 | Azure |
Connectors in the same bucket scan one after the other, so the slowest bucket sets the length of a full scan cycle.
Was this page helpful?
Thanks for the feedback.
Thanks. What was wrong?