How to Dynamically Change Dataflow Gen2 Destination During CI/CD Deployment Between Workspaces?

[carlo-spring]

Hi everyone,

Does anyone know how to dynamically change the destination of a Dataflow Gen2 (CI/CD) when deploying it from one workspace to another (e.g., from DEV to UAT or PRO)?

I frequently use Dataflow Gen2 with Git integration, and the biggest issue I’m facing is that every time I deploy a dataflow to a different workspace (UAT or PRO), I have to manually go into each dataflow and change its destination (usually a Warehouse) so it points to the correct workspace environment.

This becomes very inefficient and error-prone, especially when managing many dataflows across environments.

Is there a way to automate this destination switch during CI/CD deployment, maybe through environment variables, scripting, or some feature I might be missing?

Thanks in advance!

[v-veshwara-msft · Accepted solution]

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.

[Bgo5]

I'm just wondering if this feature has been added, as I cannot find a way to dynamically change the output destination during deployment.

[Corujo]

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

[miguel]

I believe this may help:

https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-cicd-alm-solution-architecture

[v-veshwara-msft]

Hi @carlo-spring ,
Just wanted to check if the response provided was helpful. If yes, please consider marking it as "Accepted Solution" to assist others with similar queries. If further assistance is needed, please reach out.
Thank you.

[miguel]

We're working on multiple solutions for this. At the moment you are correct that you have to make the changes in each of the stages.