Press "Enter" to skip to content

Category: Microsoft Fabric

Types of Applications in Microsoft Fabric

Valerie Junk disambiguates a term:

When you log in to Power BI online these days, you may notice more than one type of App.  You have the Apps you’ve known for years, Fabric Apps where people can even write data back, and Org apps that can include all kinds of items like reports and even a Fabric App.
Confused? Honestly, so was I, and I’ve been using Power BI for a long time.

In this article, I go through them one by one: where to find each one, what it does, and when to pick each.

Click through for the breakdown of three different classes of application.

Leave a Comment

Using Direct Lake across Public and Private Link Workspaces

Gilbert Quevauvilliers gets all of the data:

Currently in the Microsoft documentation it talks to not being able to connect from a Public Workspace to a Private Link workspace using DirectLake to a Semantic Model.

What this means in my mind is it is where it is a direct connection from a Public Workspace to a Private Link workspace

NOTE: A Private Link workspace is where inbound connectivity is blocked from the public internet.

In this blog post I am going to show you how to work around this, where at the end I will show you how you can still use DirectLake for a Semantic Model between a Public and Private Link Workspace.

Read on for the solution.

Leave a Comment

Testing Fabric Data Agent Accuracy and Determinism

Marc Lelijveld trusts but verifies:

Over the past year, I’ve written quite a bit about Fabric Data Agents. From configuring them and preparing Semantic Models for AI, all the way to deploying Data Agents using the Data Agent SDK. But once you start moving Data Agents beyond experimentation, another question quickly becomes relevant: “How do you actually know whether your Data Agent continues to return the right answer?”

Of course, you can open the Data Agent, enter a prompt and manually validate the response. That works perfectly fine while experimenting with a handful of questions, although it can already become quite time-consuming. Now imagine having to validate 20, 50 or maybe hundreds of questions, and not just once, but every time your data, Semantic Model, Agent Instructions or other parts of the solution change.

There is another aspect to this. With generative AI, we don’t only care about accuracy, but also about determinism. If we ask the same question again, can we rely on the Data Agent to consistently produce the expected outcome? This is where automated testing becomes increasingly important.

Read on to see how you can work toward answers for both.

Leave a Comment

Building a Rayfin App to Replay Soccer Games

Nikola Ilic builds an app:

On 29 November 2010, Barcelona beat Real Madrid 5-0 at Camp Nou. This week I “watched” that match again, event by event, on a pitch inside Microsoft Fabric: Xavi at 9′, Pedro at 17′, Villa twice after the break, and Barcelona’s xG line climbing to 2.77 while Madrid’s stayed flat at 0.13.

If you know me, you know I’m a huge football and Barça fan. So when Microsoft introduced Rayfin, the open-source SDK and CLI that deploys a full application backend straight onto Fabric, I knew what my first Fabric App would be: a live match center.

This post covers what I built, the scripts that turned the whole setup into one command, and a step-by-step guide to run the same Clásico in your own workspace.

Click through for the architecture and the process. Nikola also has the repo available if you want to re-create it yourself.

Incidentally, if you want to do something similar with American football, the NFLfastR package ties in with play by play datasets going back to 1999 and that get updated the day after each game.

Leave a Comment

Tips for Planning a Microsoft Fabric Solution

Paul Turley shares some tips around the various Microsoft Fabric workloads:

Fabric hands you an entire toolbox of analytics workloads. Using all of them isn’t the goal — using the right ones is.

Resist the shiny-object trap. Fabric packages Power BI, Data Factory, Data Engineering, Data Warehouse, Data Science, and Real-Time Intelligence into one platform, and it’s tempting to adopt all of them at once. Map each workload to a business problem you already have, and bring in only the pieces that solve something real today. Every workload you adopt without a real use case behind it is one more thing your team has to learn, maintain, and eventually explain to an auditor.

Click through for a half-dozen such tips.

Leave a Comment

Report Bursting with Fabric Dataflows Gen2

Chris Webb tries something out:

When the new Send Email action was announced for Fabric Dataflows Gen2 – which allows you to send an email from a dataflow when it refreshes – I was curious to know if you could use it to send multiple emails to multiple different people, and therefore do report bursting or something like it. There are already several different ways to do this in Power BI/Fabric, for example using Power BI report subscriptions or paginated reports, but there might some cases where using a dataflow is easier or more convenient. It turns out that is is possible but only in combination with another relatively new feature: Parameterised Dataflows.

Click through for an example that sends a batch of e-mails. Not all of the functionality is fully baked yet, but it does have the potential to be interesting.

Leave a Comment

Microsoft Fabric Tenant Settings and the Govern Tab

Heidi Hasting sees something new:

Hiya!

“Ooh, what’s this?”

That was me this week, poking around the OneLake catalog. It keeps getting better and better, and I spotted something that made my admin heart very happy. The Govern tab now has Configurations > Tenant settings, right there in the catalog.

Click through to see what’s there. It’s still not ideal for non-admin users, as Heidi points out, but it is a marginal improvement over what was there before.

Leave a Comment

Creating an Azure DevOps Deployment

Reitse Eskens deploys some Microsoft Fabric assets:

Let me generalise first: you can essentially choose two options to promote your hand-crafted and superior code compared to anyone else from development to production. The first way is to use the Fabric deployment pipelines. These are essentially copy actions that move the development state to production. Option two is to use either GitHub Actions or Azure DevOps pipelines.

The main issue I’ve seen with the Fabric deployment pipelines is that the deployed code still references the development environment. This results in your notebook running in production and happily writing the results in the development lakehouse. To mitigate this, you can add actions to the Fabric pipeline, check out the newly announced Fabric deployment plans, or remember to update all references.

Click through for a high-level depiction of the process.

Leave a Comment