Skip to main content

Optimizing MS365 throughput: "sweet spot" for Azure apps and streams?

  • September 2, 2026
  • 1 reply
  • 37 views

Unique display name
Novice
Forum|alt.badge.img+1

(CV11.40.67 - self hosted)

Has anyone found a "sweet spot" or a good ratio for the number of azure apps and streams for large exchange/Sharepoint jobs ?

Before, adding more apps and streams at our large sharepoint and Exchange jobs improved the throughput. but I have read that Microsoft has become much stricter with throttling recently, also that using too many apps/streams might have the opposite effect and degrade the performance.

When reviewing a recent sharepoint job, the tab where we can see throttling showed only 6 minutes of throttling. That seems like not so much, so I am not sure if Microsoft throttling is actually my bottleneck here.

I tested the theory that fewer streams might perform better under the new Microsoft limits, I reduced the streams from 10 to 5. Unfortunately, this resulted in lower throughput.

When I see only 6 minutes throttling time reported by CV, should I be looking elsewhere for the bottleneck rather than focusing on Microsoft throttling?

When observing the access node and index server during a backup job, I am not observing any errors, congestion or overload. The RAM and CPU usage is stable.

1 reply

Paul G
Explorer
Forum|alt.badge.img+2
  • Explorer
  • September 8, 2026

Hi ​@Unique display name,

As far as I know, Microsoft applies throttling tenant-wide so increasing or reducing the amount of apps should not meaningfully change the amount of throttling.

I have found that I see more throttling when exchange and sharepoint backups run at the same time. having these jobs more separated might help increase performance or reduce throttling.

There can also be limits (without throttling) to the speed you can get out of an Microsoft API.

Kind regards,

Paul