Performance and parallelism
Sixteen seconds for a full pass is a setting, not luck. Here is what the knobs do — and what they can never break.
Parallel controls
Audits run several controls simultaneously: the default is eight, adjustable from one to sixteen in the performance settings. More parallelism shortens the run on fast machines and fast tenants; less makes the progress easier to follow on modest hardware.
The built-in benchmark
Rather than guessing, run the benchmark: it measures your actual machine and connection against a sample workload and recommends the optimum. Two minutes, once per workstation.
Why you cannot throttle a client tenant
The Graph and Exchange connectors self-limit regardless of the parallelism setting: they respect the services' rate limits, back off on throttling responses and retry politely. The worst case of an over-ambitious setting is a slower audit — never a hammered tenant. That guarantee matters when the tenant belongs to your client.
Recommendation. Run the benchmark once, accept its suggestion, and forget about it. Revisit only if you change machine or audit very large tenants.