Black Friday50% off your first month on any monthly plan with EARLY50 See plans
All 35 lessons
  1. Start here: cloud, data, Fabric and Power BI basics

    1. 1. Start here: the exam, the plan and what you already know
    2. 2. Cloud in plain words: SaaS, PaaS, IaaS and where Fabric fits
    3. 3. Data basics: files, tables, formats and the lakehouse idea
    4. 4. A tour of Microsoft Fabric: OneLake, workspaces and items
    5. 5. Power BI in plain words: semantic models, reports and DAX
  2. Prepare data: get data in (exam area 2, 45-50%)

    1. 6. Connect to data and find it: connections, gateways, OneLake catalog and Real-Time hub
    2. 7. Choosing a data store: lakehouse, warehouse or eventhouse
    3. 8. Use data without copying: shortcuts, mirroring and OneLake integration
    4. 9. Ingest data: Dataflow Gen2, pipelines, Copy job and notebooks
    5. 10. Power Query in Dataflow Gen2: filter, data types, merge and new columns
    6. 11. Messy data: duplicates, missing values and nulls
  3. Prepare data: transform and query (exam area 2)

    1. 12. Views, functions and stored procedures in T-SQL
    2. 13. Build a star schema in a lakehouse or warehouse
    3. 14. Aggregate, join and enrich: SQL and PySpark side by side
    4. 15. Query with the Visual query editor and SQL
    5. 16. Query with KQL
    6. 17. Query with DAX: DAX query view and EVALUATE
  4. Design and build semantic models (exam area 3, 25-30%)

    1. 18. Choose a storage mode: Import, DirectQuery, Direct Lake and Dual
    2. 19. Relationships: star schemas, bridge tables and many-to-many
    3. 20. DAX foundations: measures, filter context, CALCULATE and variables
    4. 21. DAX functions the exam tests: iterators, table filters, windows and information functions
    5. 22. Calculation groups, dynamic format strings and field parameters
    6. 23. Composite models and large semantic model storage format
  5. Optimize models, then secure them (exam areas 3 and 1)

    1. 24. Direct Lake in depth: fallback, refresh and the two flavors
    2. 25. Incremental refresh for semantic models
    3. 26. Faster reports and DAX: finding and fixing slow queries
    4. 27. Who can see what: workspace roles and item permissions
    5. 28. Fine-grained security: rows, columns, objects and files
    6. 29. Governance: sensitivity labels and endorsement
  6. Lifecycle, then exam practice (exam area 1)

    1. 30. Version control: Git integration and Power BI projects (.pbip)
    2. 31. Deployment pipelines and impact analysis
    3. 32. XMLA endpoint and reusable assets: .pbit, .pbids and shared semantic models
    4. 33. Mock exam 1
    5. 34. Final review and exam day: every decision on one page
    6. 35. Mock exam 2
See the leaderboard

20 min

Version control: Git integration and Power BI projects (.pbip)

Connect a workspace to Git and save Power BI work as a project for source control.

By the end of this lesson you can

  • Connect a workspace to an Azure DevOps or GitHub branch and folder
  • Tell Commit from Update, and resolve a conflict in the Source control pane
  • Save a Power BI file as a project (.pbip) and name what each folder holds
  • Pick the least-privilege role for each Git action

From earlier lessons · 1 of 2

Juniper Coffee's finance semantic model is the approved source for all budget reports. You need report builders to see it as the official model in the OneLake catalog. What should you apply?

Pick one answer.

From earlier lessons · 2 of 2

A semantic model has a row-level security role for the North region. Which user does that role filter?

Pick one answer.

Two Juniper Coffee analysts edit the same Store Sales report file. Each saves a copy to a shared folder. On Friday, one copy overwrote a new Gross Margin measure. Nobody can tell what changed, or when. Your manager wants every model change tracked, reviewed and reversible.

[6]

What Git integration does

Exam depth: know it cold.

Git is a version control system. It keeps every saved version of your files in a repository (repo). Each saved version is a commit. A branch is a separate line of work inside the repo.

Git integration connects one Fabric workspace to one branch, and optionally one folder, in a repo. Each item is saved as text files that describe it. Workspace folders are kept, up to 10 levels deep.

Supported providers, cloud versions only:

  • Azure DevOps
  • GitHub
  • GitHub Enterprise

Your Fabric admin must allow Git integration. My workspace can't connect to Git.

[293][294]

Exam depth: recognize it.

The items an analytics engineer uses are supported, including:

  • Lakehouse, Warehouse, Notebook, Dataflow Gen2 and Pipeline.
  • Power BI Report (generally available) and Semantic model (preview).

