Black Friday50% off your first month on any monthly plan with EARLY50 See plans
All 33 lessons
  1. Start here: cloud and data 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. The three languages: SQL, PySpark and KQL side by side
    6. 6. Getting data in: the map of Fabric tools
  2. Store, ingest and transform batch data (exam area 2, 30-35%)

    1. 7. Choosing a data store and a transformation tool
    2. 8. Shortcuts and mirroring: use data without copying it
    3. 9. Ingest data with pipelines and Copy job
    4. 10. Transform with PySpark and SQL: join, denormalize, aggregate
    5. 11. Messy data: duplicates, missing values and late arrivals
    6. 12. Full and incremental loads, and loading a star schema
  3. Orchestrate and stream (exam areas 1 and 2)

    1. 13. Pipeline or notebook? Choosing how to orchestrate
    2. 14. Schedules and event-based triggers
    3. 15. Parameters and dynamic expressions
    4. 16. Streaming in Fabric: Eventstreams, Spark streaming and KQL
    5. 17. KQL and windowing functions for real-time data
  4. Set up and secure a Fabric solution (exam area 1, 30-35%)

    1. 18. Workspace settings: Spark, domains, OneLake and data workflows
    2. 19. Version control with Git and database projects
    3. 20. Deployment pipelines: development, test and production
    4. 21. Who can see what: workspace roles and item permissions
    5. 22. Fine-grained security: rows, columns, objects, files and masking
    6. 23. Governance: sensitivity labels and endorsement
  5. Monitor, fix and optimize (exam area 3, 30-35%)

    1. 24. Monitoring hub, alerts and Activator
    2. 25. Fixing errors in pipelines, dataflows and notebooks
    3. 26. Fixing errors in Eventhouse, Eventstream and T-SQL
    4. 27. Optimize lakehouse tables: V-Order, OPTIMIZE, VACUUM and partitions
    5. 28. Optimize Spark, pipelines and warehouses
    6. 29. Optimize eventstreams, eventhouses and queries
  6. Exam practice and final review

    1. 30. Exam day: question types, timing and how to think
    2. 31. Mock exam 1
    3. 32. Mock exam 2
    4. 33. Final review: every decision on one page
See the leaderboard

20 min

Version control with Git and database projects

Connect a workspace to Git, commit and update items, and use database projects for warehouses.

By the end of this lesson you can

  • Connect a workspace to an Azure DevOps or GitHub branch and folder
  • Tell Commit from Update in the Source control pane, and resolve a conflict
  • Set up feature workspaces with branch out, and name the roles each action needs
  • Explain why a Warehouse schema belongs in a database project

From earlier lessons · 1 of 2

Every notebook in a workspace needs the same library. Where should a workspace admin put it?

Pick one answer.

From earlier lessons · 2 of 2

Who can assign a workspace to a domain from the workspace's own settings?

Pick one answer.

Two Northwind Rides engineers edited the same trip-cleaning notebook last week. One overwrote the other's fix, and nobody noticed for three days. There was no history to compare and no way to roll back. Your manager wants every change tracked, reviewed and reversible, starting with the dev workspace.

[4]

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 a folder, in a repo. Items are saved as files that describe them. The workspace's folder structure is kept, up to 10 levels deep.

Supported providers, cloud versions only:

  • Azure DevOps
  • GitHub
  • GitHub Enterprise

A tenant switch, on by default, must allow it. My workspace can't connect to Git.

[168][169][171]

Exam depth: recognize it.

Most data engineering items are supported, including:

  • Data Engineering: Lakehouse, Notebook, Spark job definition, Environment.
  • Data Factory: Pipeline, Copy job, Dataflow Gen2, Mirrored database.
  • Real-Time Intelligence: Eventhouse, KQL database, KQL queryset, Eventstream, Activator.
  • Warehouse and SQL database. Power BI reports and semantic models are in preview.

Unsupported items are ignored: not saved, not synced and not deleted.

[168][176]

[176]

Connecting and the first sync

Exam depth: know it cold.

Only a workspace Admin can connect a workspace to Git. Once it's connected, 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. With GitHub, set up your own connection instead of sharing a personal access token, a password-like key.

[169]

Try it in Fabric

You need the Admin role on the workspace and an Azure DevOps repo. A trial capacity is enough.

  1. Open the workspace and select Workspace settings.
  2. Select Git integration, then Azure DevOps.
  3. Select Connect. Fabric signs you in with your Microsoft Entra account.
  4. Pick the Organization, Project and Git repository.
  5. Pick the Branch, such as main.
  6. Type a Git folder name. This folder syncs with the workspace.
  7. Select Connect and sync.

The workspace now shows a Git status column and the connected branch.

[170][175]

Workspace settings with Git integration selected. The Connect Git repository and branch 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

[175]

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 to commit.No, it always takes 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, such as Synced, Uncommitted changes, Update required or Conflict.

[169]

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

[169]

You are a data engineer at Northwind Rides. A teammate merged a fixed notebook into main. Your workspace is connected to main and shows 1 item under Updates. You also edited a different pipeline 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, and Commit is disabled. 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. Its status becomes Uncommitted changes, so commit it next.

If you're not sure which version is right, select Checkout new branch. It creates a branch from the last synced commit and keeps your workspace as it is. Commit there, then merge the two branches in Git.

[172]

You are a data engineer at Northwind Rides. The trip-cleaning notebook 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.

[172]

