Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
It would be really nice if the deployment pipelines updated the destination lakehouse or warehouse of a dataflow gen 2 and still show synced across workspaces. Barring that, it would be great if the destination lakehouse or warehouse could be parameterized for use in a deployment pipeline.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Updating the Mashup.pq is actually something that would trigger a commit and not something that we would recommend as it woudl be considered a change between the Dataflow that you have across workspaces.
Fundamentally, you want the same Dataflow definition across all environments, but they should have the right context as to what items they should be getting the data from OR loading the data to.
The article below explains in detail with tutorials how you can set the best solution architectures with a Fabric deployment pipeline in mind:
CI/CD and ALM solution architectures for Dataflow Gen2 - Microsoft Fabric | Microsoft Learn
Do feel free to post any other ideas if you think that there's any functionality that should be extended or improved on