Azure Synapse & Microsoft Fabric ETL

Load Synapse and Fabric. Both ways.

Q: Does Etlworks support both Azure Synapse and Microsoft Fabric?

Yes — both. Etlworks loads into Azure Synapse Analytics (dedicated SQL pools) and Microsoft Fabric (Warehouse and Lakehouse on OneLake). VAT IT streams transactional data from PostgreSQL into Synapse and Fabric in real time on Etlworks.

Q: How does Etlworks load data into Synapse and Fabric?

Etlworks stages files in Azure Data Lake Storage (ADLS Gen2) and runs COPY INTO for high-throughput bulk loading. On Synapse, PolyBase / external tables are also supported. Change data is applied with MERGE. No row-by-row inserts.

Q: Does Etlworks support real-time CDC into Synapse and Fabric?

Yes. Log-based CDC from MySQL, Postgres, SQL Server, Oracle, MongoDB, and DB2 streams change events in with MERGE, preserving INSERT, UPDATE, and DELETE idempotently at sub-second source latency. VAT IT runs exactly this pattern from PostgreSQL into Synapse and Fabric.

Q: How does Etlworks authenticate to Azure?

Via Microsoft Entra ID (Azure AD), service principals, managed identity, or SQL authentication, with the ADLS staging container scoped to the same identity. Connections honor VNet and Private Link where configured.

Q: Can I use dbt with Etlworks, Synapse, and Fabric?

Yes. Etlworks loads raw data into Synapse or Fabric, then you can trigger a dbt run to model it — or use Etlworks's native SQL, JavaScript, and Python transformations and skip dbt. ELT pushdown generates the target's T-SQL for in-warehouse transformations.

Q: Will Etlworks drive up my Azure costs?

Etlworks's loading patterns minimize warehouse-up time: ADLS-staged COPY INTO instead of chatty inserts, batched MERGE during CDC, and short load windows. Because Etlworks bills per platform tier — not per row — your integration cost stays flat as data volumes grow, on top of whatever Synapse or Fabric capacity you run.

ETL, ELT, real-time CDC, and Reverse ETL — all into and out of Azure Synapse Analytics and Microsoft Fabric. COPY INTO from ADLS, MERGE-based change data, 270+ source connectors. Predictable monthly pricing instead of per-row consumption.

Start free trial Talk to us

2-in-1: Synapse + Fabric
2-way: In + Reverse ETL
<1s: CDC latency
No: Per-row billing

The problem

Azure capacity is metered. Your ETL bill shouldn't pile on.

Most ways into Synapse or Fabric cost you twice. Consumption-priced ETL tools bill per row on top of your DWU or capacity-unit spend, or you build Data Factory pipelines and notebooks that someone has to own and tune. Either way, loading the warehouse becomes its own project.

Where budgets go to die

Per-row pricing punishes the workloads that justify the warehouse.

CDC pipelines, hourly SaaS syncs, large historical backfills — exactly the data you want in Synapse or Fabric — are the workloads consumption-priced tools cost the most for. Etlworks bills per platform tier, not per record. Load 200 billion rows or 200 million; same monthly cost. Predictable for your CFO, painless for your data team.

Capabilities

Azure-native, end to end.

COPY INTO from ADLS

Stages files in ADLS Gen2, then runs COPY INTO at warehouse speed — on Synapse dedicated SQL pools and Fabric Warehouse. PolyBase / external tables also supported on Synapse.

Real-time CDC into Azure

Log-based CDC from MySQL, Postgres, SQL Server, Oracle, Mongo, DB2 — sub-second latency, MERGE-based deduping into Synapse and Fabric.

Reverse ETL out of Azure

Push modeled Synapse or Fabric data to Salesforce, HubSpot, Marketo, NetSuite, and 200+ SaaS targets. Same platform, same subscription.

Synapse + Fabric, one engine

Target dedicated SQL pools or Fabric Warehouse and Lakehouse on OneLake. Schema evolution propagates automatically — no DDL drift.

Transformations + ELT pushdown

SQL, JavaScript, Python — transform in flight or push down to run as T-SQL inside Synapse or Fabric. dbt-friendly, dbt-optional.

Cost-aware loading

ADLS-staged COPY INTO, batched MERGE, and short load windows keep capacity work efficient on both Synapse and Fabric.

Patterns

Three flows, one platform.

Every Synapse and Fabric data pipeline pattern, configured the same way. No separate tool for CDC, no separate tool for Reverse ETL, no Data Factory pipelines to maintain by hand.

Data in

Source ADLS Synapse / Fabric

Bulk ETL / ELT

