DevOps & Observability
From Notebook to Production: Git and CI/CD in Microsoft Fabric
How a Fabric notebook or pipeline gets from a developer's workspace to production safely: Git integration, dev/test/prod workspaces, deployments, environment configuration and release practices.
- Status
- Proposed
- Type
- Talk
- Formats
- Workshop · Webinar · Internal session
- Level
- Intermediate
- Duration
- 45–60 minutes (talk) · half day (workshop)
This is a proposed session topic. No public event is currently scheduled.
Who it is for
- Data engineers who build in Fabric and deploy by hand today
- Platform and DevOps engineers supporting Fabric teams
What attendees will learn
- How Git integration works in Fabric, and what it does and does not track
- How to structure dev, test and production workspaces
- How to keep environment differences in configuration instead of code
- What can be deployed automatically today, and what still needs manual steps
- A release practice that a small team can actually follow
On this page
Session overview
Many Fabric teams start with notebooks edited directly in one workspace. That works until the first change breaks a production report. This session follows a single notebook and pipeline from a feature branch to production. It shows the minimum process that makes change safe without slowing a small team down.
- Feature branchChange in a dev workspace
- Pull requestReview and checks
- TestDeployed with test data
- ProductionApproved release
Outline
- Why “edit in production” fails, and what it costs to recover.
- Git integration: connecting a workspace, what is serialised, and branching.
- Workspaces per environment: naming, permissions and capacity.
- Configuration, not code: parameters, connections and environment-specific values.
- Deploying: deployment pipelines and automation APIs, plus what still needs manual steps.
- A release practice: reviews, versioning, rollback and communication.
Adapting the session
- Workshop: attendees connect a workspace to Git, make a change on a branch, and promote it through test to a production workspace.
Related articles
DevOps & ObservabilityIntermediate
Microsoft Fabric CI/CD with fabric-cicd: From Git to DEV, QA and PROD
A production guide to deploying Microsoft Fabric items from Git with Microsoft’s fabric-cicd library, covering repo layout, authentication, parameterization, CI and CD.
DevOps & ObservabilityBeginner
Connect Microsoft Fabric to Git
Connect a Microsoft Fabric workspace to a GitHub or Azure DevOps repository step by step, and understand branches, folders, commits, updates, conflicts and what belongs in source control.
DevOps & ObservabilityIntermediate
Deploy a Fabric Solution with Git, Deployment Pipelines and Database Projects
A hands-on Microsoft Fabric lifecycle lab: version a workspace with Git integration, promote it from Dev to Test with a deployment pipeline and deployment rules, change a Warehouse schema as a database project, cause two controlled deployment failures and plan rollback.
DevOps & ObservabilityIntermediate
Git Integration in Microsoft Fabric: A Practical Development Workflow
How Fabric Git integration really works day to day: workspace and branch, commit and update, branching out, pull requests, conflicts, drift and permissions.