1.5 — Version Control and Power BI Desktop Projects (.pbip)
DP-600 Domain 1 · Skill 1.5
What You Need to Know
Version control on DP-600 has two sides. In the service, a workspace is connected to Git. On the desktop, a report and its model are saved as a Power BI Desktop project (.pbip): plain text files that Git can track and that you can review in pull requests.
Workspace Git integration (recap)
- Providers: Azure DevOps and GitHub (cloud only). A workspace Admin connects the workspace to one branch and folder.
- Contributors and higher commit workspace changes and update the workspace from Git. Viewers see no Git features.
- Git holds item definitions, not data. Semantic models and reports are stored in the same text formats that PBIP uses.
- Branch out to another workspace to give each developer an isolated feature workspace, then merge with a pull request.
Power BI Desktop projects
Saving as .pbip (File > Save as > Power BI project files) creates a folder instead of one binary .pbix:
Sales/
├── Sales.SemanticModel/ ← model definition (TMDL files in /definition)
├── Sales.Report/ ← report definition (PBIR format)
├── .gitignore ← excludes .pbi/cache.abf and localSettings.json
└── Sales.pbip ← pointer that opens the report and model
| Benefit | Why it matters |
|---|---|
| Readable diffs | A changed measure shows up as a changed line in Git, so you can review it in a pull request |
| TMDL (Tabular Model Definition Language) | One text file per table, with its measures, columns and partitions. You can edit it in VS Code |
| PBIR (enhanced report format) | One file per page or visual, which makes merges and bulk edits possible |
| No data in source control | The local data cache (cache.abf) is git-ignored. Only definitions are versioned |
| CI/CD | Build pipelines can validate the files and deploy them to workspaces through Git integration or the Fabric APIs |
Working practices:
- Edit in Power BI Desktop, or in external tools such as VS Code and Tabular Editor. Power BI Desktop detects outside changes and asks you to apply them.
- Some files (for example
diagramLayout.json) aren't documented for outside editing, so change them only in Desktop. - Publishing from Desktop publishes metadata and the local data cache. Deploying through Git or the APIs deploys metadata only, so the model then needs a refresh.
Key Concept: A .pbix is a binary blob that Git can't diff. A .pbip is a folder of text files (TMDL for the model, PBIR for the report) that Git can track, review and merge.
Exam Traps
- Committing .pbix files and expecting meaningful diffs or merges
- Committing
cache.abf(data) to the repository - Expecting a Contributor to connect the workspace to Git
- Expecting a model deployed through Git to contain data without a refresh
Check your understanding
Practice Scenario
Your BI team wants every change to measures and relationships in a Power BI model to be reviewed in Azure Repos pull requests, with a readable line-by-line diff. What should the developers do?
Log in to save your progress.
Sources
- Power BI Desktop projects (PBIP), Microsoft Learn
- Power BI Desktop project semantic model folder (TMDL), Microsoft Learn
- Power BI Desktop project report folder (PBIR), Microsoft Learn
- What is Microsoft Fabric Git integration?, Microsoft Learn