A semantic model lands in Git as a folder of TMDL text files, covered below. Unsupported items are ignored: not saved, not synced, not deleted.

Git holds definitions, never data. A model's imported rows, a lakehouse's tables and its files all stay out of Git.

[293][299][300]

Connecting and the first sync

Exam depth: know it cold.

Only a workspace Admin can connect a workspace to Git. After that, anyone with the right role can work in it.

On the first sync, Fabric makes both sides match:

  • If one side is empty, content copies from the side that has it.
  • If both have content, you choose a direction.
    • Commit exports the workspace and overwrites Git.
    • Update overwrites the workspace with Git, after a confirmation.

Each user signs in to Git with their own account. The connection is per user, not shared.

[294]

Try it in Fabric

You need the Admin role on a trial workspace and an empty Azure DevOps repo.

  1. Open the workspace and select Workspace settings.
  2. Select Git integration, then Azure DevOps, then Connect.
  3. Pick the Organization, Project and Git repository.
  4. Pick the Branch, such as main, and type a Git folder name.
  5. Select Connect and sync. Each item now shows its Git status.
  6. Edit a report, then open Source control at the top of the workspace.
  7. Under Changes, tick the report, add a message and select Commit.

Open the repo in Azure DevOps. The report is now a folder of text files.

[294][295]

Workspace settings with Git integration selected. The connect section shows Organization, Project, Git repository, Branch set to main and a Git folder field, with the Connect and sync button highlighted.
Microsoft Learn, CC BY 4.0

[298]

Commit and Update in the Source control pane

Exam depth: know it cold.

The Source control icon shows how many items differ between the workspace and the branch. Open it to see two lists.

CommitUpdate
DirectionWorkspace to Git.Git to workspace.
Listed underChanges.Updates.
Pick items?Yes, choose which items.No, always the whole branch.
Blocked whenThe branch has updates you haven't taken.The same item changed on both sides.

You sync one direction at a time. Each item shows a Git status: Synced, Uncommitted changes, Update required or Conflict.

[294]

The Source control pane showing the current branch, a Changes tab with 2 items and an Updates tab. One changed item is selected, with a commit message box and Commit and Undo buttons.
Microsoft Learn, CC BY 4.0

[294]

You are an analytics engineer at Juniper Coffee. A teammate merged a fixed Store Sales report into main. Your workspace is connected to main and shows 1 item under Updates. You also changed the Budget semantic model and haven't committed it. You need both changes in Git. What should you do first?

Pick one answer.

When both sides changed: conflicts

Exam depth: know it cold.

A conflict means the same item changed in the workspace and in the branch. Its status shows Conflict. Select Update, then Resolve conflicts. For each item, choose one:

  • Accept incoming changes: the Git version replaces the workspace version, which is lost.
  • Keep current content: the workspace version stays. It becomes Uncommitted changes, so commit it next.

Not sure which side is right? An Admin selects Checkout new branch. It creates a branch from the last synced commit and keeps your workspace as it is. Commit there, resolve and merge the branches in Git, then switch the workspace back.

[296]

You are an analytics engineer at Juniper Coffee. The Regional Sales semantic model shows Conflict. You know your workspace version is correct and the branch version is outdated. You need your version to end up in Git. What should you do?

Pick one answer.

[296]

Feature workspaces and who can do what

Exam depth: recognize it.

Teams often keep a shared dev workspace on main. Each person works in a feature workspace on their own feature branch. Finished work returns to main through a pull request, a request to merge one branch into another.

Branch out to another workspace sets this up. It creates a branch from the last commit and connects a new or existing workspace to it.

ActionLowest workspace role
Connect, disconnect, sync settingsAdmin.
Commit and UpdateContributor, with write access to the items.
Branch out to another workspaceContributor.
Checkout new branch, Switch branchAdmin, unless a setting lets Contributors.
See Git status at allContributor. Viewers see nothing.

[294][297]

Commit sends your work to Git. Update brings Git's work to you. Never both at once. Picture: Sticky-note sketch style: two yellow sticky notes on a corkboard.

Power BI Desktop projects (.pbip)

Exam depth: know it cold.

A normal Power BI Desktop file (.pbix) is one binary file. Git can store it, but can't show what changed inside.

A Power BI project (.pbip) saves the same report and semantic model as folders of plain text files. Git can then show each changed line, and two people can merge their work.

  • Create one with File > Save as, type Power BI project (*.pbip).
  • You can save it back as a .pbix the same way.
  • Open it by double-clicking the .pbip file, or the definition.pbir file in the report folder.

PBIP is generally available; no preview switch is needed to save one.

[300][303]

