How to programmatically publish Power BI / Power Query Dataflows after deployment (CI/CD scenario)?

[TEJAK504]

Hi all,

We are working on implementing CI/CD for Power Platform / Power BI across multiple environments (Dev → UAT → Prod), and we’ve run into a blocker related to publishing dataflows.

🔹 Context:

• We deploy solutions and artifacts using Azure DevOps pipelines

• Dataflows are successfully deployed to the target environment

• However, they remain in an unpublished state until manually opened and published in the UI

  🔹 Issue:

  We are unable to find any supported way to programmatically trigger the “Publish” action for dataflows.

  🔹 What we’ve tried:

  • Power Platform CLI (pac)

  • Power BI REST APIs

  • Power Automate (cloud flows)

  • Power Automate Desktop (UI automation approach — not ideal for enterprise pipelines)

    🔹 Current limitation:

    There does not appear to be a supported API to:

     

    Publish Dataflow (equivalent to clicking "Publish" in UI)

     

    🔹 Questions:

    1. Is there any supported API or mechanism to publish dataflows programmatically?

    2. Are there any recommended enterprise patterns for handling this in CI/CD?

    3. Is this capability on Microsoft’s roadmap (e.g., Fabric / Dataflow Gen2)?

       🔹 Current workaround:

       We are currently considering:

       • Manual publish step post-deployment

       • Raising a Microsoft support ticket for confirmation
         
         #power-bi #dataflows #power-platform #ci-cd #azure-devops #fabric

[TEJAK504]

@ToddChitt  Thanks for responding.Currently, these are Power Apps legacy dataflows, not Fabric dataflows. In our case, publishing after deployment remains a manual step, which is quite challenging operationally since we have nearly 40 production environments to manage.

[ibarrau]

Hi. I don't think that's possible. Even if you import the dataflow as json like this link shows:

https://learn.microsoft.com/en-us/rest/api/power-bi/imports/post-import-in-group

The object wasn't prepared for CICD like reports. The only way to make it move between dev-uat-prod would be editing online at dev and use Deployment Pipelines to handle that.

Otherwise you should get rid of them moving that logic to back (DB or warehouse), to the dataset power query or purchasing Fabric for Dataflows Gen2 (I think they don't need that manual publish)

I hope that helps,

[TEJAK504]

@ibarrau Thanks for responding.Currently, these are Power Apps legacy dataflows, not Fabric dataflows. In our case, publishing after deployment remains a manual step, which is quite challenging operationally since we have nearly 40 production environments to manage.

[ToddChitt]

Are you using legacy Dataflows in Fabric? Or the newer Dataflow Gen2 CI/CD object? 

Your reference to the "Publish" operation makes me believe you are using the old type. 

Dataflow Gen2 CI/CD do not have "Publish" operations. You simply Save/Close/Run.

Maybe that is the hang up?