CI/CD & Git
Treat Fabric workspaces as deployable artifacts — Git-backed, promoted through environments, parameterized per stage.
The goal: no human clicks "publish" in a production workspace. Changes land in Git, CI validates them, and a pipeline promotes them dev → test → prod with stage-specific parameters injected automatically.
Pages
Git integration
Workspace ↔ repo binding, folder layout, what is and isn't serializable.
Deployment pipelines
Stages, deployment rules, item bindings, and gating promotion.
Variable libraries
Per-stage values without deployment rules — connections, paths, capacities.
GitHub Actions for Fabric
fabric-cli in CI: validate on PR, deploy on merge, with a service principal.
Reference topology
Lakehouse.Lakehouse
Ingest.Notebook
Transform.Notebook
Orchestrate.DataPipeline
Analytics.SemanticModel
parameter.yml
- dev workspace is Git-connected. Engineers work in feature branches.
- test and prod receive changes only via the deployment pipeline.
parameter.ymlholds deployment rules; connection-level values move to variable libraries.
Stay ahead of Fabric changes
Fabric runtime changes, API updates, and deprecations. No spam, unsubscribe anytime.