Overview
Emit collected data from Entegrata into a Microsoft Fabric Warehouse. Emission is available to customers on the Firm-Hosted model. This emitter endpoint is not currently available to customers on the Entegrata-Hosted model. Destination type: SQL database (Microsoft Fabric Warehouse)Before You Start
Entegrata authenticates to Fabric with an Azure AD identity. Pick one of:- Managed Identity — ask your Entegrata Customer Experience Manager for the managed identity Entegrata uses in Azure. Add that identity to the target Fabric workspace as a Member (or higher) and grant it read/write access to the warehouse.
- Service Principal — create (or reuse) an Azure AD app registration with a client secret or certificate. Add the app registration to the target Fabric workspace as a Member (or higher) and grant it read/write access to the warehouse.
- Pick (or create) a target schema where Entegrata can create and manage tables
Connection Details
Fabric Warehouse endpoint hostname, e.g.
<workspace>.datawarehouse.fabric.microsoft.com.Schema inside the warehouse where emitted tables live. Defaults to
dbo. Silver emitters can send each Databricks schema (such as main and metric) to its own target schema (requires platform v1.3.151+) — see Target Schema.Encrypt the connection in transit. Enabled by default. Only disable for legacy servers that cannot negotiate encryption.
Authentication
Fabric endpoints don’t accept SQL logins — Entegrata authenticates with an Azure AD identity. Pick the method that matches how you’ve set up access.- Entra Service Principal
- Entra ID
Application-based authentication using an Azure AD app registration.
Write Modes
- Full Refresh — Entegrata loads all rows into a staging table and atomically swaps it with the target table. Any indexes and keys you’ve added to the target are captured beforehand and reapplied after the swap.
- Incremental Merge — Entegrata writes only rows that changed in the source since the last emission, using the target’s primary key to apply inserts, updates, and deletes.
If your Fabric capacity is paused, updating, or temporarily inactive when an emission runs, Entegrata waits and retries instead of failing the emission (requires platform v1.3.144+).
Naming Convention
Emitted table and column names are transformed to match the convention configured on the emitter (default:snake_case). Configure the convention per emitter to match the downstream tools consuming the replica.