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…
