# What happens at your volume?

> What degrades first at scale depends on the storage provider, not the integration layer connecting to it. What that means for SharePoint specifically, and what to actually test.

*Buyer's guide · Question 8*

## What happens at your *volume*?

What degrades first depends on the storage provider, not the integration connecting to it.

For Salesforce admins and IT evaluating this at real, not demo, scale.

Last verified 21 Aug 2026·Sources: Microsoft, CloudFiles engineering·v1.0 Where this claim comes fromPublished by CloudFiles. That the connection routes through Microsoft Graph, and that Graph enforces throttling under load, is Microsoft's own published policy, linked below. That this is what actually degrades first for SharePoint specifically, ahead of anything CloudFiles adds, is our own observation, not independently verified.

## Why the provider matters more than the integration
A connector or app sits between Salesforce and your storage provider. At real volume, it's usually the provider's own infrastructure that slows first, not the layer connecting to it.

For SharePoint, that connection runs through **Microsoft Graph**, and Graph enforces its own throttling: exceed a library's list-view threshold and Graph returns an HTTP 429 (“activityLimitReached”), regardless of which app is calling it. Our own observation is that this is what degrades first at real volume, not CloudFiles' link to it. That's a Microsoft constraint no vendor engineers around, which is also exactly why no vendor should claim to have solved it.

Source: [Microsoft Graph throttling guidance](https://learn.microsoft.com/en-us/graph/throttling). Retrieved 21 Aug 2026.

## What to ask any vendor

- What did you actually test, at what document count, in what folder structure?
- What specifically slowed down first: listing, search, sync, or something else?
- Can I see that test against a folder my own real size, not a demo dataset?

## What your answer means
**Modest volume,** nothing approaching tens of thousands of files in one folder: this rarely bites in practice. Don't over-weight it in your evaluation.

**Large or fast-growing corpus:** require the vendor's own test data against something close to your real size, not a features list or a demo with a few dozen files.

## Where this stops
This page settles volume only. What you already have to migrate is [its own question](/salesforce/document-management/questions/what-you-have-to-migrate); cost is a separate one, in [the guide](/salesforce/document-management/guide#questions).

## *Check* my working

Most readers won't need this. If your volume is unusually large, say what's in the way.

- Report: written assessment, two to three working days.
- Reader: a person. Not a bot, not an auto-reply.
- Call: only if you ask. We won't ask twice.
- Fields: four. No phone, no company size, no mailing list.

**What happens next**

One chip, one line, one email.

A contact form follows this section.

Last verified 21 Aug 2026·Reviewed quarterly·v1.0