Status check, verified October 2026. The Fabric Core MCP Server is generally available since the September 2026 Fabric update, but the pieces around it move fast. The Fabric skills are open source and get new versions often, the Fabric CLI ships regularly, and the VS Code extension changes its UI from time to time. If…
Status check, verified October 2026. The Fabric Core MCP Server is out of preview: Microsoft listed it as generally available in the September 2026 Fabric update. The tool set is still growing, though. At the time of writing it has no tools for capacity assignment, Git or Spark settings, which is why fab and az…
Preview notice, verified August 2026. The Fabric Core MCP Server is in public preview. Endpoints, tool names and configuration can change before GA, so if a command here doesn’t behave the way I describe, check the Microsoft Learn docs before assuming your setup is broken. I date-stamp every post in this series and update them…
If you’ve been building shared code for your team in Fabric, you already know the easy part is writing the library. The hard part shows up later: keeping that same library consistent across a dozen workspaces without turning every release into a manual chore. I’ve covered how to work as a team in an enterprise…
When you’ve got more than one data engineer building things in Microsoft Fabric, you’ve probably hit the same little annoyance I did: everyone is quietly rewriting the same helper functions. Same string concat. Same date parser. Same five-line utility nobody can find when they actually need it. There are a few ways to tackle this…
If you’re working with Microsoft Fabric and running complex workloads – multiple notebooks executing at the same time, or needing Python libraries that aren’t built-in – you’ve probably asked yourself: “How do I manage this properly?” The answer is Fabric Environments. In this post, I’ll walk you through what they are, how to configure them,…
In my previous post, I walked through setting up development environments in Microsoft Fabric, connecting them to Git, and shared some best practices for collaboration and continuous development. If you haven’t read that yet, I’d recommend starting there—this post builds on those concepts and refers back to them in several places. Here, we’ll tackle the…
If you’ve ever worked on building or releasing data solutions, you’ve probably run into the usual suspects: long release cycles, last-minute bugs, and the classic “it works on my machine” problem. Writing clean code is only half the job—getting it into production reliably and quickly is where things tend to break down. That’s where CI/CD…
Microsoft Fabric monitoring is essential when you’re running production pipelines – you need to know when something breaks before your users do. In my previous post, I walked through how to connect and ingest logs using a notebook. Now let’s take it a step further – automating the entire process with built-in alerting. By automation,…
Introduction If you’ve been working with Microsoft Fabric in production environments, you’ve probably faced this critical question: “How can we monitor our pipelines, notebooks, and processes with automated notifications when something goes wrong?” Here’s the thing—as of now, there’s no built-in functionality in Microsoft Fabric that fully addresses this need. The recently announced Workspace Monitoring…
