After Creating Power BI Deployment Pipeline, in future if we want to add a new workspace to the pipeline, we dont have ability.
Looks like we need to delete the whole deployment pipeline and recreate to add one more state.
It would be nice to have this functionality
5 Comments
- lmatthiasNew Member
This is a much needed feature.
- fbcideas_migusrNew MemberStatus added:Needs Votes
- dzebrowitz
Advocate I
If a deployment pipeline is built with 2 stages for instance and we need to add a third stage/workspace to the deployment pipeline, that is currently not possible. We shouldn't need to delete and recreate the deployment pipeline from scratch. - MaryanneBSAFrequent VisitorI discovered this the hard way. After configuring a deployment pipeline to promote from development to test, including deployment rules for multiple semantic models, to find it is not then possible to add a production environment to this existing pipeline. The only resolution currently is to delete the existing pipeline and all it's deployment rules, to then create a new pipeline with the additional environment and reconfigure all of the deployment rules again from memory (as you can't reference a deleted deployment pipeline and can't add the new one before deleting the old one). The consideration of creating all deployment pipelines with the maximum of 10 stages as a default position, allowing editing of workspace assignment at later date, has crossed my mind - but would only help if the stage is added to the end of the process. When using workspaces containing multiple lakehouses and semantic models, at best this requires very specific documentation of repointing per model and per stage, along with a ton of manual rework should a stage need to be added at the end or in the middle of the process (eg Training environment).
- tom_vanleijsen
Advocate I
Absolutely a must have for deployment pipelines. In our organization we introduce new regions regularly for our customers to use our reporting solution and it would be nice if this can be achieved without re-creating a deployment pipeline. As a workaround we now created a deployment pipeline with as many stages as possible. But not an ideal situation.
Recent ideas
Expose Refresh Warnings and Informational Messages via Notifications and API
When a Power BI semantic model refresh completes successfully, the status shows Completed, even when the refresh details contain warnings or informational messages that require attention. Please pro...Jashwanth_K1 hour agoMicrosoft EmployeeNew19Views6likes0CommentsInvoke Pipeline Task - Workspace Identity Authentication
Currently, the Fabric Data Factory Invoke Pipeline task uses the user's credentials who saved the pipeline to then authenticate to the Azure Data Factory to execute the ADF pipeline. When that user'...dzebrowitz6 hours agoAdvocate IPlanned1.8KViews61likes5CommentsFabric Pipeline should run as workspace identity
Currently, Microsoft Fabric pipelines run under the identity of the last user who modified them, which can cause disruptions when tenant administrators make changes to security policies, such as enab...pellitteris6 hours agoAdvocate IINew1.4KViews27likes3CommentsBring Back separating Power BI artifacts on a per web page basis
Previously, the ability to have different artifacts open on different web tabs was enabled. This was beneficial if you wanted to differentiate what environments you were in, working across three diff...zoe-dean7 hours agoNew MemberNew53Views8likes0CommentsREST API Should expose credentials used in connections
When a consultant leaves a client, it's important to clean up any connections that may have the consultants credentials embedded within. I'm able to use the Fabric CLI to get the managed connections ...PeterDaniels7 hours agoAdvocate IIINew20Views7likes0Comments