Connect Microsoft Fabric to Rig

    Ingest tables from a Microsoft Fabric Warehouse or from a Lakehouse's SQL analytics endpoint into your warehouse. Rig signs in as a Microsoft Entra service principal that has access to the Fabric workspace.

    Before you start

    • You need an Entra app registration with a client secret, and the app's Directory (tenant) ID and Application (client) ID.
    • You need to be able to add that app to the Fabric workspace with the Viewer role or above.
    • Fabric does not support SQL authentication on this endpoint, so Rig signs in with the service principal.
    • Fabric's SQL connection string uses TCP port 1433. If your organisation restricts outbound or inbound traffic, treat it as SQL Server (TDS) traffic.

    Step 1: Give a service principal access to the workspace

    1. Create an Entra app registration, add a client secret, and note the tenant ID, the application (client) ID and the secret value.
    2. In Fabric, add the app to the workspace that holds the Warehouse or Lakehouse, with the Viewer role or above.
    3. Open the Warehouse or Lakehouse and its settings, and copy the SQL endpoint host. It looks like xxxx.datawarehouse.fabric.microsoft.com.
    4. Note the exact name of the Warehouse or Lakehouse.

    Reading tables
    The Fabric data plane lets you grant a service principal SELECT on specific tables, so you can restrict what Rig reads to the objects you want.

    Step 2: Connect it in Rig

    Adding a source needs a workspace owner, or a role with the Manage connections permission, on a workspace where you manage your own connections. If the Connectors tab says “Data ingestion for this workspace is managed by Rig”, ask an owner or Rig support to add the source.

    1. In Rig, open Connections, choose the Connectors tab and go to Sources & actions.
    2. Search for Microsoft Fabric (Warehouse / Lakehouse SQL endpoint), open the card and click Connect.
    3. SQL endpoint host: the SQL endpoint host from the item's settings.
    4. Warehouse / Lakehouse name: the exact name of the Warehouse or Lakehouse.
    5. Schema: leave it as dbo unless your tables live in another schema.
    6. Entra tenant ID: the directory (tenant) ID of the app registration.
    7. Entra application (client) ID: the application (client) ID of the app registration.
    8. Entra client secret: the client secret value you created.
    9. Click Continue. Rig checks the credentials and lists the streams it can reach, so choose the ones you want and click Connect.
    10. The source then syncs on its schedule, which is nightly unless you change it. To load data straight away, click Sync on its row; Test pulls a small sample first if you want to check the connection.

    What Rig pulls in

    Microsoft Fabric lands in its own fabric schema in your warehouse:

    • Tables in the schema: the tables Rig can reach in the schema you set, which you choose from a list when you connect. What you see depends on your own warehouse.

    Good to know

    • Give the Warehouse or Lakehouse name when you connect. Fabric otherwise opens the master database, which holds no user tables.
    • Microsoft documents occasional transient errors during Fabric system updates. A retry after a few minutes clears them.
    • To disconnect Microsoft Fabric, click the bin icon on the source's row under Sources & actions. Only whoever connected the source or a workspace owner can do this, and data already synced stays in the warehouse.

    What people use this for

    • Combine Fabric tables with your other sources
    • Let AI tools query Fabric data
    • Read a Lakehouse through its SQL endpoint

    More ideas for using Microsoft Fabric

    Was this guide helpful?