Stage files in ADLS, then COPY INTO. The pattern Microsoft recommends, automated end to end.

Real-time

DB Log CDC MERGE

CDC into Azure

Log-based CDC streams change events into Synapse or Fabric via MERGE. Sub-second latency, no Kafka.

Reverse

Synapse / Fabric Transform SaaS

Reverse ETL out

Push enriched data from Azure to Salesforce, HubSpot, Marketo, NetSuite — 200+ SaaS targets.

Pricing transparency

A typical 50M-row pipeline, three ways.

Same workload — Salesforce account changes, Postgres orders, hourly SaaS syncs into Synapse or Fabric — priced under three common ETL pricing models. Numbers are approximate, based on public pricing as of 2026, and exclude Azure compute itself.

Consumption (per-row)

~$8,000/mo

Scales linearly with row volume. Hidden surge pricing during busy months.

Credit-based

~$3,500/mo

Better, but credits expire, and peak-load tier upgrades add cost.

Etlworks (fixed tier)

$1,000/mo

Standard tier, all features, all rows. Predictable for budgets, painless for data teams.

Specifications

Synapse & Fabric integration depth.

Every part of an Azure analytics pipeline you'd actually run — loading, CDC, targets, and security — supported and documented.

Staging

Azure Data Lake Storage (ADLS Gen2) · auto-managed lifecycle

Load methods

COPY INTO for bulk · PolyBase / external tables on Synapse · MERGE for change data

File formats

CSV, JSON, Parquet

Targets & transforms

Synapse

Dedicated SQL pools · T-SQL surface

Microsoft Fabric

Fabric Warehouse and Lakehouse on OneLake

CDC & ELT

MERGE deduping, INSERT/UPDATE/DELETE preserved · pushdown T-SQL · dbt-friendly

Security & auth

Authentication

Microsoft Entra ID (Azure AD), service principal, managed identity, or SQL auth

Network

VNet · Private Link · static IP allowlisting for on-prem agents

Schema

Automatic schema evolution · new columns and type changes propagated

Comparing data integration platforms? See Etlworks vs Azure Data Factory

Proof

Synapse and Fabric pipelines, in production.

VAT IT streams transactional data from PostgreSQL into Azure Synapse and Microsoft Fabric in real time with Etlworks — low-latency, reliable pipelines across production and development environments.

VAT IT

Real-time CDC · PostgreSQL → Synapse + Fabric

Read the case study

FAQ

Common questions.

Does Etlworks support both Azure Synapse and Microsoft Fabric?

Yes — both. Etlworks loads into Azure Synapse Analytics (dedicated SQL pools) and Microsoft Fabric (Warehouse and Lakehouse on OneLake). VAT IT streams transactional data from PostgreSQL into Synapse and Fabric in real time on Etlworks.

How does Etlworks load data into Synapse and Fabric?

Etlworks stages files in Azure Data Lake Storage (ADLS Gen2) and runs COPY INTO for high-throughput bulk loading. On Synapse, PolyBase / external tables are also supported. Change data is applied with MERGE. No row-by-row inserts.

Does Etlworks support real-time CDC into Synapse and Fabric?

Yes. Log-based CDC from MySQL, Postgres, SQL Server, Oracle, MongoDB, and DB2 streams change events in with MERGE, preserving INSERT, UPDATE, and DELETE idempotently at sub-second source latency. VAT IT runs exactly this pattern from PostgreSQL into Synapse and Fabric.

How does Etlworks authenticate to Azure?

Via Microsoft Entra ID (Azure AD), service principals, managed identity, or SQL authentication, with the ADLS staging container scoped to the same identity. Connections honor VNet and Private Link where configured.

Can I use dbt with Etlworks, Synapse, and Fabric?

Yes. Etlworks loads raw data into Synapse or Fabric, then you can trigger a dbt run to model it — or use Etlworks's native SQL, JavaScript, and Python transformations and skip dbt. ELT pushdown generates the target's T-SQL for in-warehouse transformations.

Will Etlworks drive up my Azure costs?

Etlworks's loading patterns minimize warehouse-up time: ADLS-staged COPY INTO instead of chatty inserts, batched MERGE during CDC, and short load windows. Because Etlworks bills per platform tier — not per row — your integration cost stays flat as data volumes grow, on top of whatever Synapse or Fabric capacity you run. Talk to us for a cost comparison.

Start your trial

14 days. No card. Real workloads.

Spin up a free trial, point it at your Synapse pool or Fabric workspace, and load production data. See what predictable ETL pricing actually feels like.

Start free trial Talk to us