Within this post I share my initial thoughts about some of the CI/CD announcements at FabCon. I decided to cover a few since there were so many fantastic announcements during the event.
In addition, I decided to focus on the Fabric related announcements even though the SQL-based SQLCon took place at the same time.
For a more comprehensive list of what is new in Microsoft Fabric this month check out the Fabric March 2026 Feature Summary.
CI/CD announcements at FabCon
First CI/CD announcement that caught my attention is the branched workspace with Git integration capability.
Which will allow developers to branch out to new feature workspaces in a more secure manner based on Git integration settings. Without the need of elevated permissions within your tenant.
Plus, it will show the relationships between existing branches better. This feature has yet to appear at this time of writing. However, I have seen the demos and like others I am keen to get it in-place.
Side-by-side with that announcement was the announcement about the selective branching with Git integration. Which allows you to choose which items will appear in a branched-out workspace.
This feature appears to be already available. As you can see below.
Another new Git integration feature that caused a lot of excitement was the ability to compare code changes with Git integration. Which allows you to compare the changes to the workspace with what is stored in the Git branch.
This has been in huge demand as of late and as you can see below is already available.
Personally, I like this new feature as it makes it easier to see what changes were made before they ae committed.
Fabric-CLI announcements
Another feature is the new fab deploy command that is available as part of the Fabric Command Line Interface (CLI). Which allows you to deploy items with the fabric-cicd Python library through a Fabric CLI command.
Initial tests have proved to be interesting, as it requires you to work with configuration-based deployments. In other words, you need to work with a config file. However, I was able to showcase it working in a YAML pipeline in Azure DevOps during SQL Saturday Atlanta. Which took place right after FabCon.
Initial tests seem fine and can be a viable option if you wish to remain in the Fabric CLI ecosystem. However, to make the most of it you will still require basic fabric-cicd skills. Like I covered in my first fabric-cicd deployments steps post.
Final feature I want to mention is the new Fabric CLI AI Agents which are now available. Which will allow you to generate Fabric CLI commands with natural language better. Which I also showed at SQL Saturday Atlanta, along with a custom set of instructions that I created.
AI is significantly changing how development is performed in a lot of areas, and CI/CD is no exception. So this is a welcomed feature.
Final words
I wanted to share my thoughts about some of the CI/CD announcements at FabCon to raise awareness of these new possibilities.
In reality, these announcements were the tip of the iceberg. Because there were so many announcements. My aim in this post was to highlight that the CI/CD story appears to be developing. AI seems to be becoming more involved in this area as well now. So, we will have to see where this will lead.