Assign a workspace to a Microsoft Fabric deployment pipeline
Microsoft Fabric is in preview.
Deployment pipelines enable you to assign and unassign workspaces to any stage in a pipeline. This capability is important for organizations that already have workspaces that are used as development, test, and production environments. In such cases, you can assign each workspace to its corresponding pipeline stage, and continue working in your usual flow.
Assign a workspace to any vacant pipeline stage
To assign a workspace to a pipeline, the pipeline stage you want to assign the workspace to has to be vacant. If you want to assign a workspace to a pipeline stage that already has another workspace assigned to it, unassign the current workspace from that stage and then continue with assigning the new workspace.
Before you assign a workspace to a pipeline stage, review the limitations section and make sure that the workspace meets the required conditions.
Before you assign or unassign a workspace to a pipeline, consider that every time you deploy to a vacant stage, a new workspace is created.
To assign a workspace to a pipeline stage, follow these steps:
Open the pipeline.
In the stage you want to assign a workspace to, expand the dropdown titled Choose a workspace to assign to this pipeline.
From the dropdown menu, select the workspace you want to assign to this stage.
Select Assign a workspace.
Unassign a workspace from a pipeline stage
You can unassign a workspace from any pipeline stage. If you want to assign a different workspace to a pipeline stage, you first have to unassign the current workspace from that stage.
To unassign a workspace from a pipeline stage, follow these steps:
Open the pipeline.
In the stage you want to unassign the workspace from, select settings.
From the settings menu, select Unassign workspace.
In the Unassign workspace dialogue box, select Unassign.
After assigning a workspace to a deployment pipeline stage, if there are any adjacent stages already assigned, deployment pipelines attempts to create the connections between the items (such as reports, dashboards, and datasets) in the adjacent stages. During this process, deployment pipelines checks the names of the items in the source stage and the stages adjacent to it. Connections to items in adjacent stages, are established according to the item's type and name. If there are multiple items of the same type with the same name in the adjacent stages, assigning the workspace will fail. To understand why this happens and resolve such cases, see I can't assign the workspace to a stage?
Connections between items are only established when you assign a workspace to a pipeline stage. Adding a new item to a workspace that's part of a pipeline, doesn't trigger the creation of connections between that item and identical items in adjacent stages. To trigger forming a connection between a newly added item in a workspace stage and its equivalent item in an adjacent stage, unassign and reassign the workspace that contains the newly added item.
You must be an admin of the workspace.
The workspace isn't assigned to any other pipeline.
The workspace must reside on a Fabric capacity.
To assign a workspace, you need at least workspace member permissions for the workspaces in its adjacent stages. For more information, see [Why am I getting the 'workspace member permissions needed' error message when I try to assign a workspace?](../troubleshoot-cicd.yml#error-message-workspace-member-permissions needed-)
You can't assign a workspace with Power BI samples to a pipeline stage.
You can't assign a template app workspace.