Skip to content
  • There are no suggestions because the search field is empty.

Fabric Warehouse - Target environment

Applies to
Platform: Fabric Warehouse

Prepare a Fabric workspace for a Fabric Warehouse project: a warehouse, a lakehouse for the execution log and a Key Vault with service principal secrets. Afterwards you can deploy and load the generated artifacts. The setup applies to all Fabric Warehouse generator configurations, including Dimensional and Dimensional and Mart.

This article shows one possible setup. Microsoft Fabric and Azure Key Vault offer many other configurations, which their documentation describes.

Prerequisites

  • Access to Microsoft Fabric with a capacity on which you can create a workspace, a warehouse and lakehouses.
  • A service principal, an application in Microsoft Entra ID, with a client secret.
  • An Azure subscription in which you can create a Key Vault.

Set up the environment

Store the secrets in a Key Vault

  1. Create a Key Vault, as described in the Azure Key Vault quickstart.
  2. Add the secret client-id with the client ID of the service principal. Azure shows it as Application ID in Enterprise applications.
    Enterprise applications in Azure with the Application ID of the service principal highlighted
  3. Add the secret client-secret with a client secret of the application.
  4. Add the secret tenant-id with the tenant ID. Fabric shows it when you select your profile picture and point to the information icon next to the tenant name.
    Fabric profile panel with the Tenant ID highlighted

The secret names are examples; you enter them as placeholder values. The load notebook reads the secrets with the identity of the user who runs it, so that user needs read access to them.

Create the workspace

  1. In Fabric, select Workspaces, then New workspace.
    Workspaces panel in Fabric with the New workspace button highlighted
  2. Enter a name, for example bgDocumentationWarehouse, and select Apply.
    Create a workspace dialog with the name bgDocumentationWarehouse
  3. Select Manage access, then Add people or groups. Search for the service principal, choose the role Member and select Add.
    Add people dialog with the role Member highlighted

The service principal is now listed as a Member of the workspace. The Member role is sufficient for deploy.ps1 and for the connections of the load notebook.

Manage access with the service principal as Member

Create the warehouse and the lakehouse

  1. In the workspace, select New item, then Warehouse.
    New item button Warehouse item type
  2. Enter a name, for example docu_bgwarehouse, and create the warehouse.
  3. Select New item, then Lakehouse, and create a lakehouse for the execution log, with or without Lakehouse schemas.
    Lakehouse item type

deploy.ps1 needs at least one warehouse and one lakehouse in the workspace. An execution log in a lakehouse with schemas needs a default lakehouse with schemas, see Fabric Warehouse - Placeholder values. If the default lakehouse that deploy.ps1 sets for the load control notebooks has no schemas, make a lakehouse with schemas their default lakehouse.

To keep the notebooks in Git, connect the workspace in its workspace settings under Git integration, as the Microsoft Fabric documentation describes.

Provide source data from a lakehouse

The Stage reads its source tables through the warehouse, with the source system type Microsoft Fabric Warehouse. To read tables of another lakehouse, create a lakehouse with shortcuts to them in the workspace of the warehouse:

  1. Select New item, then Lakehouse. Enter a name, for example lakehouse_shortcut, and select Create.
    New Lakehouse dialog with the name lakehouse_shortcut and the Lakehouse schemas check box
  2. In the Tables folder, open the context menu and choose New shortcut.
    Explorer of lakehouse_shortcut with New shortcut in the context menu of Tables
  3. Select Microsoft OneLake.
    New shortcut dialog with the source Microsoft OneLake
  4. Select the lakehouse that holds the source data and select Next.
    List of data sources with the source lakehouse selected
  5. Select the source tables, then select Next and Create.
    Source tables selected in the New shortcut dialog

The shortcuts appear in the Tables folder:

Tables folder of lakehouse_shortcut with six shortcut tables

The warehouse finds the shortcut tables only after the SQL analytics endpoint of the lakehouse has synchronized its metadata; until then, a query on them fails with Invalid object name.

In the placeholder values, enter the lakehouse name as database_name of the source system and dbo as schema_name for a lakehouse without schemas.

Projects of the other Fabric Warehouse configurations can also read the model objects of a linked project. Fabric Warehouse Stage offers no linked project import.

Check the result

The workspace contains the warehouse and at least one lakehouse, and Manage access lists the service principal as Member. The Key Vault holds the three secrets.

Upload artifacts in Microsoft Fabric

Uploading and running the generated notebooks is described in Fabric Warehouse - Deployment.

Failure symptoms and recovery

Failures of the deployment, such as a missing warehouse or lakehouse, are described in Fabric Warehouse - Deployment. Load failures are described in Fabric Warehouse - Load data - Native Load Control.

Related articles