Skip to content

Deploy a Data Storage Unit in Fabric/OneLake

With version 2024.06, Sidra starts supporting Microsoft Fabric as a DSU.

In a Fabric DSU, data will be ingested in Fabric/OneLake instead of Databricks. Sidra users doesn´t need to do anything different, just by creating a Data Intake Process in a Fabric DSU, Sidra takes care of all automatically

Each Provider will be reflected as a Lakehouse, automatically created by the DIP. Data will be stored as Delta in OneLake and each Entity will be represented by a Table in the Lakehouse.

More information about Fabric in Microsoft site.

Deployment

Entra ID user

Fabric APIs are currently in preview and most methods are does not support to be invoked by a Service Principal. This is something that will be fixed soon, but, in the meanwhile, it means you will need to create an Entry Id user.

This user must not require Multifactor Authentication (MFA) and needs to have a Power BI Pro license assigned.

In future releases, when Fabric APIs support a Service Principal, this step will not be needed anymore.

Take note to the Fabric User Object Id because it will be needed later.

Power BI Tenant settings

In Power BI Admin Portal, go to "Tenant settings" and make sure that "Users can create Fabric items" is Enabled.

Tenant Settings

In case you don´t want to enable for the entire organization, you can use a group, as in the image. Make sure to include in that group: - The Entra Id user you have created - The Sidra Manager Service Principal created by the pre-deployment script. You can find it in the output of the script execution as "App Registration Manager Id":

AAD applications
----------------------------------------------------------------
App Registration Identity Server Id: 00000000-0000-0000-0000-000000000000
App Registration Manager Id: 00000000-0000-0000-0000-000000000000
App Registration Manager Object Id: 00000000-0000-0000-0000-000000000000
----------------------------------------------------------------

Additional permissions

Sidra Manager Service Principal will now require the following permissions. You don´t need to care about it, they will be granted by the pre-deployment script.

In case you are updating from an older versions, an updating script is provided to grant those additional permissions.

  • Power BI Service
    • Capacity.ReadWrite.All
    • Item.ReadWrite.All
    • OneLake.ReadWrite.All
    • Tenant.ReadWrite.All
    • Workspace.ReadWrite.All
  • Azure Subscription
    • Role Based Access Control Administrator

Sidra deployment

The ARM template now have an extra parameter DsuType which you can use to pick between Databricks and Fabric.

If you choose Fabric, some extra parameters related with the Entra Id user has to be provided:

Parameter name Description Example
Default DSU Type Type of DSU to deploy. It can be 'Databricks' or 'Fabric'. The default value is Databricks. Fabric
Fabric User Fabric user, this value will be mandatory if you selected dsuType = Fabric [email protected]
Fabric Password Fabric password, this value will be mandatory if you selected dsuType = Fabric 000000-0000-0000-0000-000000000000
Fabric User Object Id Fabric user object id, this value will be mandatory if you selected dsuType = Fabric 000000-0000-0000-0000-000000000000
Sidra Admin Object Id Admin Sidra object id, this value will be mandatory if you selected dsuType = Fabric 000000-0000-0000-0000-000000000000