MICROSOFT FABRIC
type: fabricMicrosoft's unified analytics platform combining data engineering, data science, and business intelligence in one SaaS offering.
DVT SUPPORT
read in federation models
materialize federation results
run full dbt projects against it
dvt seed --target loads here
DVT supports Microsoft Fabricbecause both dbt and Sling do: dbt drives standard materializations when it's your default target, Sling moves data in and out during federation. Connectivity for both layers is checked with dvt debug --all.
PREREQUISITES
Driver: pyodbc — installed automatically by:
dvt sync
CONFIGURATION FIELDS
| FIELD | TYPE | REQUIRED | DEFAULT | DESCRIPTION |
|---|---|---|---|---|
| type | string | yes | — | Must be `fabric` |
| host | string | yes | — | Fabric SQL endpoint |
| port | integer | no | 1433 | SQL endpoint port |
| user | string | yes | — | Service principal or user |
| password | string | yes | — | Authentication credential |
| database | string | yes | — | Lakehouse or warehouse name |
| threads | integer | no | 4 | Number of parallel threads |
PROFILES.YML EXAMPLE
my_project:
target: fabric_dev
outputs:
fabric_dev:
type: fabric
host: your-workspace.datawarehouse.fabric.microsoft.com
port: 1433
user: "{{ env_var('FABRIC_USER') }}"
password: "{{ env_var('FABRIC_PASSWORD') }}"
database: my_lakehouseSOURCES.YML EXAMPLE
sources:
- name: fabric_data
meta:
connection: fabric_dev
schema: dbo
tables:
- name: sales
- name: inventoryDBT ADAPTER FEATURES
When Microsoft Fabric is your default target, every standard dbt model runs through the official dbt adapter — all of its documented capabilities apply unchanged:
MATERIALIZATIONS
tableviewincrementalephemeralf_tablef_incrementalINCREMENTAL STRATEGIES
appenddelete+insertNOTABLE CONFIGS
- ▸TDS protocol (SQL Server-compatible)
- ▸Azure AD authentication
FEDERATION INCREMENTAL STRATEGIES
Strategies available when this engine is the target of a f_incremental model:
KNOWN LIMITATIONS
- ⚠Uses SQL Server protocol via TDS endpoint