Are Dataflows Gen2 supported in Fabric Deployment Pipelines (Workspace/Lakehouse parameter change)?

[mustaphaben]

Hi everyone,
We are currently working with Fabric Deployment Pipelines and we need to clarify whether Dataflows Gen2 are fully supported in the deployment process.
Issue
When creating deployment rules, Fabric currently allows us to configure parameters for:
- Pipelines
- Notebooks
However, Dataflows Gen2 do not appear in the list of artifacts that can be configured.
This prevents us from setting deployment rules such as:
- Changing the Lakehouse ID between DEV → UAT → PROD
- Changing the Workspace ID (target environment)
- Applying environment-specific parameterization inside Dataflows Gen2 (for example different paths or different Lakehouse destinations)
Observation
In our deployment pipeline interface, we only see Pipelines and Notebooks, but no Dataflows Gen2.
We would like to confirm whether:
- Dataflows Gen2 are officially supported in Fabric deployment pipelines,
- If not, whether there is a known limitation or a planned roadmap to support this feature,
- Or if there is an alternative approach to parameterize Dataflows Gen2 per environment (DEV/UAT/PROD).
Goal
Our objective is simply to automate the promotion of Dataflows Gen2 across environments while dynamically updating the target Lakehouse and Workspace references.
Any official guidance, confirmation, or documentation link would be greatly appreciated.
Thanks in advance!

[v-echaithra]

Hi @mustaphaben ,

Thank you @ChielFaber , @GeraldGEmerick  for your inputs.

I just wanted to check if the issue has been resolved on your end, or if you require any further assistance. Please feel free to let us know, we’re happy to help!

Thank you 
Chaithra E.

[ChielFaber]

The original Dataflow gen2 is not supported by deployement pipelines, but dataflow gen2 CI/CD are supported by deployement pipelines and I'm using them myself.

When you create a new dataflow gen2 make sure to check the box that ask for Git integration etc. Then the new dataflow gen2 will appear as a dataflow gen2 CI/CD. This entity can be deployed with a deployement pipeline.

Existing dataflow gen2 dataflows can by copied to a new dataflow gen2 CI/CD. When you do this a new entity will be created so make sure any downstream entities reference the new ID.

For more information: https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-cicd-and-git-integration

[GeraldGEmerick · Accepted solution]

@mustaphaben Dataflows Gen2 are not officially supported in Azure Fabric deployment pipelines as of now. However, I believe that Microsoft has announced that support for Dataflows Gen2 in Fabric deployment pipelines will be available by the end of the year. You can find the roadmap for Fabric here: https://roadmap.fabric.microsoft.com/