Airbyte vs Azure Data Factory (2026):
Connectors, Pricing & Fabric Migration

Updated Oct 26, 2026

Airbyte
vs

Summarize with AI:

Key takeaways

  • Choose Airbyte: for broad SaaS and API coverage, CDC on every plan, multi-cloud destinations, and pricing that doesn't depend on activity runs or DIU tuning.

  • Choose Azure Data Factory: for orchestrating Azure services, hybrid copies from on-prem SQL Server through a self-hosted integration runtime, and lifting existing SSIS packages to the cloud.

  • What changed in 2026: Microsoft now positions Data Factory in Microsoft Fabric as the next generation of ADF and recommends new users start there. Fabric bills on shared capacity units instead of ADF's per-activity meters, and ADF's managed Airflow (Workflow Orchestration Manager) stopped accepting new instances on January 1, 2026.

Azure Data Factory (ADF) is Microsoft's cloud ETL and orchestration service for building pipelines inside Azure. Airbyte is a data movement platform with 700+ prebuilt connectors that load SaaS, API and database data into any destination, on Azure or anywhere else. If your challenge is reliably replicating Salesforce, HubSpot, Stripe or Postgres data, Airbyte does that without designing Copy activities and pipelines for each source. ADF remains a strong choice for orchestrating Azure-native workloads and running existing SSIS packages.

Airbyte vs Azure Data Factory at a glance

AirbyteAzure Data Factory
CategoryData movement (ELT and CDC) platformCloud ETL and pipeline orchestration service
Prebuilt connectors700+, including SaaS APIs, databases, files and unstructured sources90+ built-in connectors, strongest for Azure and Microsoft sources
Building a pipelineConfigure source and destination in UI, API or TerraformDesign pipelines of Copy and other activities in ADF Studio, or JSON and ARM templates
Custom sourcesNo-code Connector Builder with AI assist, low-code CDK, Python CDKGeneric REST, HTTP and ODBC connectors you configure, or custom code in Azure Functions
Schema changesDetected and propagated automaticallySchema drift options in mapping data flows; Copy activity mappings you manage
Change data captureLog-based CDC on every planCDC resources and data flow CDC for selected sources
DestinationsAny warehouse, lakehouse, database or vector store, on any cloudPrimarily Azure (ADLS, Synapse, Azure SQL, Fabric)
Pricing modelVolume-based (Standard, Plus) or capacity-based Data Workers (Pro, Enterprise Flex)$1 per 1,000 activity runs, $0.25 per DIU-hour, ~$0.27 per vCore-hour for data flows (US East)
Free optionAirbyte Core (self-hosted)Azure free account credits only
DeploymentSelf-hosted (Core), managed cloud, hybrid or on-prem (Enterprise Flex)Azure-managed, with a self-hosted integration runtime for on-prem sources
Multi-cloudYesAzure-centric
Open sourceYesNo
Who can use itAnalysts (UI) and engineers (API, Terraform, PyAirbyte)Azure data engineers

About Airbyte

Airbyte is the open standard for data movement, used by 18% of the Fortune 500. It replicates data from 700+ sources into warehouses, lakehouses, databases and AI context stores, and runs self-hosted, fully managed, or hybrid inside your own boundary.

About Azure Data Factory

Azure Data Factory is Microsoft's serverless data integration service. You build pipelines from activities, such as Copy, Lookup and stored procedures, transform data visually with Spark-based mapping data flows, and run existing SSIS packages on an Azure-SSIS integration runtime. A self-hosted integration runtime connects ADF to on-prem databases and file shares.

ADF vs. Fabric Data Factory

Microsoft now has two Data Factory products. Standalone Azure Data Factory remains supported and billed per activity, DIU and vCore. Data Factory in Microsoft Fabric is the newer version, with pipelines that look like ADF's but run on shared Fabric capacity units alongside lakehouses, warehouses and Power BI.

Microsoft's documentation recommends that new users start with Fabric, and teams on ADF are planning migrations. That means re-testing pipelines, triggers and networking, and re-modeling cost on Fabric capacity. If you're re-platforming anyway, it's a natural point to reconsider how ingestion is done.

