Skip Navigation

Data Factory pricing

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:

With Data Factory V2, you pay for data pipeline orchestration (by activity run) and by the hour for the compute resources used for data movement and transformation (see data movement and SSIS sections below). All data factory capabilities (orchestration, data movement, and others) are executed on a Data Factory cloud or self hosted integration runtime.

OrchestrationPreview

Runs Preview Price Examples
Activity runs (Azure integration runtime) First 50,000 activity runs—$- per 1,000 runs
Beyond 50,000 activity runs—$- per 1,000 runs
copy activity moving data from an Azure blob to an Azure SQL database; Hive activity running Hive script on an Azure HDInsight cluster.
Activity runs (Self-Hosted Integration Runtime) $- per 1,000 runs 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.
Create/retrieve/update/delete operations for all ADF entities (Pipeline, Data Set, Pipeline Runs, etc) is free during public preview.

Data MovementPreview

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. Learn about using data movement units to boost your data movement performance.

Note:
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 centers. See more information.

Data movement (Azure integration runtime) $- per hour
Data movement (self-hosted integration runtime) $- per hour
Execution and monitoring of all activities (e.g. Lookup, GetMetadata, etc), excluding data movement, is free during public preview.

SQL Server Integration Services compute resource through Azure-SSIS Integration RuntimePreview

The Data Factory integration runtime (cloud hosted only) supports running SSIS packages. SSIS usage is charged by the hour and supports SSIS standard capabilities using A-series and D-series virtual machine (VMs). Get more information on A- and D-series VMs.

SSIS standard A-series V2 VM

Instance Cores Ram Temporary Storage License Included Preview Price Preview Price with Azure Hybrid Benefit (% Savings)
SSIS A4 v2 4 8.00 GiB 40 GiB $- $-
SSIS A8 v2 8 16.00 GiB 80 GiB $- $-

SSIS Enterprise A-series V2 VM

Instance Cores Ram Temporary Storage License Included Preview Price Preview Price with Azure Hybrid Benefit (% Savings)
SSIS A4 v2 4 8.00 GiB 40 GiB $- $-
SSIS A8 v2 8 16.00 GiB 80 GiB $- $-

SSIS standard D-series V2 VM

Instance Cores Ram Temporary Storage License Included Preview Price Preview Price with Azure Hybrid Benefit (% Savings)
SSIS D1 v2 1 3.50 GiB 50 GiB $- $-
SSIS D2 v2 2 7.00 GiB 100 GiB $- $-
SSIS D3 v2 4 14.00 GiB 200 GiB $- $-
SSIS D4 v2 8 28.00 GiB 400 GiB $- $-

SSIS Enterprise D-series V2 VM

Instance Cores Ram Temporary Storage License Included Preview Price Preview Price with Azure Hybrid Benefit (% Savings)
SSIS D1 v2 1 3.50 GiB 50 GiB $- $-
SSIS D2 v2 2 7.00 GiB 100 GiB $- $-
SSIS D3 v2 4 14.00 GiB 200 GiB $- $-
SSIS D4 v2 8 28.00 GiB 400 GiB $- $-

Inactive Pipelines

Pipelines that are not associated with a trigger and have had zero runs for a week are considered inactive. An inactive pipeline is charged at $- per month.

