Assign a workspace to a Microsoft Fabric deployment pipeline

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 different environments of a managed release. 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 assign 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.

Note

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:

1. Open the pipeline.

   

2. In the stage you want to assign a workspace to, expand the dropdown titled Choose a workspace to assign to this pipeline.

3. From the dropdown menu, select the workspace you want to assign to this stage. If you don't see the workspace you want, review the limitations section and make sure that your workspace meets the required conditions.

   

4. 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:

1. Open the pipeline.

2. In the stage you want to unassign the workspace from, select settings.

3. From the settings menu, select Unassign workspace.

   

4. In the Unassign workspace dialogue box, select Unassign.

   

Item pairing

Pairing is the process by which an item in one stage of the deployment pipeline is associated with the same item in the adjacent stage. Pairing is vital for correct deployments. If items aren't paired, even if they appear to be the same, they don't overwrite on a subsequent deployment.

Pairing can happen in one of two ways:

• Deployment: when an unpaired item is copied from one stage to another using the Deploy button, the previously unpaired item is automatically paired with the copy.

• Assigning a workspace to a deployment stage: when a workspace is assigned to a deployment stage the deployment pipeline attempts to pair items. The pairing criteria are:

  • Item Name
  • Item Type
  • Folder Location

If a single item can be identified that matches all three of these criteria then pairing occurs. If more than one item in a single stage matches an item in an adjacent stage, then pairing fails.

Once items are paired, renaming them doesn't unpair the items. Thus, there can be paired items with different names.

See which items are paired

Paired items appear on the same line in the pipeline content list. Items that aren't paired, appear on a line by themselves:

Create nonpaired items with the same name

There's no way to manually pair items except by following the pairing rules described in the previous section. Adding a new item to a workspace that's part of a pipeline, doesn't automatically pair it to an identical item in an adjacent stage. Thus, you can have identical items with the same name in adjacent workspaces that aren't paired.

Here's an example of items that were added to the Test pipeline after it was assigned and therefore not paired with the identical item in the Dev pipeline:

Multiple items with the same name and type in a workspace

If two or more items in the workspace to be paired have the same name, type and folder, pairing fails. Move one item to a different folder or change its name so that there are no longer two items that match an existing item in the other stage.

Considerations and limitations

• 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?

• You can't assign a workspace with Power BI samples to a pipeline stage.

• You can't assign a template app workspace.

Related content

Compare content in different stages.