Microsoft Fabric Destination

The Microsoft Fabric destination is in Private Beta, where we work with early users and customers to test new features and get feedback before making them generally available.

Reach out to Customer Success if you’re interested in enabling this destination for your workspace.

Microsoft Fabric is an analytics platform that provides data engineering, data warehousing, and business intelligence capabilities.

• See the Warehouse Schema guide for more information on how events are mapped to tables in Microsoft Fabric.
• Find the open source code for this destination in the GitHub repository.

Set up access in Microsoft Fabric

Follow the steps in this section to set up access in Microsoft Fabric.

1. Create a warehouse and staging lakehouse

1. Create a Warehouse
2. Create a lakehouse in the same region

RudderStack stages data in the Lakehouse on OneLake before loading it into the warehouse.

2. Register a Microsoft Entra app

1. Register an application in Microsoft Entra ID to create the service principal.
2. Record the Tenant ID and Client ID.
3. Add a client secret and record it.

Copy the client secret’s Value, not its Secret ID. You can’t retrieve the Value after leaving the client secret page.

3. Enable service principal access to Fabric APIs

Ask your Fabric administrator to enable the tenant admin setting Service principals can use Fabric APIs.

If the setting applies only to specific security groups, add the app to an allowed group. This tenant-level setting often requires a different administrator than the person configuring RudderStack.

4. Assign role to the service principal

Assign the service principal the Contributor workspace role or higher.

Follow Give users access to workspaces and assign the app to each workspace containing the warehouse or staging lakehouse.

Contributor is the minimum supported role described in Roles in workspaces — Admin, Member, and Contributor roles are also sufficient.

Important considerations

Service principals can hold workspace roles and inherit the same permissions as users for Fabric API operations. Contributor grants CONTROL on each warehouse and SQL analytics endpoint, providing full read/write access, as described in Workspace roles in Fabric Data Warehouse.

Admin, Member, and Contributor can perform full CRUD operations on Lakehouse data, as described in Workspace roles in Lakehouse. The lower Viewer role grants only CONNECT and ReadData, so it can’t write data or run DDL statements. The workspace role therefore covers the Fabric REST API, OneLake, and SQL endpoint access required for the items in that workspace.

5. Let RudderStack create and maintain the schema

RudderStack creates the namespace schema if it doesn’t exist, creates tables, and alters them as the event schema evolves. You don’t need to create the schema before configuring the destination.

Configure Microsoft Fabric in RudderStack

In the RudderStack dashboard, add Microsoft Fabric as a destination, give it a name, and connect it to your source. Configure the following settings.

Connection settings

Note that:

• Microsoft Fabric supports cloud mode only for all source types.
• Microsoft Fabric’s default collation is case-sensitive, so identifiers retain their original case. Use the same capitalization when querying schemas, tables, and columns.

Sync settings

Load behavior

IPs to allowlist

To enable network access to RudderStack, allowlist the following RudderStack IPs depending on your region and RudderStack plan:

All the outbound traffic is routed through these RudderStack IPs.

Rudder Lookout connects to your warehouse from three of the US addresses: 3.216.35.97, 34.198.90.241, and 54.147.40.62. Lookout uses these addresses for workspaces in every region. If you use Lookout with an EU or IN workspace, allow them too. See Allow Lookout to reach your warehouse.

Consent settings