Press "Enter" to skip to content

Category: Microsoft Fabric

Microsoft Fabric November 2025 Feature Summary

Adam Saxton has a long list:

The November 2025 Fabric release introduces several major updates, including the general availability of SQL database, Cosmos DB, and enhanced mirroring support for key data sources such as SQL Server, Cosmos DB, and PostgreSQL.

This month also brings new AI-driven features like Copilot sidecar chat tools and real-time data exploration, as well as crucial platform enhancements such as Azure DevOps cross-tenant support, improved security permissions in OneLake, and expanded connectivity through new connectors and developer tooling. These updates are designed to empower users with greater flexibility, intelligence, and control across the Fabric platform.

When the table of contents is roughly three pages, you know it’s either Ignite or Build.

Comments closed

SQL Database in Fabric now GA

Anna Hoffman and Idris Motiwala make an announcement:

SQL is everywhere and Microsoft is innovating to deliver a unified experience across on-premises, cloud, and SaaS. One SQL unifies your data estate, bringing platform consistency, performance at scale, advanced security, and AI-ready tools together in one seamless experience, and SQL database in Fabric is no exception to that. At Microsoft Ignite, we’re thrilled to announce SQL database in Microsoft Fabric is officially Generally Available!

This is definitely a fluffy post, though Anna does have some linked videos that go into more detail.

Comments closed

Multiple Record Writeback for Translytical Task Flows

Jon Vöge wants to write multiple records at a time:

Having presented a few sessions on Translytical Task Flows at conferences in the past moths, there is one major recurring question:

How do you write-back multiple records at once?

If you ask me, the questions of bulk write-back/writing back multiple records at once can be understood as two separate user stories, which sound similar, but are technically different:

Click through for those two questions as well as the answer to the first.

Comments closed

Thoughts on OneLake Security

Reitse Eskens troubleshoots an issue:

Today was a very interesting day at a customer’s site, where I had some trouble determining why the OneLake security wasn’t functioning as I expected. Spoiler alert: a part was me, and a part had to do with setting up my testing account.

Click through to see what happened and for two Fabric Ideas to improve how column-level and row-level security work.

Comments closed

View Creation via Visual Queries in Microsoft Fabric

Jon Vöge creates a view:

As companies adopt Microsoft Fabric, the distance between backend artifact and Semantic Model is smaller than ever, and it feels more obvious than ever to push some of those local transformations to your Fabric Storage item of choice.

The question is. How do you do that? There are many options:

Read on for those options. Jon focuses on one for people with less database experience.

Comments closed

Deleting Default Semantic Models in Microsoft Fabric

Pradeep Srikakolapu says good riddance:

In our earlier announcement, we shared that newly created data warehouses, lakehouses and other items in Microsoft Fabric would no longer automatically generate default semantic models. This change allows customers to have more control over their modeling experience and to explicitly choose when and how to create semantic models.

Starting November 20, 2025, Power BI *default* semantic models are disconnected from their item and become independent semantic models.

Click through for an overview of those changes and how you can get rid of the default models you may still have hanging around.

Comments closed

Azure Tenants and Microsoft Fabric

Andy Cutler begins a new series on Microsoft Fabric architecture:

Our Fabric Architecture journey starts with Azure Tenants (the kick-off blog in this series is here with a few jumping-off links to get started with thinking about Fabric Architecture). If you’re ready to spent time sketching out your Fabric Capacity planning, workspace strategy, domain topology, lakehouse/warehouse creation, data loading processes…you might want to stop for a minute and think about tenants. The question I’d like you to consider is What do I need to know when working with a single or a multi-tenancy approach? Let’s unpack this question because while it might sound like a simple list, it actually shapes your governance, scalability, and Fabric operational model. If you’re a seasoned Azure Architect veteran then you already know how to decide between single and multi-tenant cloud rollouts (also, please comment if you have anything to add please), if you work with Fabric/Data and don’t really dive into Azure architecture on a daily basis then please stick around. Hopefully this blog gets you thinking about single/multi-tenant architectures and the benefits/costs.

Read on for a dive into what tenants are, the benefits of single- versus multi-tenancy, and how it all ties into Fabric.

Comments closed

Generating an Entity Diagram in a Fabric Eventhouse

Guy Reginiano announces a new tool:

As your KQL database grows, tables gather data from several Eventstreams, functions connect different tables, update policies move and transform data, and materialized views quietly keep aggregated data up to date – all working together behind the scenes 

It’s powerful, but it can also be hard to see the full picture. 

That’s exactly why we built the Entity Diagram – to give you a simple, visual way to explore how everything in your database connects.

Click through to see how it works.

Comments closed