What causes UserErrorCosmosDbRequestRateOrLimitExceeded?

The ADF copy activity is writing documents at a rate that exceeds the collection's provisioned RU/s. The copy activity's parallelism setting is too high, sending too many concurrent writes. Another application is simultaneously consuming the collection's RU budget while ADF is copying. The Cosmos DB collection throughput is set too low for the data volume being copied

How do I fix UserErrorCosmosDbRequestRateOrLimitExceeded?

Reduce the copy activity's parallelism: lower 'Data integration units' (DIU) and 'Degree of copy parallelism'.. Temporarily scale up the Cosmos DB collection's provisioned throughput (RU/s) during the copy window, then scale back down after.. Enable autoscale on the Cosmos DB container to automatically handle throughput spikes.. Check Cosmos DB metrics in the Azure portal for current RU consumption.. Stagger the pipeline schedule to avoid running the Cosmos DB copy simultaneously with other applications.

Medium severitydata source

Power BI Refresh Error:
UserErrorCosmosDbRequestRateOrLimitExceeded

What does this error mean?

An Azure Data Factory copy activity was throttled by Azure Cosmos DB because the provisioned throughput (RU/s) for the collection was exceeded. Cosmos DB returns HTTP 429 which ADF surfaces as this error.

Common causes

1The ADF copy activity is writing documents at a rate that exceeds the collection's provisioned RU/s
2The copy activity's parallelism setting is too high, sending too many concurrent writes
3Another application is simultaneously consuming the collection's RU budget while ADF is copying
4The Cosmos DB collection throughput is set too low for the data volume being copied

How to fix it

1Reduce the copy activity's parallelism: lower 'Data integration units' (DIU) and 'Degree of copy parallelism'.
2Temporarily scale up the Cosmos DB collection's provisioned throughput (RU/s) during the copy window, then scale back down after.
3Enable autoscale on the Cosmos DB container to automatically handle throughput spikes.
4Check Cosmos DB metrics in the Azure portal for current RU consumption.
5Stagger the pipeline schedule to avoid running the Cosmos DB copy simultaneously with other applications.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

In ADF Monitor, click the failed run, then the failed activity. The detail pane shows the error code, message, and sub-error codes.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-troubleshoot-azure-cosmos-db