Launch Deal · 50% off 1st month ·

1.2 — Configure Version Control with Git Integration

DP-700 Domain 1 · Skill 1.2

What You Need to Know

Fabric Git integration works at workspace level. You connect one workspace to one branch and one folder of a repository. Every supported item in the workspace is then saved to Git as source files, and the workspace's folder structure is kept.

Supported providers and prerequisites

Requirement Detail
Git providers Azure DevOps (cloud only), GitHub and GitHub Enterprise (cloud only)
Capacity The workspace must be on a Fabric capacity (or a Power BI Premium capacity, for Power BI items only)
Tenant settings Users can synchronize workspace items with their Git repositories must be on. GitHub also needs Users can sync workspace items with GitHub repositories
Azure DevOps details Organization, project, repository, branch and an optional folder
GitHub authentication A personal access token. A fine-grained token needs Contents: Read and write to commit. A classic token needs the repo scope

Who can do what

Action Workspace role Git permission
Connect, sync or disconnect the workspace Admin only Read
Commit workspace changes to Git Contributor or higher (write on all items) Read + Contribute (Azure DevOps); Contents read and write (GitHub). Branch policies must allow direct commits
Update the workspace from Git Contributor or higher Read
Switch or create branches Admin. Contributors and Members can too if the workspace setting Allow users with at least Contributor role to change Git branch is on Create branch
Branch out to another workspace Admin, Member, Contributor Read + create branch
Any Git action Viewers can't see or use Git features

The day-to-day flow

  1. Saved edits stay in the workspace until you commit them in the Source control panel.
  2. When someone else commits to the branch, the workspace shows Updates. Update all pulls the changes into the live items.
  3. On the first sync, if one side is empty, its content is copied from the other side. If both sides have content, you choose the direction. Updating the workspace from Git overwrites the workspace, and that can't be undone.
  4. Unsupported items can stay in the workspace. They're ignored, not deleted.

What is stored

  • Git holds item definitions only (metadata, code, notebook source, pipeline JSON). Data never goes to Git.
  • Items that support Git include lakehouses, notebooks, Spark job definitions, environments, pipelines, Dataflow Gen2, copy jobs, warehouses, SQL databases, eventhouses, eventstreams, KQL databases and querysets, Activator, semantic models and reports.
  • For a lakehouse, Git stores the item itself, not its tables or files.

Branching patterns

  • Feature workspaces: each developer branches out to a private workspace connected to a feature branch, then merges through a pull request.
  • Release flow: after the merge, either connect the next environment to the main branch, or deploy with a deployment pipeline (lesson 1.3).

Key Concept: Version control (Git) keeps the history of item definitions. Deployment (deployment pipelines or build pipelines) moves those definitions between environments. The exam often offers one where the other is needed.

Exam Traps

  • Expecting Git to version the data in a lakehouse or warehouse
  • Asking a Contributor to connect the workspace to a repository (Admin only)
  • Granting GitHub Actions or Workflows permissions for committing (only Contents: Read and write is needed)
  • Using an on-premises Azure DevOps Server or GitHub Enterprise Server (only cloud-hosted providers are supported)
  • Updating a workspace from Git without realizing it overwrites uncommitted workspace changes

Check your understanding

Practice Scenario

Priya has the Member role in the workspace Sales-Dev and write access to an Azure Repos repository. She wants to connect Sales-Dev to the repository so that the team, all Contributors, can commit their notebooks. The Git integration settings won't let her connect the workspace. What is the cause?

Report issue

Log in to save your progress.