Ingestion vs. orchestration

ADF is strongest as an orchestrator and mover inside Azure. For SaaS apps and APIs outside the Microsoft ecosystem, teams often configure generic REST connectors and handle pagination, authentication, incremental state and schema changes in pipeline logic. Every source becomes a pipeline to maintain.

Airbyte connectors ship with that logic built in and maintained for you, with incremental syncs, CDC and schema propagation. When a source is missing, the Connector Builder creates one from API docs with AI assist.

Many Azure teams use both: Airbyte to land data in ADLS, Synapse, Azure SQL or Fabric, and ADF or Fabric pipelines to orchestrate what happens next.

Pricing: activity runs and DIU-hours vs. capacity

ADF bills several meters at once. In US East, orchestration costs $1 per 1,000 activity runs on the Azure integration runtime, Copy activities cost $0.25 per DIU-hour, self-hosted data movement costs $0.10 per hour, and mapping data flows cost about $0.27 per vCore-hour. Debug runs, monitoring and SSIS runtimes add more. Cost depends on how many activities each pipeline runs and how many DIUs each copy uses.

Fabric Data Factory replaces these meters with a share of your Fabric capacity, so cost depends on capacity size and every other workload running on it.

Airbyte Core is free to self-host. Cloud starts at $20/month (Standard) and $189/month (Plus). Pro and Enterprise Flex price on Data Workers, dedicated compute capacity, so cost doesn't depend on activity counts, DIU tuning or row counts.

Multi-cloud and deployment

ADF runs in Azure and is designed around Azure destinations, with a self-hosted integration runtime for on-prem sources.

Airbyte writes to Snowflake, BigQuery, Databricks, Redshift, Postgres, Azure Blob and ADLS, Iceberg lakehouses and vector stores, on any cloud. It runs four ways on one codebase: free self-hosted Core, managed cloud, hybrid with an Airbyte-managed control plane, or fully on-prem with Enterprise Flex. You can also run it inside your own Azure subscription.

Where Azure Data Factory leads

ADF is a strong fit for orchestrating Azure-native services, hybrid copies from on-prem SQL Server through the self-hosted integration runtime, and running existing SSIS packages in the cloud.

When to choose Airbyte vs Azure Data Factory

Your situationBetter fit
You need SaaS and API data (Salesforce, HubSpot, Stripe, Zendesk)Airbyte
You don't want to build and maintain a pipeline per sourceAirbyte
You load into non-Azure destinations, or several cloudsAirbyte
You want cost that doesn't depend on activity runs or DIU tuningAirbyte (capacity-based)
You need CDC from production databases with minimal setupAirbyte
You orchestrate Azure-native services and existing SSIS packagesAzure Data Factory
You're standardizing on Microsoft Fabric for analyticsFabric Data Factory

FAQs

For ingestion, yes. Airbyte offers 700+ prebuilt connectors and loads into Azure and non-Azure destinations without building a pipeline per source. For orchestrating Azure services and SSIS, ADF and Airbyte work well together.

In US East, ADF charges $1 per 1,000 activity runs on the Azure integration runtime, $0.25 per DIU-hour for data movement, and about $0.27 per vCore-hour for mapping data flows. Self-hosted data movement, monitoring and SSIS are billed separately.

Azure Data Factory is still supported, but Microsoft positions Data Factory in Microsoft Fabric as its next generation and recommends that new users start there. Fabric bills on shared capacity units rather than per activity.

Yes. Airbyte has destinations for Azure Blob Storage, ADLS, Azure SQL and other Microsoft-hosted databases, plus Snowflake, Databricks, BigQuery and more.

Yes. Self-host Airbyte Core on AKS or Azure VMs, or use Enterprise Flex to run the data plane in your own Azure environment.

Many teams do: Airbyte ingests SaaS and database data into ADLS, Azure SQL or Fabric, and ADF or Fabric pipelines orchestrate downstream steps.