Gen2 (CI/CD, preview) df is not returned by PBI REST API

[smpa01]

@miguel 

TL;DR:
The Power BI REST API endpoint /groups/{groupId}/dataflows does not return Gen2 (CI/CD, Preview) dataflows from Git-enabled workspaces—only Gen1 and standard Gen2 are included. This breaks automation workflows and limits visibility. Users also can’t choose dataflow types in the UI, even after disconnecting Git. Microsoft should update the API to include all dataflow types, and allow UI flexibility to select standard Gen2 dataflows when Git is disconnected.

Issue

When using the Power BI REST API endpoint:

GET https://api.powerbi.com/v1.0/myorg/groups/{groupId}/dataflows

I observed that Gen2 Dataflows (CI/CD, Preview) are not returned in response. Only Gen1 and standard Gen2 dataflows are visible. This behavior is inconsistent and problematic for automation and governance scenarios.

Steps to Reproduce:

    1.Create three types of dataflows in different workspaces:

• Gen1 Dataflow (Workspace_1)

• Gen2 Dataflow (Workspace_1)

• Gen2 Dataflow (CI/CD, Preview) in a Git-enabled workspace (Workspace_2)

2. Invoke the above API with the appropriate {groupId}.

3. Observe the response:

• Gen1 and standard Gen2 dataflows are returned.

• Gen2 CI/CD Preview dataflows are not returned.

Expected Behavior:

• All dataflows, including Gen2 (CI/CD, Preview) ones, should be returned from the same API endpoint, regardless of Git integration status.

Additional Context:

• In a Git-enabled workspace, the only available dataflow creation option is Gen2 (CI/CD, Preview).

• Upon disconnecting Git integration, the option does not revert to standard Gen2 or provide a choice between types.

• This makes it extremely difficult to manage or automate anything involving Gen2 CI/CD dataflows, especially when they're excluded from standard API endpoints.

Desired Outcome:

• Ideally, the /dataflows endpoint should return all types of dataflows—Gen1, standard Gen2, and Gen2 (CI/CD Preview)—regardless of whether the workspace is Git-integrated.
• Additionally, the Power BI UI should allow users to explicitly choose between dataflow types (standard Gen2 vs. Gen2 CI/CD Preview), when Git is connected.
• At a minimum, when Git is disconnected, users should be given the option to create standard Gen2 dataflows rather than defaulting to the preview variant, which currently lacks full API support.

[miguel · Accepted solution]

This is currently expected.

Theres is no API support at the moment for Dataflow Gen2 with CICD support, but we're working on enabling it pretty soon as part of the Fabric REST API.

Stay tuned to the Fabric blog to be notified once we enable the REST API support for Dataflow Gen2 with CICD support

[smpa01]

@miguel can you reflect on this for now?

• Additionally, the Power BI UI should allow users to explicitly choose between dataflow types (standard Gen2 vs. Gen2 CI/CD Preview), when Git is connected.
• At a minimum, when Git is disconnected, users should be given the option to create standard Gen2 dataflows rather than defaulting to the preview variant, which currently lacks full API support.

[miguel]

When you mention the Power BI UI, are you referring to the Fabric UI for creating an item?

At the moment our main goal is reach general availability with the Dataflow Gen2 with CICD. Reaching GA will bring REST API support.

At the moment when you create a Dataflow Gen2 with CICD support you are not required to have a workspace with Git enabled whatsoever. This new item is simply able to support CICD, but it is not a prerequisite to create the item

[lbendlin]

Since you have a Pro license you should open a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi