Deployment Pipelines should allow a workspace to be assigned to multiple pipelines

In an ISV scenario, you may have multiple Production workspace targets that you need to deploy to (i.e. one Production workspace per client).

If that's the case, then it means you need to assign your single "Development/Testing" workspace to multiple pipelines that are each targeting a different target "Production" workspace.

Example

Workspace:

• "DEV" workspace
• "PROD Client A" workspace
• "PROD Client B" workspace
• "PROD Client C" workspace

Once a new version of a report called "Shared Client Report" is available in the "DEV" workspace, you need to deploy that version to all the following target workspaces: "PROD Client A", "PROD Client B", "PROD Client C".

This feature could also be used in a different manner. In a more mature Power BI team that doesn't use very sophisticated CI/CD tooling (i.e., requiring dataset breakdown to store into Git etc.), there may be multiple developers that are doing Power BI development.

All these developers would usually have their own development workspace. Once work is done on that development workspace, they would try to push to a single, centralised, System Integration Testing workspace.

Example

Workspaces:

• "John Doe's DEV"
• "Ann Doe's DEV"
• "SIT" workspace

In this case, the "SIT" workspace needs to be attached to two different pipelines: one managing the release process of artifacts developed within "John Doe's DEV" workspace to SIT, another one managing the release process of artifacts developed with "Ann Doe's DEV" workspace to SIT as well.