Announcing official support for Microsoft fabric-cicd tool

[yaronprigal]

Today, we’re announcing that fabric‑cicd—the open‑source Python deployment library for Microsoft Fabric—is now an officially supported, Microsoft‑backed tool for CI/CD automation across Fabric workspaces.

Over the past year, fabric‑cicd has rapidly evolved through collaboration with engineering, CAT, MVPs, enterprise customers, and the community. Growing usage, strong sentiment across internal and external channels, and adoption by organizations building enterprise‑grade deployment pipelines helped solidify its value within the Fabric ecosystem.

With this announcement, we’re affirming long-term support, quality, roadmap ownership, and deep integration with the broader Fabric platform—including Git Integration, Fabric REST APIs, the CLI, and future deployment capabilities.

Internal discussions and customer conversations consistently reinforced the value of a reliable cross‑workspace deployment mechanism, particularly in environments where Git Integration and Variable Library don’t fully address all needs, or where deployment pipelines alone don't support every deployment scenario.

fabric‑cicd is now a fully recognized part of the Fabric CI/CD story.

Fabric CI/CD tool objectives

In modern application development, robust DevOps capabilities are essential for delivering reliable, scalable solutions. Customers and partners surfaced challenges around Fabric cross‑workspace deployments, especially in two key areas:

• Dependencies between Fabric items, which today require manual orchestration and often cause deployment ordering or binding issues.
• Lack of parametrization across many Fabric item types, limiting the ability to promote the same artifacts across environments (Dev → Test → Prod) in a clean, repeatable way.

The fabric‑cicd tool directly addresses these gaps: providing a unified, automated deployment engine that handles dependencies, enables parametrization, and reduces the friction of managing multi‑environment workflows. It can also serve as a core component in implementing Git based deployment using build environment option, offering a more customizable and automation‑friendly alternative to built‑in deployment pipelines or pure Git‑based flows., offering a more customizable and automation‑friendly alternative to built‑in deployment pipelines or pure Git‑based flows.

Git-based deployment using build environment

In this cross‑workspace deployment approach, all deployments originate from the same main branch of your Git repository. Each stage in the release flow (Dev → Test → Prod) has its own Build and Release pipeline, providing full control over validations, approvals, and environment‑specific configuration.

In this model, pipelines typically use a Build environment to execute unit tests, validate item integrity, and then invoke the fabric‑cicd tool to deploy item definitions into the target workspace. During deployment, the pipeline passes a parameterization file that adjusts environment‑specific settings before items are uploaded.

This enables teams to reliably customize configuration per stage, for example:

• Updating data source connections
• Adjusting relationships or bindings between items
• Injecting environment‑specific parameters
• Applying configuration transformations required for Test or Production

Build_Release_pipeline_flow_using_fabric-cicd_tool

Figure 1 - Suggested build and release pipelines using fabric-cicd tool

This approach is particularly powerful for teams that need flexible parameterization, dependency management, or granular control over specific items—capabilities readily available within the fabric‑cicd toolbox.

Find out more in our ci-cd tool documentation and ci-cd tool deployment examples.