Home > Docs > Features > Git Integration

🔀 Git Integration for Fabric¶

Last Updated: 2026-04-21 | Version: 1.0.0

📑 Table of Contents¶

• 🎯 Overview
• 🏗️ Architecture
• ⚙️ Configuration
• 🔄 Sync Workflows
• 👥 Multi-Developer Patterns
• 🎰 Casino Implementation
• 🏛️ Federal Implementation
• ⚠️ Limitations
• 📚 References

🎯 Overview¶

Fabric Git Integration connects a workspace to a Git repository (Azure DevOps or GitHub), enabling source control for Fabric items. Changes made in the Fabric portal are committed to Git, and changes pushed to Git are synced back to the workspace. This provides version history, branching, pull requests, and code review for notebooks, pipelines, semantic models, and other Fabric items.

Key Capabilities¶

Git Integration vs. Deployment Pipelines vs. fabric-cicd¶

🏗️ Architecture¶

Sync Architecture¶

flowchart LR
    subgraph Fabric["☁️ Fabric Portal"]
        WS["Workspace<br/>casino-fabric-dev"]
        NB["Notebooks"]
        PL["Pipelines"]
        SM["Semantic Models"]
    end

    subgraph Git["📦 Git Repository"]
        MAIN["main branch"]
        DEV["dev branch"]
        FEAT["feature/* branches"]
    end

    WS <-->|"Commit / Sync"| DEV
    DEV -->|"Pull Request"| MAIN
    FEAT -->|"Pull Request"| DEV

    style WS fill:#2E86C1,stroke:#1B4F72,color:#fff
    style MAIN fill:#E74C3C,stroke:#C0392B,color:#fff
    style DEV fill:#27AE60,stroke:#1E8449,color:#fff

Repository Structure¶

When Git Integration is enabled, Fabric items are serialized into the repo:

casino-fabric/
├── casino-fabric-dev.Workspace/
│   ├── 01_bronze_slot_telemetry.Notebook/
│   │   ├── notebook-content.py
│   │   └── .platform
│   ├── 01_silver_slot_cleansed.Notebook/
│   │   ├── notebook-content.py
│   │   └── .platform
│   ├── daily_revenue_pipeline.DataPipeline/
│   │   ├── pipeline-content.json
│   │   └── .platform
│   ├── slot_analytics.SemanticModel/
│   │   ├── definition/
│   │   │   ├── model.bim
│   │   │   └── diagramLayout.json
│   │   └── .platform
│   ├── lh_bronze.Lakehouse/
│   │   └── .platform
│   └── env-casino-analytics.Environment/
│       ├── Setting/
│       │   └── Sparkcompute.yml
│       ├── PublicLibraries/
│       │   └── requirements.yml
│       └── .platform

The .platform File¶

Every Fabric item includes a .platform metadata file:

{
    "$schema": "https://developer.microsoft.com/json-schemas/fabric/gitIntegration/platformProperties/2.0.0/schema.json",
    "metadata": {
        "type": "Notebook",
        "displayName": "01_bronze_slot_telemetry"
    },
    "config": {
        "version": "2.0",
        "logicalId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
    }
}

⚙️ Configuration¶

Connecting a Workspace to Git¶

1. Open the workspace → Workspace settings → Git integration
2. Select provider: Azure DevOps or GitHub
3. Authenticate and select:
4. Organization / Account
5. Repository
6. Branch (typically dev or main)
7. Folder (root or subfolder)
8. Click Connect and sync

Azure DevOps Setup¶

Workspace Settings → Git Integration
  Provider: Azure DevOps
  Organization: contoso-gaming
  Project: casino-analytics
  Repository: fabric-items
  Branch: dev
  Git folder: /casino-fabric-dev

GitHub Setup¶

Workspace Settings → Git Integration
  Provider: GitHub
  Account: contoso-gaming
  Repository: fabric-items
  Branch: dev
  Git folder: /casino-fabric-dev

💡 Tip: Use a dedicated branch per workspace. Map dev branch to the Dev workspace, and use PRs to promote to main (which maps to the Prod workspace or deploys via fabric-cicd).