FAQ

  • An activity is a step within a pipeline. The execution of each activity is called a run.

    For example, you may use a copy activity to copy data from an on-premises SQL Server to an Azure Blob Storage. Then, use a Hive activity that runs a Hive script on an Azure HDInsight cluster to process/transform data from the blob storage to produce output data.

  • Pipelines that are not associated with a trigger and have had zero runs for a week are considered inactive.

  • Integration runtime is the data integration infrastructure for performing data movement and transformation.

    For data movement, integration runtime moves the data between the source and destination data stores, while providing support for built-in connectors, format conversion, column mapping, and performant and scalable data transfer.

    For transformation, integration runtime provide capability to natively execute SSIS packages. Integration Runtime also supports dispatching and monitoring transformation activities running on a variety of compute services such as Azure HDInsight, Azure Machine Learning, Azure SQL Database, SQL Server, and more.

    Customers can deploy one or many instances of integration runtime as required to move and transform data. The integration runtime can run in Azure public network or in a private network (on premises, Azure Virtual Network, or AWS VPC).

  • Yes. If the Activity uses Azure services such as HDInsight, those services are billed separately at their per-service rates.

  • Yes. You will have to pay for the SQL Azure instance to host the SSIS catalog on Azure. You can either use an existing SQL Azure Database server or create a new one for this under subscription.

  • Azure Hybrid Benefit for SQL Server helps you get more value from your SQL Server licenses on Azure SQL Server Integration Services. Customers with active Software Assurance on Enterprise Edition and Standard Edition per-core licenses are eligible for Azure Hybrid Benefit if they choose to move these licenses to the cloud. Azure Hybrid Benefit for SQL Server is not restricted to any specific licensing program, but you must have active Software Assurance coverage.

    You can activate Azure Hybrid Benefit via the Azure Portal by attesting you have sufficient active licenses with Software Assurance.

    *Savings are based on 8 vCore business-critical managed Instances in East US Region, running 730 hours per month. Savings are calculated from full price (license included) against reduced price (using Azure Hybrid Benefit for SQL Server), which includes the Software Assurance cost for SQL Server Enterprise Edition. Actual savings may vary based on region, instance size, performance tier, and Software Assurance tier. Prices as of December 2017. Prices subject to change.

  • No. Licenses must be used on-premises or in the cloud. Customers have a 180-day grace period during which they can use licenses both on-premises and in the cloud to facilitate migration.

  • No. Azure Hybrid Benefit cannot be applied retroactively.

  • To use Azure Hybrid Benefit for SQL Server, you need active Software Assurance. If your Software Assurance expires and you don’t renew it, you’ll be moved to the License Included pricing of the respective SKU.

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
Activites 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 a self-hosted Integration Runtime

(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

Notes:

  • Usage beyond 100 activities/month will receive a 20% discount for both low frequency and high frequency scenarios.
  • First 5 low frequency activities in a month are free 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
Note:
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 centers. 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 starting date and time of 1/1/2016 at 12:00 AM and an ending date and time of 1/20/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.

Example

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.

Notes:

  • 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 & SLA

  • Free billing and subscription management support.
  • Flexible support plans starting at $29/month. Shop for a plan
  • Guarantee at least 99.9% of the time we will successfully process requests to perform operations against Data Factory resources.
  • Guarantee 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.

FAQ

  • Activities define the actions to perform on your data. Each activity takes zero or more datasets as inputs and produces one or more datasets as output. An activity is a unit of orchestration in Azure Data Factory.

    For example, you may use a Copy activity to orchestrate copying data from one dataset to another. Similarly, you may use a Hive activity to run a Hive query on an Azure HDInsight cluster to transform or analyze your data. Azure Data Factory provides a wide range of data transformation and data movement activities. You may also choose to create a custom .NET activity to run your own code.

  • A pipeline is a logical grouping of activities. Pipelines can be active for a user-specified period of time (start and end times). Pipelines are inactive at all other times.
  • Yes. If the Activity uses Azure services such as HDInsight, those services are billed separately at their per service rates.

  • There are two sets of costs incurred when you perform a data copy. First, the compute resources that are used for performing the copy are represented by the data movement meter. There are cloud and on-premises versions of the data movement meter, and on-premises data movement is less expensive because a portion of the compute associated with the copy is performed by your own on-premises resources. Data movement charges are prorated by the minute and rounded up. (For example, a data copy taking 41 minutes 23 seconds of compute time will result in a charge for 42 minutes).

    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 centers. See Data Transfers Pricing Details for more information.

Resources

Estimate your monthly costs for Azure services

Review Azure pricing frequently asked questions

Learn more about Data Factory

Review technical tutorials, videos, and more resources

Added to estimate. Press 'v' to view on calculator View on calculator

Learn and build with $200 in credit, and keep going for free