Forum Discussion
How to Dynamically Change Dataflow Gen2 Destination During CI/CD Deployment Between Workspaces?
Hi carlo-spring ,
Thanks for raising this in Microsoft Fabric Community, and also thanks to miguel for addressing it.
As mentioned, currently, there's no built-in way to dynamically change the output destination during deployment, and it requires manually updating the destination in each environment. However, the product team is actively working on addressing this.
As noted in the Fabric roadmap, support for parameterizing the Dataflow Gen2 output destination is planned for public preview in Q3 2025. This should help streamline CI/CD deployments across workspaces once available.
For now, continuing with manual updates remains the approach until that feature is released.
Hope this helps. Please reach out for further assistance.
Please consider marking the helpful reply as Accepted Solution to help others with similar issues.
Thank you.
Hi carlo-spring ,
Thanks for raising this in Microsoft Fabric Community, and also thanks to miguel for addressing it.
As mentioned, currently, there's no built-in way to dynamically change the output destination during deployment, and it requires manually updating the destination in each environment. However, the product team is actively working on addressing this.
As noted in the Fabric roadmap, support for parameterizing the Dataflow Gen2 output destination is planned for public preview in Q3 2025. This should help streamline CI/CD deployments across workspaces once available.
For now, continuing with manual updates remains the approach until that feature is released.
Hope this helps. Please reach out for further assistance.
Please consider marking the helpful reply as Accepted Solution to help others with similar issues.
Thank you.
I'm just wondering if this feature has been added, as I cannot find a way to dynamically change the output destination during deployment.
There is a way to do it, but it’s inconvenient. Basically, you can create variables for the workspace_id and the lakehouse_id in a variable library, and then only from GitHub you can change the destination by replacing the workspace_id and lakehouse_id with the variables created in the library.
In this article, the examples of what needs to be modified in the mashup.pq file in GitHub are shown in the final section.
https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-variable-references