Commit: workspace to Git. Update: Git to workspace. Both at once: pick a side first. Picture: Movie-poster parody in bold retro style.

Feature workspaces and branch out

Exam depth: know it cold.

A common setup has a shared dev workspace connected to main. Each developer works in a feature workspace connected to their own feature branch. Finished work goes back to main through a pull request, a request to merge one branch into another.

Branch out to another workspace, on the Branches tab, sets this up for you. It creates a new branch from the last commit. It then connects a new or existing workspace to that branch. Select items individually brings over only the items you need.

Two look-alikes on the same tab:

  • Switch branch replaces every item in the workspace with the other branch's content.
  • Checkout new branch creates a branch but keeps the workspace content.

[169][173][174]

Put in order

Put the steps of a feature change at Northwind Rides in order

Drag, or focus an item and press Space, move with the arrow keys, then Space to drop.

  1. Branch out from the dev workspace to a new feature branch and workspace
  2. Open a pull request and merge the feature branch into main
  3. Commit the change to the feature branch
  4. Update the dev workspace from Git
  5. Edit the notebook in the feature workspace

[175][177]

Permissions you need

Exam depth: know it cold.

What you can do depends on your workspace role and your rights in the repo.

ActionWorkspace role
Connect, disconnect, sync settingsAdmin.
Switch branchAdmin, or Member/Contributor when a setting allows it.
Commit and UpdateContributor or higher, with write access to the items.
Branch out to another workspaceContributor or higher.
Anything Git relatedNot Viewers; they can't even see Git status.

The setting is Allow users with at least Contributor role to change Git branch. On the Git side, committing needs write access to the repo. Branching out also needs rights to create branches in Git, and to create workspaces in Fabric.

[169][174]

You are a data engineer at Northwind Rides. You need a new workspace connected to Git with the least privilege. One engineer will connect it to the repo. Three others will edit items and commit their changes. Which roles should you assign?

Pick one answer.

[169]

Database projects: Warehouse schema as code

Exam depth: know it cold.

A database project (SQL database project) keeps a database's schema as files. Each table, view or procedure has one .sql file with its CREATE statement. A .sqlproj project file ties them together.

Build checks that every reference is valid; a view that names a missing column fails. The output is a .dacpac file, one package holding the whole schema. Publish then changes the target Warehouse to match the project.

When a workspace is connected to Git, a Warehouse is committed as a database project. You can also build one in Visual Studio Code with the SQL Database Projects extension. Pick Synapse Data Warehouse in Microsoft Fabric as the target and the newer SDK-style project format. Warehouse Git integration is in preview.

Why bother? Schema changes get reviewed in pull requests and checked before they reach the warehouse.

[178][179][181][182]

sql
-- NorthwindDW/
-- sqldw.sqlproj project file
-- dbo/Tables/FactTrip.sql
-- dbo/Tables/DimStation.sql
-- dbo/Views/vTripsByStation.sql
-- dbo/Tables/FactTrip.sql
CREATE TABLE [dbo].[FactTrip]
(
[TripId] BIGINT NOT NULL,
[StationKey] INT NOT NULL,
[StartTime] DATETIME2(6) NOT NULL,
[DurationSec] INT NULL
);
How the Northwind warehouse looks in the repo: one .sql file per object, grouped by schema and object type.

[183]

[178][179]

Exam-style practice

You are a data engineer at Northwind Rides. The company keeps code in a Git server hosted in its own data center. You need to connect a Fabric workspace to Git with the least change to company tools. What should you do?

Pick one answer.

[168][169]

You are a data engineer at Northwind Rides. Warehouse schema changes are made by hand, and last month a dropped column broke a view in production. You need schema changes reviewed and validated before they reach the Warehouse. What should you use?

Pick one answer.

[178][180]

FlashcardsIndex cardsFlashcards ⚡

Card 1 of 14

[168][169][172][173][176][178]

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. Feature workspaces come from branch out; work returns to main by pull request, then Update.
  5. Git holds definitions, not data; a Warehouse is stored as a database project.

Main now holds reviewed, working items. But production still runs last month's notebook, against the production lakehouse, not dev. Next lesson: deployment pipelines that promote content from dev to test to prod.

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 (17)

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

  1. [4]Microsoft Learn: Study Guide for Exam DP-700
  2. [168]Microsoft Learn: What is Microsoft Fabric Git integration?
  3. [169]Microsoft Learn: Basic concepts in Git integration
  4. [170]Microsoft Learn: Get started with Git integration
  5. [171]Microsoft Learn: Git integration tenant settings
  6. [172]Microsoft Learn: Conflict resolution
  7. [173]Microsoft Learn: Development process using branch workspace
  8. [174]Microsoft Learn: Fabric CI/CD concepts and best practices
  9. [175]Microsoft Learn: Tutorial: Application lifecycle management in Fabric
  10. [176]Microsoft Learn: Lakehouse git integration and deployment pipelines
  11. [177]Microsoft Learn: SQL database source control integration in Microsoft Fabric
  12. [178]Microsoft Learn: What are SQL database projects?
  13. [179]Microsoft Learn: Git integration for Fabric warehouse development
  14. [180]Microsoft Learn: How to use Git integration for warehouse development and deployment
  15. [181]Microsoft Learn: Development and deployment overview (Fabric Data Warehouse)
  16. [182]Microsoft Learn: Develop warehouse projects in Visual Studio Code
  17. [183]Microsoft Learn: Warehouse definition