Skip to main content
Microsoft Fabric connections must be enabled for your Omni instance. Reach out to Omni support to have this feature enabled.
Omni supports the following methods for connecting to Microsoft Fabric:
  • Service principal authentication - Recommended. Omni authenticates with a Microsoft Entra ID app registration, also called a service principal.
  • Entra user password - If you can’t use a service principal, you can use this approach instead. Note that this method will fail for accounts that require multi-factor authentication (MFA).
Choose the method that best fits your team’s security requirements and preferences.

​
Select an authentication method

To view instructions for your authentication method, select it from the dropdown menu on the right side of the page, above the table of contents.
Authentication method selection menu on right side of this page

Select your authentication method from the dropdown to view setup instructions

​
Querying warehouses and lakehouses together

Fabric can query across the warehouses and lakehouses in a workspace. One Omni connection can use this to read from several of them:
  1. In Warehouse or Lakehouse, enter a warehouse. Omni writes table uploads to this item, so it must be writable.
  2. In Include Other Databases, enter the lakehouses and other warehouses you want to model.
Omni then generates views for each item, and you can join tables across them. When using this approach, note that:
  • The same table can show in more than one item. Lakehouse shortcuts can point to warehouse tables, so dbo.orders can exist in both. Model the table from one item only.
  • New shortcut tables can take a few minutes to show in Omni. If a schema refresh runs right after someone adds a shortcut, the new table may be missing. Run the refresh again.

​
Differences from SQL Server

While Fabric uses T-SQL, it doesn’t support all Microsoft SQL Server features. Omni generates SQL that works in Fabric. The differences below affect SQL that you write yourself, and filter results. For the full list, refer to Microsoft’s T-SQL surface area in Fabric Data Warehouse documentation.

​
Troubleshooting

An error like Login failed for user '<token-identified principal>' means that Fabric couldn’t open the warehouse or lakehouse for the service principal. Check that:
  • The Service principals can call Fabric public APIs tenant setting is enabled. If the setting is limited to security groups, the service principal must be in one of the groups. Changes can take up to 15 minutes to apply.
  • The service principal has a role on the workspace.
  • The Warehouse or Lakehouse field matches the item name in Fabric exactly.
  • The Secret field contains the secret Value, not the Secret ID.
  • If you use Entra User Password, the account doesn’t require MFA and has a role on the workspace.
Check whether the client secret expired. To fix it, create a new client secret for the app registration in the Azure Portal. Then, update the Secret field on the connection in Omni.
Omni can read data but can’t create the table for an upload. Check that:
  • The service principal or Entra user has the Contributor role, or higher, on the workspace. Sharing the warehouse item gives read permissions only.
  • The Warehouse or Lakehouse field in Omni contains a warehouse, not a lakehouse.
Fabric warehouses are case-sensitive by default. Change the table and column names in your SQL to match their case in Fabric.
Fabric returns these errors for a short time during a system update, or when the workspace is temporarily unavailable. Run the query again. If the errors continue, check that the Fabric capacity is running and isn’t paused.

​
What’s next?

Now that your database is set up, you can: