Microsoft Fabric Warehouse Connector

Use Microsoft Fabric Warehouse as a source or destination for replication, activation, and analytics pipelines.

SourceDestinationSilver

Start for Free Source Documentation Destination Documentation

Evaluating against Fivetran? See how Supaflow handles Microsoft Fabric Warehouse pricing, connector quality, and Snowflake deployment side-by-side.

Supaflow vs Fivetran

Why Supaflow

All connectors included

Every connector is available on every plan. Pricing does not increase with connector count.

Pay for compute, not rows

Credit-based pricing. Usage scales with your pipelines, not with row counts.

One platform

Ingestion, dbt Core transformation, reverse ETL, and orchestration in a single workspace.

Capabilities

Warehouse-Wide Source Coverage

Discover and select every table and view the service principal can query across accessible schemas in the configured Fabric Warehouse.

Replication and Activation Reads

Run full refreshes, use a date or timestamp cursor for incremental replication, or use modeled Warehouse data in downstream activation pipelines.

Flexible Destination Load Modes

Append new rows, merge current state, overwrite a table, or truncate and reload it, with merge as the default destination behavior.

Managed Destination Schemas

Create destination schemas and tables and add compatible nullable columns as source schemas evolve. Unsupported changes fail before data is loaded.

Microsoft Entra Service Principal

Use a dedicated application identity with workspace-scoped Fabric access instead of an interactive user or SQL password.

Supported Objects

As a Source

Tables across accessible schemas

Every table in the selected Fabric Warehouse that the configured service principal can access and query.

Views across accessible schemas

Every queryable view exposed through the selected Warehouse SQL endpoint and visible to the service principal.

As a Destination

Existing and connector-created tables

Pipeline output written to existing tables or new schemas and tables in the selected Fabric Warehouse.

How It Works

Register a service principal

Create a single-tenant Microsoft Entra application, generate a client secret, and save the tenant ID, application ID, and secret value.

Enable Fabric API access

Ask a Fabric administrator to allow approved service principals to call Fabric APIs, preferably through a dedicated security group.

Grant workspace access

Assign Viewer access for source and activation reads, or Contributor access when Supaflow will create and update destination tables.

Configure the SQL Server connector

Select SQL Server in Supaflow, enter the Warehouse SQL endpoint and item name, choose Entra Service Principal, add the workspace ID, and click Test & Save.

Use Cases

Load operational data into Fabric

Bring SaaS, database, and file data into Fabric Warehouse for reporting, semantic models, and governed analytics.

Replicate Fabric data elsewhere

Move selected Warehouse tables into another supported warehouse, database, or data-lake destination.

Activate curated Fabric data

Use modeled Warehouse tables as the source for activation pipelines that update supported business applications.

Frequently Asked Questions

Which connector do I select in Supaflow?

Select SQL Server. The SQL Server connector recognizes a standard Fabric Warehouse hostname automatically and applies Fabric-compatible authentication, types, and SQL behavior.

Can Fabric Warehouse be both a source and a destination?

Yes. The same connector can read Fabric Warehouse tables for ingestion or activation pipelines and can load supported source data into a Fabric Warehouse destination.

Which authentication method is supported?

Fabric Warehouse connections use a Microsoft Entra service principal. SQL password authentication is not supported by the Fabric Warehouse SQL endpoint.

Does the Fabric source support Change Tracking?

No. Use Standard query mode with full refresh or a reliable date or timestamp cursor. SQL Server Change Tracking is available only for SQL Server and Azure SQL Database.

Does the Fabric destination physically delete rows?

No. Leave Perform Hard Deletes disabled for Fabric Warehouse destinations. A pipeline that explicitly enables physical hard deletes fails before loading data.

Can I use a Lakehouse SQL analytics endpoint as the destination?

No. Configure a Fabric Warehouse item for destination loads. Lakehouse SQL analytics endpoints are read-only for external SQL clients.

Prepare Microsoft Fabric Warehouse