Branch Policies (Recommended)¶

Configure in Azure DevOps or GitHub:

🔄 Sync Workflows¶

Commit from Workspace to Git¶

When you modify items in the Fabric portal:

1. Source Control panel shows uncommitted changes
2. Review changed items (diff view)
3. Enter commit message
4. Click Commit

Source Control Panel:
  Modified items:
    ✅ 01_bronze_slot_telemetry.Notebook    (2 cells modified)
    ✅ daily_revenue_pipeline.DataPipeline  (new activity added)
    ☐  slot_analytics.SemanticModel         (no changes)

  Commit message: "feat: add compliance filter to bronze ingestion"
  [Commit]

Sync from Git to Workspace¶

When changes are pushed to the connected branch:

1. Source Control panel shows incoming changes
2. Review what will be updated
3. Click Update All

Conflict Resolution¶

When both workspace and Git have changes to the same item:

Conflict detected:
  01_bronze_slot_telemetry.Notebook
    Workspace version: Modified cell 3 (add filter)
    Git version: Modified cell 5 (add column)

  Options:
    [Accept workspace version]
    [Accept Git version]
    [Keep both changes (manual merge)]

⚠️ Fabric conflict resolution is item-level, not line-level. For complex merges, resolve in your Git client (VS Code, etc.) and then sync.

👥 Multi-Developer Patterns¶

Pattern 1: Branch-Per-Workspace¶

flowchart TB
    subgraph Workspaces
        DEV1["Dev-Alice<br/>workspace"]
        DEV2["Dev-Bob<br/>workspace"]
        TEST["Test workspace"]
        PROD["Prod workspace"]
    end

    subgraph Git
        FA["feature/alice"]
        FB["feature/bob"]
        DEVB["dev branch"]
        MAINB["main branch"]
    end

    DEV1 <--> FA
    DEV2 <--> FB
    FA -->|PR| DEVB
    FB -->|PR| DEVB
    DEVB <--> TEST
    DEVB -->|PR| MAINB
    MAINB <--> PROD

    style MAINB fill:#E74C3C,stroke:#C0392B,color:#fff
    style DEVB fill:#27AE60,stroke:#1E8449,color:#fff

How it works: 1. Each developer has their own workspace connected to a feature branch 2. Developer commits changes from workspace to their branch 3. Developer opens a PR from feature branch → dev 4. After review and merge, Test workspace syncs from dev 5. After QA, PR from dev → main, Prod workspace syncs

Pattern 2: Shared Dev Workspace¶

Shared workspace: casino-fabric-dev
  Connected to: dev branch

  Developer workflow:
  1. Work in shared workspace
  2. Commit changes to dev branch
  3. Create PR from dev → main for production

Simpler but riskier — changes are immediate in the shared workspace. Best for small teams (2-3 developers).

🎰 Casino Implementation¶

Repository Structure¶

casino-fabric/
├── casino-fabric-dev.Workspace/
│   ├── Bronze Notebooks (17)/
│   ├── Silver Notebooks (16)/
│   ├── Gold Notebooks (18)/
│   ├── Pipelines (4)/
│   ├── Semantic Models (2)/
│   ├── Reports (5)/
│   ├── Lakehouses (3)/
│   └── Environments (1)/
├── .github/
│   └── workflows/
│       └── deploy-fabric.yml
├── validation/
│   └── unit_tests/
└── README.md

Branching Strategy¶

🏛️ Federal Implementation¶

Compliance Considerations¶

Multi-Agency Repository Options¶

⚠️ Limitations¶

📚 References¶

🔗 Related Documents¶

• Deployment Pipelines — Stage-based promotion
• Fabric CI/CD Deployment — Programmatic deployment with fabric-cicd
• Identity & RBAC Patterns — Access control
• Architecture — System architecture

📝 Document Metadata - Author: Documentation Team - Reviewers: Platform Engineering, DevOps - Classification: Internal - Next Review: 2026-07-21