World of Azure Cloud

Fabric Jumpstart: Deploying and Extending the Fabric Platform Monitoring – Capacity Events Real-Time Intelligence Solution

Rene Fürstenberg — Sat, 27 Jun 2026 08:35:53 +0000

Introduction

In this article, I write about Fabric Jumpstart, a website where you can find demos and tutorials to get started with Fabric. However, you can also find solutions there that are perfectly suitable for use in production environments. In this article, I will show you how to use Fabric Jumpstart and deploy solutions in a workspace.

In my example, I will deploy a Real-Time Intelligence workload, focusing on Capacity Events. We can use this solution to monitor the utilization of one or more capacities. This is extremely helpful. We can also extend the solution to receive notifications using Fabric Activator. I will describe this in more detail later in the article.

The solution does the following:
Monitor your Fabric capacity usage in real time using Capacity Events. Telemetry data is streamed into an Eventhouse via Eventstream and analyzed through live KQL dashboards. This helps you identify usage trends early and manage your resources proactively.

How to Save Costs in Microsoft Fabric by Automating Capacity Start & Stop with Azure Logic Apps

Rene Fürstenberg — Sat, 16 May 2026 07:15:55 +0000

Introduction

I get asked quite often how to save costs efficiently in Microsoft Fabric. One of the biggest levers is pausing your Fabric capacity when it’s not in use.

What’s important to understand here: storage costs continue, even when the capacity is stopped. You’re only saving on compute. That’s still a huge win, especially if your workloads are not running 24/7.

In this article, I’ll walk through what this can look like in practice and how you can set up a proper solution to stop and start your capacity.

Let’s quickly look at the available options:

Manually start and stop the capacity
Automatically start and stop using a Logic App
Automatically start and stop using Azure Automation
With Semantic Link Labs

Technically, all of these work. But let’s be honest, manually starting and stopping your capacity every day isn’t something anyone wants to deal with in the long run.

That’s why automation is the only approach that really makes sense.

In my case, I decided to go with Azure Logic Apps, and I’ll show you how to set this up step by step. It’s lightweight, reliable, and easy to maintain, exactly what you want for something that should just run in the background without any manual effort.

Let’s get into it.

Materialized Lake Views in Microsoft Fabric

Rene Fürstenberg — Thu, 16 Apr 2026 15:24:05 +0000

Introduction

In this article, i want to focus specifically on Materialized Lake Views (MLVs in order to better understand how they work and where they can be applied.

MLVs are still relatively new in Microsoft Fabric and, at first glance, do not fully align with what Microsoft has strongly promoted so far, namely a strict separation of the individual layers. Nevertheless, they represent a very interesting alternative, especially when it comes to reducing complex ETL processes.

In my projects, I generally follow the Medallion architecture, where I use a separate Lakehouse for each of the Bronze, Silver, and Gold layers. Alternatively, the Gold layer can also be implemented as a Fabric Warehouse.

This is exactly where Materialized Lake Views come into play, as they enable a different approach:

Instead of operating multiple Lakehouses for the individual layers, Bronze, Silver, and Gold can be represented via separate schemas within a single Lakehouse. The individual layers are logically separated while being technically created within the same Lakehouse.