Press "Enter" to skip to content

Category: Microsoft Fabric

Fabric Tenant Settings to Check at Launch

Paul Turley continues a series on Microsoft Fabric:

Article 3 covered the headline settings almost every tenant touches first, but the full tenant settings screen runs past 30 categories, from information protection to advanced networking. You won’t master all of it on day one, but knowing what’s there keeps you from being caught flat-footed later. Skim the full list once, even if you’re not ready to configure most of it, just so nothing surprises you when a business unit asks for a capability you didn’t know existed.

Click through for six tips.

Comments closed

A First Look at Microsoft Fabric On-Demand Capacity

Reitse Eskens gives it a try:

You can compare it to Serverless SQL databases: when it’s not in use, it won’t cost anything. Storage will always incur some cost, but no compute.
First, be aware that there are no reservations (reserve plans soon) available. Second, pricing to use items will differ from the regular capacities. Some items may have the same price; others will be calculated at x2 or x3. We have to wait for the official documentation to find out what the actual prices will be.

Right now, we don’t know what the cost will look like, though once the documentation is available, we should have a better idea. Assuming it’s not in some inscrutable units.

Comments closed

Flat File Ingestion Options with Microsoft Fabric

Andy Brownsword loads some data:

For this example I’ll use NHS monthly prescribing data which provides us with a large CSV, and we’ll copy it into a Lakehouse. For the Bronze layer we want to retain data as close to source as possible, so simply retrieving the file and retaining the CSV is the goal.

I’ll compare the options for this specific use case, with multiple runs for each. So, let’s see how the options stack up.

Click through to see how long each of the four options takes and what Andy recommends.

Comments closed

Ten Decisions to Make Prior to Creating a Fabric Workspace

Meagan Longoria has a list:

Creating a Fabric workspace takes about 30 seconds. Restructuring workspaces after people have built content in them takes a lot longer. Moving content to another workspace usually means redeploying or recreating it, and anything bound to the old item IDs has to be rebound: reports connected to a semantic model, a notebook’s default lakehouse, pipeline activities, and shortcuts. Item-level shares, app content, and links people saved don’t carry over either.

Most of that rework is avoidable if you make a handful of design decisions before anyone starts building. None of these decisions has a single right answer. The right choice depends on your organization’s size, skills, security requirements, and how much self-service you want to support. But I’d much rather see them made deliberately, before the first workspace exists, than left at the defaults and discovered later. For each decision, I’ll cover the options, what should drive the choice, and the platform constraints that narrow it down.

Read on for that list.

Comments closed

Extracting Lineage Information from Microsoft Fabric Spark Notebooks

Gerhard Brueckl retrieves some information:

When building data platforms and data pipelines to populate them, one of the most challenging parts is orchestration. You need to figure out dependencies between your pipelines and activities, know the run times/duration and make sure to run them only when all upstream pipelines succeeded. From a technical point of view, this can be easily accomplished within Microsoft Fabric using runMultiple(). (I really dont know why Databricks doesn’t offer something similar out of the box?!?)

Now the next question that comes up is: “Where do I get those dependencies from?” – and this is exactly what this blog post is about!

Click through to learn how.

Comments closed

Users, Licenses, and Guest Access in Microsoft Fabric

Paul Turley manages a tenant:

Fabric doesn’t have its own separate licensing screen — you assign every license, Fabric included, from the Microsoft 365 admin center, the same place you’d manage Exchange or Teams. Easy to miss if you came into this world through the Fabric admin portal. Save yourself a search: bookmark the Microsoft 365 admin center alongside the Fabric admin portal, since you’ll need both within your first week.

Click through for some more tips and tricks around user management in Microsoft Fabric.

Comments closed

Clustering in Fabric Data Warehouse

Louis Davidson does some exploring:

Clustering is one of the data terms that could not have been created by a database design person. Why? Because it has multiple meanings. In PostgreSQL it means the same thing as an instance in SQL Server. In server architecture it means connecting multiple servers together to form a “single” unit of some form to protect against failure. Then it means an index that determines the physical storage of a table in some manner. This usage of the word means the former.

The weirdest part of using a Fabric Data Warehouse when you first try to look at a query is the lack of indexes. So (currently as of writing this is late 2026), you only have this one tool to affect your performance. The tool allows you to order the data physically in your files so query processing can be reduced when searching the physical file.

Read on for an introduction of how it works, with the caveat that Louis is about two pages ahead of most people in the book.

Comments closed

Tracking Microsoft Fabric Capacity Operation Events

Gilbert Quevauvilliers stores some data:

This blog post will explain how to capture the data from real-time events for Fabric Operation Events and store the results in a Lakehouse.

My approach is to use a Python notebook to query Eventhouse.

The reason for this is the Python notebook runs very quickly and because it consumes very little Capacity Units, it is a very efficient way to store the Fabric Operational Events to be analyzed over a long period of time.

Read on for the instructions and the notebook that Gilbert used.

Comments closed

An Explanation of Fabric Licensing

Paul Turley digs in:

When the Power BI cloud service morphed into the Fabric platform a few years ago, Microsoft introduced very attractive cost and capacity options for small organizations, teams and projects – and its easy to scale-up. This is why Fabric works for both small and huge workloads.

Fabric licensing might look intimidating from the outside, mostly because Microsoft describes it in acronyms. Strip those away and it really boils down to two questions.

Click through for those questions and what it all means.

Comments closed

Creating Alerts in Microsoft Fabric

Koen Verbeeck turns on the Bat-signal:

We are building a new data platform with Microsoft Fabric and we’re using the warehouse for our “gold layer”. We don’t have real-time ingestion or analytic requirements, but we have a use case where we want to send an alert if a certain threshold is reached. Ideally, the alert is sent when a SQL query returns a result set.

Click through to see how that’s possible, as well as what kinds of rules, triggers, and conditions you can set.

Comments closed