Power BI
CompletedAllow for selecting preexisting Workspaces for different stages of the deployment pipeline.
Volody on 30 May 2020 02:40:37
Our Power BI environment already has existing DEV, QA, and PROD Workspaces for which we'd like to integrate with the new deployment pipelines feature in preview.
Currently the deployment pipelines only allow for you to select 1 preexisting Workspace for which 2 new subsequent Workspaces are created for the other stages. We would like to be able to select all 3 of the Workspaces that represent each stage of the deployment.
Administrator on 15 Jul 2023 13:38:40
This functionality is supported in deployment pipelines.
Assigning a workspace to a Power BI Application lifecycle management (ALM) deployment pipeline - Power BI | Microsoft Docs
- Comments (4)
RE: Allow for selecting preexisting Workspaces for different stages of the deployment pipeline.
Update: we are now deploying all reports through multiple live Power BI apps, but want to retain one Dev and one Test environment.
This means that in addition to allowing selection of existing workspaces for Dev, Test and Live, there needs to be a one-to-many relationship with live workspaces (since 1 app = 1 workspace and cannot be changed).
In other words, allow deployment from Test to multiple live workspaces.
RE: Allow for selecting preexisting Workspaces for different stages of the deployment pipeline.
This is a must-have for most organisations because they will already have Dev, Test and Prod environments set up.
We have fully functioning Test and Prod environments in place and the associated app is being rolled out to the organisation as we speak.
Without the ability to assign those pre-existing environments to each deployment phase, this new feature will be useless to us because it will break all our existing workflows and force us to redeploy all reports to a different/new Prod workspace.
RE: Allow for selecting preexisting Workspaces for different stages of the deployment pipeline.
Currently you need workspace creation rights to set up the deployment pipeline since you can't select existing workspaces. A problem is that no error message is displayed when you try to deploy from the selected workspace in, for example, Development to Test. Clicking "Deploy to production" will only generate a 400 error message in the background. Same with "Deploy to previous stage".
RE: Allow for selecting preexisting Workspaces for different stages of the deployment pipeline.
In addition, this change would support environments where the permission to create new Workspaces is restricted - the existing processes within the enterprise for managing Workspace creation can be maintained, but still allow self-service of assigning workspaces to a Deployment Pipeline.