Real-Time Intelligence with Microsoft Fabric

Chapter 12. Automation

At first, you just set things up by hand: a dashboard here, an eventstream there, maybe a KQL query that does the job. No big deal. Honestly, that’s how most people start. It’s quick, it works, and you don’t think twice.

But then, the project grows. Suddenly, you’ve got more data and more teams asking for the same thing, and you realize you’re clicking through the same setup again. And again. And again. It feels clumsy and, let’s be honest, a little painful.

That’s when automation stops being a “nice-to-have” and becomes the only way to keep up with maintaining complicated and huge environments. Automation is not a single feature in Microsoft Fabric; it is a set of capabilities that span provisioning and configuration, lifecycle management (versioning, promotion, and rollback), operational changes, and “run” activities. This means that automation in Microsoft Fabric is less about “doing everything with code” and more about choosing the right control surface for the job.

In Fabric, there are really two main approaches. Developers usually grab the REST API. It’s clean, programmatic, and easy to plug into other systems. Admins and data folks? They almost always prefer Shell. It’s scriptable, it’s practical, and it just works across environments. This is where Fabric CLI comes into play.

In this chapter, we will cover the most commonly used automation interfaces and show you how these layers combine into a practical operating model.

Why Automate?

At the end ...