Connecting a workspace to a Git repository

Microsoft Fabric supports Git integration so workspaces can be connected to a Git repository (Azure DevOps or GitHub) for version control of supported items. Once connected, changes made in the Fabric workspace can be committed to the repo, and changes in the repo can be synced back into the workspace, enabling collaboration, history tracking, and branching workflows. This integration is configured per workspace via Workspace settings > Git integration.

1 · Learn the must-know

• 1Git integration is configured at the workspace level under Workspace settings, where you connect to either Azure DevOps or GitHub, specify the organization/repo, branch, and folder path.
• 2Each Fabric item is serialized into source control as a folder containing platform-specific definition files (e.g., .platform, .pbir, .json), not as a single binary export.
• 3Not all Fabric item types support Git integration; unsupported item types will not sync and must be managed manually until support is added.
• 4Users need appropriate permissions both in Fabric (workspace Admin/Member role, depending on action) and in the Git provider (repo read/write access) to connect and sync a workspace.
• 5The workspace shows sync status (Git diff) indicating uncommitted changes, and you must explicitly commit workspace changes to the repo or update the workspace from the repo: sync is not fully automatic.
• 6Branching out to a new workspace lets teams create isolated dev/test branches connected to separate Git branches, supporting a branch-per-environment or feature-branch workflow before merging back.

2 · Check your understanding