Overview
Emit collected data from Entegrata into a Microsoft Fabric workspace through its SQL endpoint. Emission is available to customers on both hosting models. Destination type: SQL database (Microsoft Fabric SQL endpoint)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 target database.
- 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 target database.
- Pick (or create) a target schema where Entegrata can create and manage tables
Connection Details
Fabric SQL database server name, e.g.
<server-id>.database.fabric.microsoft.com. Copy it from the Data Source= value in Fabric (database → Settings → Connection strings). Enter only the hostname: omit any tcp: prefix and the ,1433 port suffix, and set the port in Port.Full database name, including the GUID suffix, e.g.
my_database-00000000-0000-0000-0000-000000000000. Copy it from the Initial Catalog= value on the same Connection strings page. The short item name alone fails with error 40532.Schema inside the database 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, unique keys, and foreign 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 in a single
MERGE.
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.
Troubleshooting
Error 40532: Cannot open server ... requested by the login
Error 40532: Cannot open server ... requested by the login
Fabric received the sign-in but could not route it to a database. Check these items:
- Host: use only the
<server-id>.database.fabric.microsoft.comhostname from theData Source=value on the Connection strings page in Fabric. Omit anytcp:prefix and the,1433port suffix. - Database: use the full name from
Initial Catalog=, including the GUID suffix. The short item name fails. - Access: make sure the identity has access to the Fabric workspace and the database.