text
StoreSales/
StoreSales.pbip shortcut that opens the report
.gitignore
StoreSales.Report/
definition.pbir which model the report uses
definition/ PBIR: pages and visuals as JSON
StoreSales.SemanticModel/
definition.pbism model settings
definition/ TMDL: one .tmdl file per table
.pbi/cache.abf local copy of the data
.pbi/localSettings.json your own machine's settings
Juniper's Store Sales report saved as a project. The two .pbi files are listed in .gitignore, so Git skips them.

[300][301][302]

Exam depth: recognize it.

Each folder has a newer text format and an older one.

FolderNewer formatOlder format
.SemanticModelTMDL: a definition folder, one file per table, role and culture.TMSL: one large model.bim JSON file.
.ReportPBIR: a definition folder, one JSON file per page and visual.PBIR-Legacy: one report.json file.

Both newer formats are easier to read and merge. PBIR is generally available and now the default. Power BI converts a legacy report to PBIR when you edit and save it. Fabric Git integration always writes models as TMDL.

[299][301][302]

text
table Sales
measure 'Gross Margin' = SUM(Sales[Revenue]) - SUM(Sales[Cost])
formatString: $ #,##0
column Revenue
dataType: decimal
sourceColumn: Revenue
column Cost
dataType: decimal
sourceColumn: Cost
TMDL reads like an outline. This is part of tables/Sales.tmdl in Juniper's model. Indentation shows what belongs to what.

[304]

[300][301]

Match

Match each project file to what it does

Pick an item on the left, then its match on the right.

[300][301][302]

You are a BI developer at Juniper Coffee. You clone the repo that the dev workspace syncs to. You find StoreSales.Report and StoreSales.SemanticModel folders but no .pbip file. You need to edit both the report and the model in Power BI Desktop. What should you open?

Pick one answer.

[300]

Exam-style practice

You are a data analyst at Juniper Coffee. Three analysts build one report and its semantic model in Power BI Desktop. In code review, you need to see exactly which measures and visuals each person changed. What should the team do?

Pick one answer.

[300][301]

You are an analytics engineer at Juniper Coffee. A new finance workspace must connect to Git with least privilege. One engineer will connect it to the repo. Three analysts will edit semantic models and commit their changes. Which roles should you assign?

Pick one answer.

[294]

FlashcardsIndex cardsFlashcards ⚡

Card 1 of 15

[293][294][296][297][300][301][302]

Worth keeping

  1. A workspace connects to one branch and folder in cloud Azure DevOps or GitHub; only an Admin connects it.
  2. Commit sends workspace changes to Git; Update pulls the whole branch into the workspace.
  3. Conflicts: keep current content and commit, or accept incoming changes.
  4. A .pbip saves the model as TMDL and the report as PBIR, so Git can diff them.
  5. .gitignore keeps cache.abf data out; open definition.pbir if there's no .pbip.

On the job

At Juniper Coffee, the analytics engineer keeps the Store Sales project in a folder that is a clone of the team repo. She adds a Gross Margin measure in Desktop and saves. Git shows one changed line in Sales.tmdl, not a new 80 MB file. She pushes her branch and opens a pull request. A colleague reads the DAX, asks for a format string, and approves. After the merge, the dev workspace shows Update required. One click on Update brings the new measure into Fabric. Nobody emailed a .pbix, and Friday's overwrite can't happen again.

[300]

Main now holds reviewed changes, but store managers still use last month's model in production. Next lesson: deployment pipelines that promote dev to test to prod, and impact analysis to see who breaks before you ship.

Leaderboard

Loading…

50 XP for each lesson you finish, 10 for each right answer. Names show only for learners who turn on Show me on leaderboards.

Sources for this lesson (13)

Each fact in the lesson is marked with the number of the page it comes from.

  1. [6]Microsoft Learn: Study guide for Exam DP-600: Implementing Analytics Solutions Using Microsoft Fabric
  2. [293]Microsoft Learn: What is Microsoft Fabric Git integration?
  3. [294]Microsoft Learn: Basic concepts in Git integration
  4. [295]Microsoft Learn: Get started with Git integration
  5. [296]Microsoft Learn: Conflict resolution
  6. [297]Microsoft Learn: Branched workspaces
  7. [298]Microsoft Learn: Lifecycle management tutorial
  8. [299]Microsoft Learn: Git integration source code format
  9. [300]Microsoft Learn: Power BI Desktop projects
  10. [301]Microsoft Learn: Power BI Desktop project semantic model folder
  11. [302]Microsoft Learn: Power BI Desktop project report folder
  12. [303]Microsoft Learn: Edit PBIP files outside Power BI Desktop
  13. [304]Microsoft Learn: Tabular Model Definition Language (TMDL)