Git integration in Power BI is a game-changer for us. It simplifies version control, which is a big win for anyone working with Power BI projects.

Over the years, the team behind Power BI has worked on refining and expanding the capabilities of this tool, with the .pbip format being a key milestone. This format allows for a more streamlined and organized way of handling Power BI projects, making it easier for teams to collaborate, manage versions, and maintain consistency across different environments.

With the introduction of features like Git integration and deployment pipelines, the value of the .pbip format has been further amplified. These features leverage the structured nature of .pbip files to ensure more efficient and error-free project management. As a result, users can enjoy a more seamless experience in developing, deploying, and maintaining Power BI projects, underscoring Microsoft’s commitment to continuous improvement and innovation in the realm of data analytics and business intelligence.

Before this, managing versions of Power BI projects was a manual process, involving tedious and error-prone methods. Basically there was no Continuous Integration process for working with Power BI files (.pbix). Analysts and developers often had to rely on naming conventions or external version control tools (like Sharepoint), leading to inefficiencies and a lack of a streamlined process.

Continuous Deployment part of CI/CD process is already covered by Deployment pipeline. It streamlines the process of moving content across different environments – from development to testing, and finally to production. This structured approach brings numerous advantages. It ensures consistency and accuracy of reports across environments, reduces the risk of errors during deployment, and significantly accelerates the release process. By automating the movement of content, the deployment pipeline minimizes manual interventions, thus boosting productivity and enabling a more reliable and agile workflow. This integration with Git further amplifies these benefits, making the management of Power BI projects more seamless and efficient than ever before.

No more juggling with external tools or complex setups. This guide will walk you through the basics, so you can get started without a hitch.


Software we are going to use: Visual Studio Code, Power BI Desktop, Internet browser of Your choice.

Software we are going to need: Power BI workspace assigned to Premium/Fabric Capacity and Pro for User or Power BI workspace assigned to Premium Per User and PPU for User.

Here’s what we’re doing with Git in Power BI:

    1. Set up a Git Repository with Azure DevOps: Just a few clicks and you’re up and running.
    2. Get Your Machine Ready: You’ll get your local setup connected to Azure DevOps in no time.
    3. Work with Power BI Projects: Save your Power BI reports as PBIP files in your new Git folder. This way, they’re ready for version control.
    4. Make and Share Changes: Commit your changes and push them up to Azure Repos.
    5. Synchronize with Power BI Workspaces: Set up your Power BI workspace to play nice with Git, and watch your files sync up automatically.
    6. Collaborate like a Pro: Work with your team by branching off, making changes, and merging them back in after review. It’s all about keeping the workflow smooth and the reports accurate.

Step by step instruction

1. Set up a Git repository in Azure DevOps (Azure Repos).

    • Navigate to Azure DevOps and select or create your organization for the project.
    • Click New Project to create a new project, enter the project name, and then click Create.

2. Get Your Machine Ready.

There are many ways to clone your repo to your local machine. Here is the one I consider as the easiest.

  • In Azure DevOps go to Repos, Files and use the Clone in VS Code button to open the repository in Visual Studio Code. (If you don’t have Visual Studio Code installed, this won’t work for you, fortunately you can easily download it from its official site).

    • Create a new folder by right-clicking on the canvas and selecting New, Folder when prompted by VS Code and select it as the repository destination.

    • You will then be asked if you want to open the cloned repository – choose Open.

3. Create and manage Power BI Projects.

    • Open your Power BI report or create a new one with the desired semantic model.
    • If you have not previously enabled the option to save Power BI projects (.pbip), you will need to do so now: in Power BI Desktop go to: File, Options and settings, Options, Preview features, select the checkbox for Power BI Project (. pbip) save option.

    • Now we can save the report as a PBIP file in your Git project folder. Go to File, Save as, select .pbip as the extension and click Save.

4. Save and push changes to repository.

    • Go to your Visual Studio Code window, notice that the Source Control tab on the right-hand side bar has notifications about changes we have made to the repo. Open this tab.

    • Write a commit message, click the down arrow next to Commit and select Commit & Push

    • You will be asked to stage your changes first, select Yes.

5. Create a premium workspace and enable Git integration in Power BI.

    • Go to Power BI Service and create a new workspace.
    • Fill in the workspace details, making sure you select Premium or Fabric capacity under Advanced.


    • In the workspace settings, link your Azure DevOps repository by selecting “Connect and sync.”
    • After a few seconds, you will see that the report you created and pushed from your local repository to the remote master branch has been deployed to the Power BI Service workspace.

6. Collaborate with branches and pull requests

    • Let’s create a branch for our new changes. Select the ellipsis next to Source Control, Branch and Create Branch…

    • Enter a name for your branch in the ribbon and confirm with Enter.
    • Open your Power BI report, make some changes there – I’ve added a line chart. Then save as .pbip in your local repository.
    • Go to VS Code, notice, that you have new messages in Source Control tab. Write a commit message, then select Commit & Push.
    • Go to your Azure DevOps project:
    • In Azure DevOps, navigate to your branch and main branch.

    • Create a pull request to merge your changes into the main branch.

    • Review and approve the pull request and complete the merge.
    • In your Power BI workspace you’ll notice a notification on the Source Control button about new changes made to master branch, apply the pending changes by clicking Source Control, Update all.

    • Refresh and deploy changes

Remember to refresh your semantic model in Power BI Service because the report will only have metadata in this type of deployment (as just metadata is saved in Git).


In brief, the integration of Git with Power BI, powered by Microsoft Fabric, revolutionizes the way teams collaborate on BI projects. It enables whole teams to work simultaneously with a clear version control system and integrates with deployment pipelines for smooth transitions from development to production. This synergy ensures that BI solutions are developed, tested, and deployed with greater efficiency and teamwork, setting a new standard in the industry.

Thanks to the implementation of CI/CD practices, it’s now possible to introduce robust release management and deployment management practices. These enhancements significantly improve the overall quality and reliability of BI solutions, fostering an environment where best practices in both release and deployment management can thrive.