Publich PBIP on fabric workspace programatically

[powerbiexpert22]

i have pbip file (zipped) in one of folder in ADLS and i want to publish this file on to fabric workspace in power bi programmatically using python? also i want to extract that pbip file on to pbix in workspace, how to acheive this? can it be done using git integration option in power bi workspace 

[powerbiexpert22]

Hi @Ray_Minds , is there a way to do it programmatically using python?

[Ray_Minds]

Solution:  You can’t directly publish a zipped .pbip file from ADLS to a Fabric workspace.

.pbip is mainly a development format (project-based), while the service expects either a .pbix or artifacts coming through Git integration.

What you can do instead of it :

First, take that zipped PBIP from ADLS and extract it. Once extracted, open the .pbip file in Power BI Desktop and simply do a Save As → PBIX. After that, you can publish it normally to your Fabric workspace.

Now coming to Git integration - yes, this is actually the better approach if you’re thinking long term (CI/CD kind of setup).

Just one thing - Git integration won’t pick a zipped PBIP directly from ADLS. It needs the extracted folder format.

So, you’ll have to unzip it first, push it to Git, and then connect your workspace to that repo.

[powerbiexpert22]

Hi @Ritaf1983 , @KevinChant 

I missed to add that I want to acheive this using Python programatically

[KevinChant]

In that case what you can do is add it to a workspace that is configured with Git integraion (or directly to the repository) and then deploy it either directly with fabric API's or using a tool of abstractions such as the popular fabric-cicd Python library.

Variety of resources available online on how to work with either.

[Ritaf1983]

Hi @powerbiexpert22 

To publish a PBIP (Power BI Project) file from ADLS to a Fabric workspace and manage it effectively, you should use Git Integration. Fabric does not "extract" a PBIP into a PBIX internally; rather, it reads the PBIP folder structure directly from a Git repository to create the corresponding items.

Here is the professional workflow to achieve this:

1. Git Integration Workflow (Recommended)
This is the only way to natively use the PBIP format within a Fabric workspace without manual conversion.

Extract and Push: Since your file is zipped in ADLS, you must first extract the PBIP folder structure. You need to push these folders (the .dataset, .report folders, and the .pbip file) into an Azure DevOps or GitHub repository.

Connect Workspace: Go to your Fabric Workspace settings, select Git integration, and connect it to the repository and branch where you pushed the files.

Sync: Once connected, Fabric will detect the project files. Click Sync (or "Update all"). Fabric will automatically transform the PBIP metadata into a live Semantic Model and Report in the workspace.

2. Converting PBIP to PBIX
There is no automated "server-side" feature in Fabric to convert a PBIP back into a single PBIX file.

Manual Method: Open the PBIP file in Power BI Desktop, then use File > Save As and select the .pbix format. You can then upload this PBIX to the workspace.

Workspace Download: If you use the Git Integration mentioned above, you can subsequently click on the report in the workspace and select Download this file. This will provide you with a .pbix version of the report.

3. Automation via ADLS
If you need to automate this from ADLS:

Pipeline: Use an Azure DevOps Pipeline or GitHub Action to trigger when the ZIP is updated in ADLS.

Deployment: The pipeline should unzip the file and commit the changes to the Git branch linked to your Fabric Workspace.

Rest API: You can use the Fabric Git REST API to trigger the workspace "Update from Git" command programmatically after the files are pushed.

Note: The Power BI Import API currently supports .pbix and .rdl files, but it does not support the .pbip folder structure directly. Therefore, Git Integration is your primary tool for this specific requirement.

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

[KevinChant]

If you configure a workspace with Git integration you can sync/move your pbip project to the repository location so that the report appears in the workspace.