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

Understanding scan buckets and parallel scanning

Last updated Scanning

AI summary

Rencore Governance groups connectors into scan buckets to prevent overloading shared resources like Microsoft APIs. Only one connector per bucket runs at a time, but connectors from different buckets run in parallel. Understanding buckets helps you predict scan timing, see which connectors run together, and identify when paused scans block others.

Rencore Governance scans your Microsoft 365 tenant by running jobs against many different connectors: SharePoint, Teams, Power Platform, Entra ID, and so on. To keep scans fast and to avoid hitting Microsoft API throttling limits, those connectors are organised into scan buckets.

This page explains what scan buckets are, how parallel scanning works across them, and which connectors belong to which bucket by default.

Why connectors are grouped into buckets

Some connectors use the same Microsoft API. SharePoint and OneDrive, for example, both call the same SharePoint REST endpoints, and Microsoft 365 and Teams both rely on Microsoft Graph. Scanning them at the same time would make Microsoft slow both down. So Rencore Governance puts them in the same group, a scan bucket, and scans them one after the other.

A bucket is a group of connectors that should not run in parallel because they share resources. Connectors in different buckets can run at the same time without interfering with each other.

How parallel scanning works

Rencore Governance schedules scans according to two rules:

  1. Only one connector from any given bucket runs at a time.
  2. Connectors from different buckets can run in parallel.

So if “Microsoft 365”, “Power Apps”, and “OneDrive” are each in different buckets, all three can scan concurrently. But “Microsoft 365” and “Teams”, both in the same bucket, will scan one after the other, never simultaneously.

Example: a parallel scan window might run "Microsoft 365 + Power Automate + Power BI + OneDrive + Azure" all at once, because each connector comes from a different bucket. But the scheduler will never run "Microsoft 365 + Teams" together, because they share Bucket 1.

Connectors in each bucket

The default grouping is:

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

Why this matters for you

Understanding the bucket model helps in three situations:

  • When you see scans running concurrently in the scan history and want to know why some combinations appear together and others do not.
  • When you are estimating how long a full scan cycle takes across all enabled connectors in your tenant. Connectors in the same bucket scan sequentially, so the total time is driven by the slowest bucket, not by the sum of all individual scans.
  • Knowing that a paused or running scan will block other scans in the same bucket until complete.

Frequently asked questions

Why do some connectors scan in parallel and others sequentially?

Connectors that share Microsoft APIs are grouped into buckets. Only one connector per bucket runs at a time to avoid throttling, but different buckets run in parallel.

Can we scan Teams and Microsoft 365 at the same time?

No. Teams and Microsoft 365 are both in Bucket 1 and share Microsoft Graph resources, so they scan one after the other.

How long will a complete scan cycle take?

The total time is determined by the slowest bucket, not the sum of individual scans, since connectors within a bucket scan sequentially.

Will a paused scan delay other scans?

Yes. A paused or running scan blocks other scans in the same bucket from starting.

Can Power Apps and Power Automate scan at the same time?

No. Power Apps and Power Automate are both in Bucket 2, so they scan one after the other.