Press "Enter" to skip to content

Category: Microsoft Fabric

Fabric Studio 2.0 Released

Published 2025-07-29 by Kevin Feasel

Gerhard Brueckl has an update:

7 months after the first official release of Fabric Studio, I am very happy to share the I just released the next major version with a lot of new features that make working with Microsoft Fabric from VSCode better and more intuitive than ever! The release includes some new capabilities that I wanted to get into the tool since the very beginning but back then the APIs just weren’t there yet. Finally they are and I integrated them into Fabric Studio v2.0!

Click through for a quick changelog, a link to the full changelog, and where you can grab a copy of the Visual Studio Code extension.

Comments closed

Optimizing Multi-Notebook Jobs in Microsoft Fabric and AWS Glue

Published 2025-07-24 by Kevin Feasel

Daniel Janik flips a switch:

Are your Azure Fabric pipelines with multiple notebooks running slower than you’d like? Are you paying for more Spark compute time than you should be? The culprit might be a simple setting that’s easy to miss. In this blog post, we’ll dive into the “For pipeline running multiple notebooks” setting in Azure Fabric and explain why enabling it can significantly improve your pipeline’s performance and reduce your costs.

Click through for this, as well as a comparison with AWS Glue and ways to perform something similar there.

Comments closed

Goodbye, Default Semantic Models

Published 2025-07-22 by Kevin Feasel

Pradeep Srikakolapu makes an announcement:

Microsoft Fabric is officially sunsetting Default Semantic Models. This change is part of our ongoing efforts to simplify and improve the manageability, deployment, and governance of Fabric items such as warehouse, lakehouse, SQL database, and mirrored databases.

This is definitely a good thing. The idea of a default semantic model wasn’t bad, especially early on in Microsoft Fabric’s development life. But those default models almost never had enough information to do what customers actually want, so they would sit there as a distraction.

Comments closed

The Microsoft Fabric Service Status Page

Published 2025-07-22 by Kevin Feasel

Brent Ozar notes a new status page:

I’ve been pretty vocal here on the blog and on social media about the reliability problems with Microsoft Fabric. Today, I’ve got good news: Microsoft released a new Fabric status page and a known issues page, something that really does take guts given the current reliability situation.

It’ll be important to see how frequently they update this status page and if the page displays sufficient information on issues in a timely manner. But this is a good starting point.

Comments closed

Private Endpoints in Fabric Eventstream now GA

Published 2025-07-17 by Kevin Feasel

Alex Lin makes an announcement:

We’re excited to announce the General Availability of Managed Private Endpoints (MPE) in Fabric Eventstream. This network security feature allows you to stream data from Azure resources to Fabric over a private and secure network without the complexity of manual network configurations.

Read on to see what private endpoints give you and what’s new for general availability.

Comments closed

Error Handling in Microsoft Fabric Translytical Task Flows

Published 2025-07-16 by Kevin Feasel

Jon Vöge continues a series on write-back in Microsoft Fabric:

In my pursuit of testing out Translytical Task Flows and User Data Functions as a write-back alternative to Power Apps, I’ve come to spent a good amount of time trying to debug those features as well. Especially since they have a tendency to throw pretty non-descriptive error messages your way.

For this week’s blog post, I’ve made a small write-up of tips and tricks for troubleshooting and debugging translytical task flows, as this was something I struggled a little with myself.

Read on for several tips around better testing and error handling within these functions.

Comments closed

Access Limits in Microsoft Fabric Workspaces

Published 2025-07-16 by Kevin Feasel

Brian Kernan announces a change:

In August 2025, Microsoft Fabric will introduce workspace access limits to improve service quality, reliability, and to encourage workspace access control hygiene. This limit will be permanent once it is rolled out – each Fabric & Power BI workspace will be limited to a maximum of 1,000 users or groups in workspaces roles (Admin, Member, Contributor, Viewer). A workspace with a group over 1,000 individuals will not be impacted by this change, the number of users within a group is not impacted. Additionally, workspaces that are overlimit at the time of access limit enforcement will remain overlimit, but no additional users or groups can be added until the workspace is under-limit.

I read this and I say “Hmm…” I’m not in a position where I could say that 1000+ users in a workspace is a bad idea that they’re protecting us from, or if it’s an implicit acknowledgement of failure to scale.

Comments closed