Data Factory Pricing

Transform data into trusted information

Azure Data Factory helps you create, schedule, monitor and manage data pipelines. A data pipeline consists of activities that can move data between on-premises and cloud data stores and transform data to produce trusted information.

Pricing Details

The pricing for Data Factory usage is calculated based on the following factors:

  • The frequency of activities (high or low). A low frequency activity does not execute more than once in a day (for example, daily, weekly, monthly); a high-frequency activity executes more than once in a day (for example, hourly, every 15 mins). See Orchestration of activities section below for details.
  • Where the activities run (cloud or on-premises). See Data Movement section below.
  • Whether a pipeline is active or not. See Inactive Pipelines section below.
  • Whether you are re-running an activity. See Re-running activities section below.

Orchestration of activities

Low frequency High frequency
Activities running in the cloud

(examples: copy activity moving data from an Azure blob to an Azure SQL database; hive activity running hive script on an Azure HDInsight cluster).
$- per activity per month $- per activity per month
Activities running on-premises and involving Data Management Gateway

(examples: copy activity moving data from an on-premises SQL Server database to Azure blob; stored procedure activity running a stored procedure in an on-premises SQL Server database)
$- per activity per month $- per activity per month


  • Usage beyond 100 activities/month will receive a 20% discount for both low-frequency and high-frequency scenarios.
  • The first 5 low-frequency activities in a month are free of charge in both cloud and on-premises variants.

Data movement

Azure Data Factory can copy data between various data stores in a secure, reliable, performant and scalable way. As your volume of data or data movement throughput needs grow, Azure Data Factory can scale out to meet those needs. Refer to the Copy Activity Performance Guide to learn about leveraging data movement units to boost your data movement performance.

Data Movement between Cloud data stores $- per hour
Data Movement when an on-premises store is involved $- per hour
Second, you may incur data transfer charges, which will show up as a separate outbound data transfer line item on your bill. Outbound data transfer charges are applied when data goes out of Azure data centres. See Data Transfers Pricing Details for more information.

Inactive pipelines

You must specify an active data processing period using a date/time range (start and end times) for each pipeline you deploy to the Azure Data Factory. The pipeline is considered as active for the specified period even if its activities are not actually running. It is considered as inactive at all other times.

An inactive pipeline is charged at $- per month.

Pipelines that are inactive for an entire month are billed at the applicable “inactive pipeline” rate for the month. Pipelines that are inactive for a portion of a month are billed for their inactive periods on a prorated basis for the number of hours they are inactive in that month. For example, if a pipeline has a start date and time of 1/1/2016 at 12:00 AM and an end date and time of 20/1/2016 at 12:00 AM, the pipeline is considered active for those 20 days and inactive for 11 days. The charge for inactive pipeline ($-) is prorated for 11 days.

If a pipeline does not have an active data processing period (a start and end time) specified, it is considered inactive.

Re-running activities

Activities can be re-run if needed (for example, if the data source was unavailable during the scheduled run). The cost of re-running activities varies based on the location where the activity is run. The cost of re-running activities in the cloud is $- per 1,000 re-runs. The cost of re-running activities on-premises is $- per 1,000 re-runs.


Suppose you have a data pipeline with the following two activities that run once a day (low-frequency):

  1. A Copy activity that copies data from an on-premises SQL Server database to an Azure blob.
  2. A Hive activity that runs a hive script on an Azure HDInsight cluster.

Assume that it takes 2 hours in a day to move data from on-premises SQL Server database to Azure blob storage. The following table shows costs associated with this pipeline:

First activity (copying data from on-premises to Azure)
Data Movement Cost (per month) 30 days per month
2 hours per day
Orchestration of Activities Cost (per month) $-
Subtotal (per month) $-
Second activity (a Hive script running on Azure HDInsight)
Data Movement Cost (per month) $-
Orchestration of Activities Cost (per month) $-
Subtotal (per month) $-
Total activities (per month) $-

You can also use the Data Factory Pricing Calculator to calculate charges for this scenario.


  • There is no charge for the first five cloud and on-premises activities. The charges mentioned above assume that you have already used five cloud and five on-premises activities per month (in other pipelines).
  • Azure Storage and HDInsight services are billed separately at their per service rates.

Support and SLA

  • Free billing and subscription management support.
  • Flexible support plans starting at $29.0/month. Shop for a plan
  • Guarantee that at least 99.9% of the time, we will successfully process requests to perform operations against Data Factory resources.
  • Guarantee that at least 99.9% of the time, all activity runs will initiate within 4 minutes of their scheduled execution times.
  • To learn more about the SLA, please visit the SLA page.




Estimate your monthly costs for Azure services

Frequently Asked Questions

Purchase FAQs

Review Azure pricing frequently asked questions

Product Details

Product details

Learn more about Data Factory



Review technical tutorials, videos and more resources

Sign up now and get $200 in Azure credits

Start today