Azure Data Factory pricing guide details
Pricing Overview
Azure Data Factory uses a pure usage-based pricing model with no upfront commitments or fixed monthly fees. You pay only for what you consume across four distinct billing dimensions: pipeline orchestration, data movement, data flow execution, and integration runtime hours. This consumption-based approach makes Azure Data Factory accessible for small projects while scaling predictably for enterprise workloads.
The core pricing components break down as follows: pipeline orchestration costs $1 per 1,000 activity runs, data movement charges $0.25 per DIU-hour (Data Integration Unit), data flow execution runs $0.273 per vCore-hour, and SSIS integration runtime costs $0.84 per node per hour for a Standard A4 v2 node (license included). Notably, the self-hosted integration runtime is free for up to 5 nodes, which is a meaningful cost advantage for hybrid data scenarios.
Plan Comparison
Azure Data Factory does not use traditional subscription tiers. Instead, costs accumulate across independent billing meters. We have organized the pricing into a clear breakdown by component.
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Component | Unit | Price | Free Tier |
|---|---|---|---|
| Pipeline Orchestration | Per 1,000 activity runs | $1.00 | First 1,000 runs/month |
| Data Movement | Per DIU-hour | $0.25 | N/A |
| Data Flow (General) | Per vCore-hour | $0.273 | N/A |
| SSIS Integration Runtime | Per node/hour | $0.84 (Standard A4 v2) | N/A |
| Self-Hosted IR | Per node | Free | Up to 5 nodes |
Each pipeline run triggers one or more activity runs. A simple copy job that moves data from a source to a destination counts as a single activity run. Complex pipelines with multiple transformation steps, lookups, and conditional logic will generate several activity runs per execution.
Data movement pricing scales with the parallelism you configure. DIUs represent a blended measure of CPU, memory, and network allocation. The default is 4 DIUs for cloud copy activities, but you can adjust between 2 and 256 DIUs depending on throughput requirements. Higher DIU counts move data faster but increase per-hour costs proportionally.
Data flow execution charges apply when you use ADF's visual data transformation engine (Mapping Data Flows). These run on an Apache Spark cluster under the hood, and pricing reflects the vCore-hours consumed. Cluster warm-up time of approximately 5 minutes is billed regardless of job duration.
Hidden Costs and Considerations
We have identified several costs that teams commonly overlook when budgeting for Azure Data Factory:
- Cluster warm-up billing: Data flow clusters take roughly 5 minutes to spin up, and that time is billed at the full vCore-hour rate even for short-running jobs.
- Retry and rerun charges: Failed activity runs that are retried still count toward your activity run total and incur orchestration costs.
- Egress fees: Moving data out of Azure regions incurs standard Azure networking egress charges on top of ADF pricing.
- Monitoring and logging: Detailed diagnostics through Azure Monitor add incremental costs that scale with pipeline volume.
Cost Estimates by Team Size
Based on the published per-unit rates, we have modeled three representative usage profiles.
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Team Size | Pipelines/Day | Est. Activity Runs/Month | Data Movement (DIU-hrs/mo) | Data Flows (vCore-hrs/mo) | Est. Monthly Cost |
|---|---|---|---|---|---|
| Small (2-5 analysts) | 10-20 | 5,000 | 50 | 20 | ~$23 |
| Mid-size (10-20 engineers) | 50-100 | 50,000 | 300 | 150 | ~$166 |
| Enterprise (50+ engineers) | 500+ | 500,000+ | 2,000+ | 1,000+ | 500 × $1 + 2,000 × $0.25 + 1,000 × $0.273 = $1,273+ |
How Azure Data Factory Pricing Compares
Azure Data Factory's usage-based model stands apart from the subscription-based pricing that most competing data pipeline tools use. We have compared it against three popular alternatives in the data pipeline category.
Scroll sideways to see all columns. With a keyboard, focus this table and use the arrow keys.
| Tool | Pricing Model | Starting Price | Best For |
|---|---|---|---|
| Azure Data Factory | Usage-Based | Variable; see worked example below | Teams already on Azure needing flexible, pay-per-use ETL |
| Airbyte | Freemium | $10/mo (Cloud Standard) | Teams wanting open-source flexibility with 600+ connectors |
| Stitch | Freemium | $100/mo (Standard) | Small teams needing simple, managed ELT |
| Hevo Data | Freemium | Starter from $299/month billed monthly or $265/month billed annually; 5M events/month | Limited connectors, up to 1M events/month; destination-event billing |
Compare Azure Data Factory with managed ingestion using the same sources, destination, sync frequency and measured workload. Hevo counts each destination insert, update or delete as an event and charges extra On-Demand fees above the plan quota. Include orchestration, processing, data transfer and any reserved or provisioned resources in the ADF estimate. A smaller entry fee does not establish which complete pipeline costs less.