Fabric Dataflow APIs – Gen1 Dataflows Not Listed

[Ajhelsing]

Recently, our organization purchased Microsoft Fabric capacity to consolidate our workloads under a single platform.

During some validation checks, we observed behavior that requires clarification:

Dataflows created in Gen1 are not being listed in the Fabric Dataflow APIs. The Fabric APIs only return Gen2 dataflows. For Gen1 dataflows, we still need to use the Power BI REST APIs.

We would like to better understand:

• Is this expected behavior?
• Are Gen1 dataflows intentionally excluded from Fabric Dataflow APIs?
• Is there a roadmap to support Gen1 dataflows in Fabric APIs?
• What is the recommended approach for automation scenarios where both Gen1 and Gen2 dataflows need to be managed?

This clarification would help us design our automation strategy correctly.

Please let me know if any additional details are required-  I’m happy to provide more information.

Looking forward to your insights.

[v-echaithra]

Hi @Ajhelsing ,

Thank you @rohit1991 , @Olufemi7 , @MohdZaid_  for your inputs.
We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.

Thank you.

[Olufemi7]

Hello @Ajhelsing,

Yes, this is expected behavior.

The Fabric Dataflow APIs currently return only Dataflow Gen2 items created in Microsoft Fabric.
Dataflow Gen1 assets are still managed through the Power BI service architecture, which is why they are not returned by the Fabric APIs.

Because of this separation today:

• Fabric APIs → Dataflow Gen2

• Power BI REST APIs → Dataflow Gen1

If your organization is automating both, the recommended approach is to use both API sets until Gen1 dataflows are migrated to Gen2.

Microsoft documentation:
https://learn.microsoft.com/fabric/data-factory/dataflow-gen2-public-apis
https://learn.microsoft.com/rest/api/power-bi/dataflows

[MohdZaid_]

Hey @Ajhelsing  , 

Yes, what you’re seeing is expected behavior. The Microsoft Fabric Dataflow APIs currently only support Gen2 dataflows, and Gen1 dataflows are not included in those APIs. To manage or automate Gen1 dataflows, you still need to use the traditional Power BI REST APIs.

This separation is intentional because Gen2 dataflows are built on a newer architecture that Fabric leverages, while Gen1 dataflows remain on the legacy platform. Microsoft has not yet announced plans to fully integrate Gen1 dataflows into the Fabric Dataflow APIs.

For automation scenarios where you need to manage both Gen1 and Gen2 dataflows, the recommended approach is to use a hybrid strategy:

• Use Fabric Dataflow APIs for Gen2 dataflows management, monitoring, and automation.
• Continue using Power BI REST APIs for any Gen1 dataflows until migration or full API support is available.

If your organization is planning to consolidate, it’s also worth considering migrating key Gen1 dataflows to Gen2 over time to simplify management under Fabric.

If this explanation helped, please mark it as the solution so others can find it easily.

If it helped, a quick Kudos is always appreciated it highlights useful answers for the community.

Thanks for being part of the discussion!

[rohit1991]

Hii @Ajhelsing 

Microsoft Fabric Dataflow APIs currently support Gen2 dataflows only because Gen2 is the Fabric-native architecture. Gen1 dataflows remain Power BI artifacts, so they must be managed using the Power BI REST APIs, not Fabric APIs. Gen1 is not intentionally “hidden”  it’s simply based on a different underlying platform. For automation scenarios involving both types, the recommended approach is to use Fabric APIs for Gen2 and Power BI REST APIs for Gen1 until Gen1 workloads are migrated to Gen2. There is no officially committed public roadmap guaranteeing Gen1 support within Fabric APIs.

[Ajhelsing]

Thanks @rohit1991 . That answers my question.. I just wanted to confirm that I wasn’t missing anything.

So, ideally, if we want to use Get Dataflow Definition using Fabric API, the capacity must be in a running state. If the capacity is paused, it should return an error- is that correct?