Fabric Dataflow APIs – Gen1 Dataflows Not Listed

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!

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