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

(0) Share

Report

Posted on by CU14020458-1

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:

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

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

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

Categories:

Building Power Apps

Microsoft Dataverse with Power Apps

Experimental features

Power Query

Governance & administering

General topics

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

pavanmanideep 576 Power Up Champ - 2025 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @CU14020458-1

There is no supported API's as of today to publish DataFlows Programmatically.

If your architecture supports, you can use Dataflows Gen 2.

Refer this https://otcbi.net/reviving-stuck-dataflows-gen-2-a-no-code-fix-using-rest-apis/?utm_source=copilot.com

Give a thumbs up if this helped you, and mark it as the answer if it solved your problem.

Hope this helps…

Cheers,
PMDY
Microsoft Business Applications MVP
Subscribe to my blog: https://ecellorscrm.com

Was this reply helpful? Yes No
CU14020458-1 3 on at

Like
a
(0)

Report
Copy link

Link copied!

@pavanmanideep Thanks for responding. At the moment, our current architecture does not support this approach. Based on that, is it correct to say there is no other supported workaround for this step and that publishing must remain a manual process for now?

Was this reply helpful? Yes No
Suggested answer

pavanmanideep 576 Power Up Champ - 2025 on at

Like
a
(0)

Report
Copy link

Link copied!

Exactly @CU14020458-1 there is no supported way which is documented, you can raise a Microsoft Support ticket if they can provide you further guidance if there is some undocumented approach.

Also note that if Microsoft team needs to contact their product team, this will add more delay.

Hope this helps.

Give a thumbs up if this helped you, and mark it as the answer if it solved your problem.

Hope this helps…

Cheers,
PMDY
Microsoft Business Applications MVP
Subscribe to my blog: https://ecellorscrm.com

Was this reply helpful? Yes No