| title | include file |
|---|---|
| description | include file |
| author | chez-charlie |
| ms.service | azure-data-factory |
| ms.topic | include |
| ms.date | 2/6/2025 |
| ms.author | n0elleli |
| ms.custom | include file |
Azure Data Factory is a multitenant service that has the following default limits in place to make sure customer subscriptions are protected from each other's workloads. To raise the limits up to the maximum for your subscription, contact support.
| Resource | Default limit | Maximum limit |
|---|---|---|
| Total number of entities, such as pipelines, data sets, triggers, linked services, Private Endpoints, and integration runtimes, within a data factory | 5,000 | 5,000 |
| Total CPU cores for Azure-SSIS Integration Runtimes under one subscription | 64 | Find out how to request a quota increase from support. |
| Concurrent pipeline runs per data factory shared among all pipelines in the factory | 10,000 | 10,000 |
| Concurrent External activity runs per subscription per Azure Integration Runtime region External activities are managed on integration runtime but execute on linked services, including Databricks, stored procedure, Web, and others. This limit doesn't apply to Self-hosted IR. |
3,000 | 3,000 |
| Concurrent Pipeline activity runs per subscription per Azure Integration Runtime region Pipeline activities execute on integration runtime, including Lookup, GetMetadata, and Delete. This limit doesn't apply to Self-hosted IR. |
1,000 | 1,000 |
| Concurrent authoring operations per subscription per Azure Integration Runtime region Including test connection, browse folder list and table list, preview data. This limit doesn't apply to Self-hosted IR. |
200 | 200 |
| Concurrent Data Integration Units1 consumption per subscription per Azure Integration Runtime region | Region group 12: 6,000 Region group 22: 3,000 Region group 32: 1,500 |
Region group 12: 6,000 Region group 22: 3,000 Region group 32: 1,500 |
| Concurrent Data Integration Units1 consumption per subscription per Azure Integration Runtime region in managed virtual network | 2,400 | 2,400 |
| Maximum activities per pipeline, which includes inner activities for containers | 120 | 120 |
| Maximum number of linked integration runtimes that can be created against a single self-hosted integration runtime | 100 | 100 |
| Maximum number of nodes that can be created against a single self-hosted integration runtime | 4 | 4 |
| Maximum parameters per pipeline | 50 | 50 |
| ForEach items | 100,000 | 100,000 |
| ForEach parallelism | 20 | 50 |
| Maximum queued runs per pipeline | 100 | 100 |
| Characters per expression | 8,192 | 8,192 |
| Minimum tumbling window trigger interval | 5 min | 15 min |
| Minimum timeout for pipeline activity runs | 10 min | 10 min |
| Maximum timeout for pipeline activity runs | 7 days | 7 days |
| Bytes per object for pipeline objects3 | 200 KB | 200 KB |
| Bytes per object for dataset and linked service objects3 | 100 KB | 2,000 KB |
| Bytes per payload for each activity run4 | 896 KB | 896 KB |
| Data Integration Units1 per copy activity run | 256 | 256 |
| Write API calls | 1,200/h | 1,200/h This limit is imposed by Azure Resource Manager, not Azure Data Factory. |
| Read API calls | 12,500/h | 12,500/h This limit is imposed by Azure Resource Manager, not Azure Data Factory. |
| Monitoring queries per minute | 1,000 | 1,000 |
| Maximum time of data flow debug session | 8 hrs | 8 hrs |
| Concurrent number of data flows per integration runtime | 50 | 50 |
| Concurrent number of data flows per integration runtime in managed vNet | 50 | 50 |
| Concurrent number of data flow debug sessions per user per factory | 3 | 3 |
| Data Flow Azure IR TTL (time to live) limit | 4 hrs | 4 hrs |
| Meta Data Entity Size limit in a factory | 2 GB | 2 GB |
1 The data integration unit (DIU) is used in a cloud-to-cloud copy operation. Learn more from Data integration units (version 2). For information on billing, see Azure Data Factory pricing.
2 Azure Integration Runtime is globally available to ensure data compliance, efficiency, and reduced network egress costs.
| Region group | Regions |
|---|---|
| Region group 1 | Central US, East US, East US 2, North Europe, West Europe, West US, West US 2 |
| Region group 2 | Australia East, Australia Southeast, Brazil South, Central India, Japan East, North Central US, South Central US, Southeast Asia, West Central US |
| Region group 3 | Other regions |
If managed virtual network is enabled, the data integration unit (DIU) in all region groups are 2,400.
3 Pipeline, data set, and linked service objects represent a logical grouping of your workload. Limits for these objects don't relate to the amount of data you can move and process with Azure Data Factory. Data Factory is designed to scale to handle petabytes of data.
4 The payload for each activity run includes the activity configuration, one or more associated datasets, and linked service configurations if any, and a small portion of system properties generated per activity type. Limit for this payload size doesn't relate to the amount of data you can move and process with Azure Data Factory. Learn about the symptoms and recommendation if you hit this limit.
Azure Resource Manager has limits for API calls. You can make API calls at a rate within the Azure Resource Manager API limits.