Microsoft Fabric Architecture Podcast

By Matthias FallandBusiness Technology

Microsoft Fabric Architecture Podcast episodes

October 23Five Thousand Files From a Blank Report
Five Thousand Files From a Blank Report
Episode 42 • 2026-10-23
Duration: 10:17
Medallion is the recommended design approach for Fabric. It's also one building block out of five, and the one that sends you a maintenance invoice nobody put on the architecture diagram. What the file-count guardrail means for Direct Lake on OneLake, why schema-enabled lakehouses can't use the automated maintenance activity, and when the whole pattern is overkill.
What we discuss
How it actually works underneath the abstraction
The pattern we keep seeing in the field
Where the obvious answer breaks
A real Reddit/Microsoft Q&A question unpacked
F-SKU realism — what this actually costs
When the rejected approach is actually right
The concrete recommended architecture
The architectural principle to take home
Key takeaways
Somewhere right now, there's a table sitting at four thousand files on an F64.
The price of that answer is maintenance. A schedule, a monitor, and someone who knows where TABLETRAITS lives.
Architecture is not religion. Medallion answers one question — what is each stage trusted for — and it leaves the other four to the other four bricks.
From the video
Architecture film: Five building blocks
Architecture film: Each layer is a contract
Demo 1: Bronze That Copies Nothing
Demo 2: Silver as a Contract
Architecture film: When recipe is wrong
Resources
Understand medallion architecture for Fabric with OneLake
OneLake patterns and foundational capabilities
Common dbt job patterns
Modern data warehouse medallion architecture in Microsoft Fabric
What are materialized lake views?
Spark SQL reference
Optimal refresh
Cross-workload table maintenance and optimization
What's new
Lakehouse Maintenance activity
Apache Spark billing and utilization
extended capabilities
CDF page
Data quality in materialized lake views
Manage materialized lake views lineage
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
11 min
October 22Five Doors and One Credential
Five Doors and One Credential
Episode 41 • 2026-09-18
Duration: 8:45
Databricks and Fabric have five integration paths, not one. Each moves data. None moves permissions. We pull apart the one-credential model, the hour-long revoke delay, and the ADLS shortcut that silently bypasses Unity Catalog's row-level security.
What we discuss
How it actually works underneath the abstraction
Where the obvious answer breaks
The pattern we keep seeing in the field
A real Reddit/Microsoft Q&A question unpacked
F-SKU realism — what this actually costs
When the rejected approach is actually right
Risks of the recommended path
The concrete recommended architecture
The architectural principle to take home
Key takeaways
Every path between these platforms moves data.
Somewhere right now, a mirrored catalog is serving a workspace that was supposed to see two schemas.
And accept that "keep access configurations synchronized" is documentation for there is no sync.
Watch the episode
The Fabric Friday video on this topic: https://youtu.be/RAqhXwSj_HE
From the video
13:33 Demo: Direct Lake Over Databricks Data
3:17 Demo: Mirror a Catalog from Unity Catalog
8:37 Demo: One Credential for Everyone, and a Revoke That Takes an Hour
23:49 Who Pays
17:02 The Reverse Direction Is Three Different Things
Resources
Mirroring Azure Databricks Unity Catalog
Secure Fabric mirrored databases from Azure Databricks
Tutorial: Configure Microsoft Fabric mirrored databases from Azure Databricks
Enable external data access to Unity Catalog
Publish a Unity Catalog catalog to Microsoft Fabric
Limitations in Microsoft Fabric mirrored databases from Azure Databricks
Enable OneLake catalog federation
Integrate OneLake with Azure Databricks
Connect Azure Databricks to a OneLake external location
Fabric capacity and OneLake consumption
OneLake compute and storage consumption
Understand your Azure bill for a Fabric capacity
Shortcuts in a lakehouse
Mirrored Azure Databricks Unity Catalog definition
OneLake storage tiers
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
9 min
October 16Throttled by Yesterday's Refresh
Throttled by Yesterday's Refresh
Episode 37 • 2026-10-16
Duration: 9:21
Fabric doesn't charge you when work happens — it spreads the cost forward into 2,880 thirty-second timepoints. That one sentence explains every confusing capacity behavior, including why surge protection can reject the SQL it's supposed to protect.
What we discuss
How it actually works underneath the abstraction
Where the obvious answer breaks
A real Reddit/Microsoft Q&A question unpacked
F-SKU realism — what this actually costs
When the rejected approach is actually right
Risks of the recommended path
The architectural principle to take home
Key takeaways
And someone's about to halve the SKU because the chart looks calm.
The spike they see is a receipt. The smoothed line is the bill that hasn't arrived.
Right now, somewhere, there's a capacity chart with a quiet-looking evening.
Watch the episode
The Fabric Friday video on this topic: https://youtu.be/iE-jdcseCaY
From the video
7:42 Demo: Watch One Job Spread
9:51 The Throttling Staircase, and Who Skips Steps
2:50 Demo: Read the Metrics App
12:46 Sizing From the Smoothed Line
Resources
Fabric capacity throttling policy
Smoothing and throttling in Fabric Data Warehouse
Throttle triggers and throttle stages
Capacity planning guide
Autoscale Billing for Spark
Fabric operations: interactive and background
Understand the metrics app timepoint page
Understand the metrics app timepoint summary page
Surge protection
Capacity and SKUs
Burstable capacity in Fabric Data Warehouse
Consumption rates and billing for Copilot in Fabric
Azure quotas for Fabric capacities
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
10 min
October 09Your Domain Isn't a Wall
Your Domain Isn't a Wall
Episode 38 • 2026-10-09
Duration: 8:43
Fabric domains look like governance boundaries but the documentation says otherwise. We unpack what a domain actually gives you, the default-domain mechanism that's still running in your tenant, and why the label on the cabinet is not the lock.
What we discuss
How it actually works underneath the abstraction
The pattern we keep seeing in the field
A real Reddit/Microsoft Q&A question unpacked
Where the obvious answer breaks
F-SKU realism — what this actually costs
When the rejected approach is actually right
Risks of the recommended path
The architectural principle to take home
Key takeaways
There's a filing cabinet in every office with a label on the front.
Pattern dictates platform. If the pattern is "organize and find," a domain is the right tool. If the pattern is "restrict and protect," you're in the wrong layer.
So here's where I'd land. A domain answers "whose data is this." Use it for discovery and delegation. Build your actual boundaries with workspace roles and item permissions. And audit that default domain list quarterly, because it's still running.
Watch the episode
The Fabric Friday video on this topic: https://youtu.be/8wRSvnF_CtQ
From the video
7:46 Demo: The Contributor Who Cannot Contribute
3:15 Demo: The Filter That Is Not a Fence
12:51 Demo: An Assignment Nobody Made
14:42 The Sensitivity Label Override Ladder
Resources
Fabric domains
Power BI implementation planning: Tenant administration
Best practices for domains
Domain-level default sensitivity labels
Endorsement overview
OneLake catalog overview
Scope the catalog to a particular domain
Governance overview and guidance
Roles in workspaces
About tenant settings
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
9 min
October 06Where Do the Columns Come From?
Where Do the Columns Come From?
Episode 40 • 2026-09-25
Duration: 9:19
Cosmos DB has no schema. Delta tables need one. When mirroring bridges the two, the replicator guesses — and the guess only ever widens. We trace where the bytes come from, why renamed properties leave ghost columns full of nulls, and what stop replication actually does.
What we discuss
How it actually works underneath the abstraction
The pattern we keep seeing in the field
A real Reddit/Microsoft Q&A question unpacked
Where the obvious answer breaks
Risks of the recommended path
F-SKU realism — what this actually costs
When the rejected approach is actually right
The concrete recommended architecture
The architectural principle to take home
Key takeaways
Somewhere right now a Cosmos container is taking writes.
And match your Fabric capacity region to the Cosmos account.
Three questions before you touch anything.
Watch the episode
The Fabric Friday video on this topic: https://youtu.be/KJUBmoNFICo
From the video
13:19 The Discovered Schema
16:20 Nested Data Arrives as a String
18:47 Stop Is Not Pause
2:53 Demo: Create the Mirror, Count the Rows
Resources
Mirroring Azure Cosmos DB
Cosmos DB mirroring FAQ
continuous backup
Cosmos DB mirroring limitations
Migrate an Azure Cosmos DB account from periodic to continuous backup mode
Migrate from Azure Synapse Link to Cosmos DB mirroring
Access mirrored data in Lakehouse and notebooks
How to: Query nested data
Configure private networks for Azure Cosmos DB Fabric Mirroring
tutorial
Monitor Fabric mirrored database replication
Mirroring public REST API
Cost of mirroring
Mirrored database in Fabric (all sources)
Cosmos DB in Microsoft Fabric (native item)
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
10 min
September 04The Permission Split Inside Read-Only
The Permission Split Inside Read-Only
Episode 36 • 2026-10-02
Duration: 8:03
A workspace carries four boundaries — security, cost, region, lifecycle — and you configured one of them. This episode pulls apart what 'read-only' actually means in Fabric, why OneLake security cannot fence in a Contributor, and the silent security change hiding inside every role promotion.
What we discuss
How it actually works underneath the abstraction
The pattern we keep seeing in the field
A real Reddit/Microsoft Q&A question unpacked
Where the obvious answer breaks
F-SKU realism — what this actually costs
When the rejected approach is actually right
Risks of the recommended path
The architectural principle to take home
Key takeaways
Somewhere right now, someone's promoting a colleague to Contributor so they can fix a report.
Show me the query pattern. That tells you whether Viewer plus OneLake security is enough, or whether you need to split.
Here's what I'd carry out of this. Every workspace is a cut through the lake, and cuts carry consequences. Security, cost, region, lifecycle — you're deciding all four whether you chose them or not.
Watch the episode
The Fabric Friday video on this topic: https://youtu.be/tpePwivxtzk
From the video
6:25 Demo: Same Table, Two Routes
12:28 Demo: Watch the Override
14:35 Who Can Claim Your Workspace
Resources
Roles in workspaces
Permission model
Give users access to workspaces
OneLake security access control model
Capacity reassignment restrictions
Understand Fabric licenses and capacity
Manage workspaces
What is a lakehouse
Reassign a workspace to a different capacity
Create a workspace
Workspace roles in Fabric Data Warehouse
Workspace roles in Lakehouse
Roles in workspaces in Power BI
Build permission for shared semantic models
Get started with Microsoft Fabric
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
9 min
August 28The Snapshot Locked in a Room
The Snapshot Locked in a Room
Episode 35 • 2026-08-28
Duration: 8:42
Graph in Fabric materializes a second copy of your data for traversal. That copy explains the staleness, the rebuild cycle, and the workspace boundary that decides whether graph belongs in your architecture.
What we discuss
How it actually works underneath the abstraction
The pattern we keep seeing in the field
A real Reddit/Microsoft Q&A question unpacked
Where the obvious answer breaks
The concrete recommended architecture
F-SKU realism — what this actually costs
When the rejected approach is actually right
Risks of the recommended path
The architectural principle to take home
Key takeaways
And somewhere right now, there's a queryset returning a result that was true yesterday.
A query timeout of twenty minutes. That's a ceiling you can plan around.
What you can't plan around is the copy. It's stale between rebuilds, locked to the workspace, and if you query it carelessly it hands you a partial answer with a warning you didn't read. Accept those three things and it solves relationship...
From the video
Architecture film: Snapshot not view
Architecture film: Four ways to ask
Architecture film: Staleness chain
Demo 3: Change the Model, Watch the Queryset
Architecture film: The ceilings
Resources
How graph in Microsoft Fabric works
Current limitations of graph in Microsoft Fabric
Troubleshooting and FAQ for graph
Quickstart: Create your first graph
Tutorial: Introduction to graph
Tutorial: Query the graph by using the query builder
Example graph datasets
Optimize GQL query performance
GQL language guide
GQL quick reference
GQL query API (REST)
Graph data models
Design a graph schema
Fabric Data Agent
OneLake security
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
9 min
August 21The Radio Button That Decides Your Security Architecture
The Radio Button That Decides Your Security Architecture
Episode 34 • 2026-08-21
Duration: 8:36
A connectivity dialog in Fabric's API for GraphQL looks like a setup step. It quietly decides who needs permissions where, whether row-level security means anything, and whether your production API serves development data after every deployment.
What we discuss
How it actually works underneath the abstraction
A real Reddit/Microsoft Q&A question unpacked
Where the obvious answer breaks
F-SKU realism — what this actually costs
When the rejected approach is actually right
The concrete recommended architecture
Risks of the recommended path
The architectural principle to take home
Key takeaways
The thing that stays with me... a generated API feels managed. Like it's watching your source and keeping up.
And the decision that matters most isn't which source to connect.
Pattern dictates platform. If the pattern is an app team needing typed, authenticated access to warehouse data, this is the right tool.
Watch the episode
The Fabric Friday video on this topic: https://youtu.be/IuGCxyLWzo0
From the video
2:34 Demo: An API in Ninety Seconds
19:42 Demo: Schema Drift, Live
17:07 What Deployment Actually Does
14:48 Demo: Two Sources, One Query
Resources
Fabric API for GraphQL FAQ
Limitations of Microsoft Fabric API for GraphQL
Connect AI Agents to Fabric API for GraphQL with a local MCP server
What is Microsoft Fabric API for GraphQL?
Create an API for GraphQL in Fabric and add data
Connect applications to Fabric API for GraphQL
Source control and deployment pipelines in API for GraphQL
Fabric API for GraphQL editor
Query multiple data sources in Fabric API for GraphQL
Use service principals with Fabric API for GraphQL
Expose stored procedures
Performance best practices
Create GraphQL API from your SQL database
Develop GraphQL applications in Visual Studio Code
Private Links overview
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
9 min
August 14When Save Grants Permissions You Can't Revoke
When Save Grants Permissions You Can't Revoke
Episode 33 • 2026-08-14
Duration: 8:26
An org app is a Fabric item that manages permissions on other items. We pull apart what it actually propagates, where the abstraction stops, and why some grants outlive the authority that created them.
What we discuss
How it actually works underneath the abstraction
The pattern we keep seeing in the field
Where the obvious answer breaks
A real Reddit/Microsoft Q&A question unpacked
Risks of the recommended path
F-SKU realism — what this actually costs
When the rejected approach is actually right
The concrete recommended architecture
The architectural principle to take home
Key takeaways
Somewhere right now there's a semantic model in workspace B with a permission entry that nobody in workspace A can remove.
The sentence to say before you build one: the org app handles THESE permissions.
An org app is an item that manages permissions on other items.
From the video
Architecture film: An item not a publication
Architecture film: Propagation tree
Demo 2: Grant, Inspect, Revoke
Architecture film: The hidden content switch
Resources
Get started with org apps
Collaborate with Power BI in Teams
CI/CD for org apps in Fabric
How to integrate notebooks with Org app
Share Fabric Maps: Org apps
Workspace roles in Microsoft Fabric
Publish an app in Power BI
Apps in Power BI (consumer view)
Direct Lake overview – permission requirements
Email subscriptions for reports
Get started with Git integration
Source code format – automatically generated system files
Focus mode in Fabric
Fabric preview features
Power BI add-in for PowerPoint
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
9 min
August 07Your App Published. Nobody Noticed.
Your App Published. Nobody Noticed.
Episode 32 • 2026-08-07
Duration: 8:22
A Power BI app update succeeds and every consumer sees nothing. The publish boundary copies more than you think, grants less than you expect, and fails without a sound.
What we discuss
How it actually works underneath the abstraction
The pattern we keep seeing in the field
Where the obvious answer breaks
A real Reddit/Microsoft Q&A question unpacked
The concrete recommended architecture
F-SKU realism — what this actually costs
When the rejected approach is actually right
The architectural principle to take home
Risks of the recommended path
Key takeaways
Somewhere right now, an app update just succeeded.
The workspace app is built around one idea — publishing makes a copy.
My advice: if you need the gate, accept what the gate costs.
From the video
Architecture film: The publish boundary
Architecture film: Permission arithmetic
Demo 2: The Hidden-by-Default Trap
Demo 3: The Pipeline Moves the Content, Not the App
Resources
Apps in Power BI
Get started with org apps
Publish an app in Power BI – Considerations and limitations
Power BI enhanced report format (PBIR)
Collaborate with Power BI in Teams
Workspaces in Power BI
Create a workspace in Power BI
End-to-end: From raw data to a shared Power BI app
The deployment pipelines process
Best practices for lifecycle management in Fabric
App tenant settings
What are Power BI template apps?
Create a template app in Power BI
Create your first Fabric app
Strategy for using groups
About the show
AI-generated voices. Matthias — cloned voice. Fabia — designed AI co-host. See Matthias live on YouTube (Fabric Friday), at his meetups, and at conferences like FabCon.
Hosted by Matthias Falland — Microsoft Data Platform MVP and community architect behind the Fabric Periodic Table. New episodes every Friday.
Submit your case
Have an architecture decision you are wrestling with? DM Matthias on LinkedIn — find him as Matthias Falland. Three to five sentences about the decision, your team size, and your current stack. We anonymize before airing.
This podcast was generated by AI. Both voices are synthetic: Matthias is a cloned voice, Fabia is a designed AI co-host.
Brand design based on fabricperiodictable.com.
9 min

About Microsoft Fabric Architecture Podcast

From the publisher's feed

Architecture decisions for Microsoft Fabric. Anonymized real customer scenarios, cost realism, counter-arguments included. Weekly episodes aligned with Fabric Friday recordings.

Share Microsoft Fabric Architecture Podcast

Sign up to save your podcasts

Microsoft Fabric Architecture Podcast

Microsoft Fabric Architecture Podcast episodes

About Microsoft Fabric Architecture Podcast