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 & Observability
Monitoring Microsoft Fabric Pipelines and Notebooks
Separate Fabric orchestration, session startup, Spark compute, data read, shuffle and write time with connected telemetry.
Microsoft Fabric
Using Session Tags in Fabric Pipelines
Use Microsoft Fabric pipeline session tags to group compatible notebook activities for Spark session reuse while preserving workload boundaries.
DevOps & Observability
Designing an Execution Log for Data Pipelines
Design a durable pipeline execution log with run identity, parent-child relationships, transitions, retries and correlation.
Microsoft Fabric
How to Make Microsoft Fabric Notebooks Faster
A practical workflow for reducing Fabric notebook startup, read, shuffle, transformation and Delta write time without guessing.