Fabric Architecture Podcast

By Matthias Falland

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

Download on the App Store

Download on the App Store

Get it on Google Play

FAQs about Fabric Architecture Podcast:

How many episodes does Fabric Architecture Podcast have?

The podcast currently has 32 episodes available.

Fabric Architecture Podcast episodes:

June 26, 2026The Column Named C1
The Column Named C1
Episode 26 • 2026-06-26
Duration: 9:21
A Fabric Data Agent generates queries from your column names, not your intentions. This episode pulls apart the grounding pipeline to show where accuracy lives and dies — and why the schema investment you skipped three years ago just became urgent.
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
Risks of the recommended path
The architectural principle to take home
Key takeaways
Somewhere, a data architect who's been filing those tickets for five years just felt a wave of vindication.
There's something to that. We spent years telling teams to name their columns properly and nobody listened, because the SQL worked either way. Now there's an LLM reading those column names and getting the wrong answer, and suddenly the...
Show me the query pattern — then show me the auth pattern.
Resources
Fabric data agent concepts
data-agent-add-datasources
Use the Fabric data agent in Foundry — Prerequisites
Consume Fabric data agent with Python client SDK
Consume Fabric data agent from Microsoft Foundry Services
Use service principal authentication with Fabric data agent
Evaluate your data agent
Create a Fabric data agent
Best practices for configuring your data agent
Adopt an iterative process to improve your data agent
Semantic model best practices for data agent
Fabric data agent tenant settings
Fabric data agent — Responsible AI FAQ
Data agent configurations
Workspace outbound access protection for Data Agent (Preview)
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.
Brand design based on fabricperiodictable.com.
...more
10min
June 26, 2026Why Moving Less Data Costs More
Copy Job: When Built-In State Management Beats Pipeline Plumbing
Episode 12 • 2026-03-20
Duration: 9:54
Copy Job fills the gap between Mirroring's zero-config simplicity and Pipeline's full orchestration control. We break down the architecture, the 2x incremental pricing controversy, V-Order performance traps, and when you should still reach for Pipeline Copy Activity instead.
What we discuss
A real-world mistake from a pre-Fabric era
The one question that reframes the architectural debate
How we got here — predecessor products and evolution
Why the "obvious" answer is often wrong
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
Risks of the recommended path
What Microsoft is shipping that changes the calculus
The architectural principle to take home
Key takeaways
Take-home principle. Copy Job is Copy Activity with built-in memory. Same engine, same connectors — it just remembers where it left off. Start with a full load to validate your schema. Switch to incremental once you trust it. And always —...
And that's the counterpoint to the counterpoint.
Fair question. For a team that already has mature pipeline patterns — control tables, parameterized watermarks, solid error handling — that is a legitimate choice. You pay one-point-five CU across the board and get ForEach loops,...
Resources
Copy Job Connectors
CDC Replication Connectors
VNet Data Gateway for Copy Job
CI/CD for Copy Job
Copy Job Activity
What is Copy Job in Data Factory?
Create a Copy Job
Quickstart: Create a Copy Job
CDC in Copy Job (Preview)
Copy Job Pricing
Monitor a Copy Job
Data Movement Decision Guide
Data Integration Decision Guide
What is Data Factory in Fabric?
Pricing Scenario: Copy Job 1 TB CSV to Lakehouse
About the show
Built on ElevenLabs voice synthesis. 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.
Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.
...more
10min
June 19, 2026The Function That Bills by the Row
The Function That Bills by the Row
Episode 25 • 2026-06-19
Duration: 9:01
AI Functions let you call GPT from a SELECT statement with no API key. Zero infrastructure — until you check the capacity meter. Two billing streams, no result cache, and a default model eleven days from retirement.
What we discuss
How it actually works underneath the abstraction
Where the obvious answer breaks
A real Reddit/Microsoft Q&A question unpacked
The pattern we keep seeing in the field
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
Ticking right now, in every tenant where someone put ai_classify in a view and moved on.
That quiet meter in your Capacity Metrics app.
Pattern dictates platform. If your pattern is "enrich once, read many," AI Functions are the shortest path in Fabric right now. If that pattern drifts into "enrich on every read," you're billing the LLM like a column default.
Resources
AI Functions overview
Use Azure OpenAI in Fabric with AI Functions (preview)
Warehouse AI functions (preview)
pandas similarity docs
PySpark similarity docs
pandas translate docs
Foundry Tools consumption rate page
Notebooks in Fabric
Fabric Data Warehouse
Apache Spark in Fabric
Copilot in Fabric
Data Agent in Fabric
Lakehouse overview
Customize AI Functions with pandas
Customize AI Functions with PySpark
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.
Brand design based on fabricperiodictable.com.
...more
10min
June 19, 2026Zero ETL, Thirty Times the Price
SQL Database in Fabric — When OLTP Meets Your CU Budget
Episode 11 • 2026-03-13
Duration: 9:50
SQL Database in Fabric promises zero-ETL translytical architecture — OLTP writes mirrored to OneLake automatically. But the 15-minute billing window and interactive CU consumption change the math. We break down when it makes sense and when Azure SQL Database plus mirroring is the smarter play.
What we discuss
A real-world mistake from a pre-Fabric era
The one question that reframes the architectural debate
How we got here — predecessor products and evolution
Why the "obvious" answer is often wrong
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
Risks of the recommended path
What Microsoft is shipping that changes the calculus
The architectural principle to take home
Key takeaways
That's... a genuinely good architecture. For a lot of teams, that's the right call. You lose zero-config mirroring — you set it up manually — and you lose Git integration and the GraphQL API. But you gain VNet support, CDC, Always...
Every. Single. Time. Plus the engine startup needs a two-gig minimum memory allocation. On an F2 capacity, that's... roughly your entire capacity eaten by one database.
Technically — yes, that works. But the failure mode I asked about? It's cost. When you create a SQL Database in Fabric, two items appear — the database and a SQL analytics endpoint. Both consume interactive CUs. Not background —...
Resources
SQL database in Microsoft Fabric — Overview
Mirroring Fabric SQL database
Translytical applications with SQL database
SQL database in Fabric tutorial — End-to-end architecture
Data Factory SQL database connector
GraphQL API for SQL database
Mirroring limitations
SQL analytics endpoint
Automatic Tuning
AI functions
Fabric's CI/CD framework
Limitations in SQL database in Fabric
Feature comparison: Azure SQL Database and Fabric SQL database
Billing and utilization reporting for SQL database
Mirroring Azure SQL Database to Fabric
About the show
Built on ElevenLabs voice synthesis. 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.
Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.
...more
10min
June 12, 2026The AI That Doesn't Send an Invoice
The AI That Doesn't Send an Invoice
Episode 24 • 2026-06-12
Duration: 9:11
Copilot in Fabric has no per-user license fee. But every request draws from the same capacity pool as your pipelines and reports. We dig into what 'included' actually costs — and when it throttles production.
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
F-SKU realism — what this actually costs
The concrete recommended architecture
When the rejected approach is actually right
Where the obvious answer breaks
Risks of the recommended path
The architectural principle to take home
Key takeaways
Somewhere right now, there's an F2 running Copilot for a whole team.
The most expensive support ticket you'll ever file is the one where the answer is "rename your columns.
Pattern dictates platform. And with Copilot, the pattern is this — it's a productivity tool that's already wired into your cost structure whether you planned for it or not. The teams that get value from it are the ones who treat enablement...
Resources
copilot-privacy-security
copilot-fabric-overview
data-warehouse/copilot
copilot-enable-power-bi
known-limitations table
Copilot in Fabric consumption
how-copilot-works
Copilot and Agent tenant settings
copilot-notebooks-overview
Enable Fabric Copilot for Power BI
SQL DB Copilot FAQ
overview docs
How Copilot in Microsoft Fabric works
Enable Copilot in Fabric
Fabric Copilot capacity
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.
Brand design based on fabricperiodictable.com.
...more
10min
June 12, 2026The Fifteen-Minute Blind Spot
SQL Analytics Endpoint: Read-Only by Design
Episode 10 • 2026-03-06
Duration: 10:53
The SQL Analytics Endpoint gives you T-SQL on Lakehouse data for free — but free comes with metadata sync delays, no Git integration, and silent Direct Lake fallbacks. Matthias and Fabia unpack when to use it, when to reach for a Warehouse instead, and how to avoid the traps that catch most teams.
What we discuss
A real-world mistake from a pre-Fabric era
The one question that reframes the architectural debate
How we got here — predecessor products and evolution
Why the "obvious" answer is often wrong
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
Risks of the recommended path
What Microsoft is shipping that changes the calculus
The architectural principle to take home
Key takeaways
So — the take-home. The SQL Analytics Endpoint is a projection, not a database. Use it for what it does brilliantly — SQL access to Delta tables with zero data duplication. But the moment you create your first view, the moment you need...
Fair point. And for teams that are SQL-first — BI developers, analysts who live in T-SQL — the Warehouse-only approach has real merit. You lose the zero-setup convenience, you manage a separate item, you pay for writes. But you gain...
Hm, let me think... because free has a price. The endpoint runs a background metadata sync process that pauses after fifteen minutes of inactivity. Your next query wakes it up, but now you're waiting for a full resync. And if you've got a...
Resources
What is the SQL analytics endpoint for a lakehouse?
SQL analytics endpoint — Capabilities
Decision guide: Warehouse and Lakehouse
Refresh SQL endpoint metadata
Data types in the SQL analytics endpoint
Direct Lake overview
Share a Lakehouse
Lakehouse overview
Warehouse overview
SQL Database in Fabric
OneLake shortcuts
Database mirroring
OneLake security
Cross-database queries
Better together: the lakehouse and warehouse
About the show
Built on ElevenLabs voice synthesis. 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.
Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.
...more
11min
June 05, 2026When Autolog Stops Logging
When Autolog Stops Logging
Episode 23 • 2026-06-05
Duration: 8:47
Fabric's MLflow autologging promises zero-effort experiment tracking — until you train with LightGBM or XGBoost and discover your metrics column is blank. We pull apart the framework gap, the compounding exclusive flag, and the Git backup that isn't one.
What we discuss
How it actually works underneath the abstraction
Where the obvious answer breaks
A real Reddit/Microsoft Q&A question unpacked
The pattern we keep seeing in the field
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 training run just finished.
And name your runs. Pass run_name to start_run. Forty runs all called Run followed by a number, and the comparison pane becomes useless regardless of how clean the rest of your tracking is.
The takeaway I'd leave anyone starting with Fabric Experiments — the abstraction is real, but it has seams you need to know on day one.
Resources
mlflow-upgrade
Machine learning experiments in Microsoft Fabric
Autologging in Microsoft Fabric
What is Data Science in Microsoft Fabric?
Analyze and train data in Microsoft Fabric
Hyperparameter tuning in Fabric
Perform hyperparameter tuning with FLAML
Training visualizations for AutoML
MLflow 3 in Fabric Data Science
Tutorial: Create, evaluate, and score a churn prediction model
Tutorial Part 3: Train and register a machine learning model
Train models with scikit-learn in Microsoft Fabric
Machine learning experiments and models Git integration and deployment pipelines (Preview)
Data science roles and permissions
Lineage for models and experiments
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.
Brand design based on fabricperiodictable.com.
...more
9min
June 05, 2026The SQL Endpoint That Can't Write Back
Fabric Warehouse vs. Lakehouse: Same Storage, Different Engines
Episode 9 • 2026-02-27
Duration: 15:34
Matthias and Fabia dissect the Warehouse-vs-Lakehouse decision. They explore why three SQL options exist in Fabric, when the SQL endpoint's read-only design saves you, and why judging Warehouse performance on a cold-cache first query is the mistake everyone makes.
What we discuss
A real-world mistake from a pre-Fabric era
The one question that reframes the architectural debate
How we got here — predecessor products and evolution
Why the "obvious" answer is often wrong
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
Risks of the recommended path
What Microsoft is shipping that changes the calculus
The architectural principle to take home
Key takeaways
Today's takeaway. Warehouse and Lakehouse aren't competing products. They're different engines on the same storage. Pick based on workload pattern — T-SQL, multi-table transactions, auto-optimization means Warehouse. Spark, ML,...
Fair. And honestly, for a lot of teams that works. If your reporting is read-only — dashboards, DirectLake — the SQL endpoint handles it fine. In a team of eight under cost pressure, Lakehouse plus SQL endpoint might be all you need. The...
Right. So here's where people get it wrong. The naive answer is — Warehouse is for SQL people, Lakehouse is for Spark people. Pick your tribe. But that's way too simple. The real difference isn't the language you write. It's who owns the...
Resources
Warehouse in Fabric
Create Warehouse
T-SQL surface area
Performance Guidelines
Better together: Lakehouse and Warehouse
Decision Guide: Warehouse vs Lakehouse
SQL Analytics Endpoint Performance
Result Set Caching
Data Clustering
Zero-Copy Table Clone
Time Travel
Transactions
Migration from Synapse
Architecture
Warehouse Team AMA (March 2025)
About the show
Built on ElevenLabs voice synthesis. 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.
Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.
...more
16min
May 29, 2026Your Endpoint Falls Asleep After Five Minutes
ML Models in Fabric: Training, Deployment, and When to Stay on Azure ML
Episode 22 • 2026-05-29
Microsoft Fabric ships its own MLflow registry — but is it a replacement for Azure Machine Learning? Matthias and Fabia work through the four-layer registry model, PREDICT versus Model Endpoints, the Direct Lake prediction loop, and the architectural question that actually determines the answer: where do your predictions land?
What we discuss
A real-world mistake from a pre-Fabric era
The one question that reframes the architectural debate
How we got here — predecessor products and evolution
Why the "obvious" answer is often wrong
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
Risks of the recommended path
What Microsoft is shipping that changes the calculus
The architectural principle to take home
Key takeaways
Where do the predictions land. That question answers the architecture. OneLake plus Power BI Direct Lake — Fabric ML Model, genuinely the right call. REST API for an app — evaluate Endpoints maturity or route to Azure ML. GPU training,...
I'd go further. Already on Databricks with Unity Catalog? Don't migrate. Fabric ML Model is not a migration target for Databricks shops — the platform maturity gap is real. The hybrid that actually works: train on Azure ML with GPU,...
For Power BI shops — yes. PREDICT writes predictions to a Delta table in OneLake, Direct Lake reads it with zero copy, zero scheduled refresh. That eliminates an entire class of ETL work. But only if Power BI is your audience.
Resources
ML Experiment
Notebooks
Lakehouse
Direct Lake
Code-first AutoML
Low-code AutoML
SynapseML
Activator
Machine learning model in Microsoft Fabric
What is Data Science in Microsoft Fabric?
Tutorial Part 3: Train and register a machine learning model
Tutorial Part 4: Perform batch scoring and save predictions
Machine learning model scoring with PREDICT
Serve real-time predictions with ML model endpoints (Preview)
Train models with scikit-learn in Microsoft Fabric
About the show
Built on ElevenLabs voice synthesis. 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.
Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.
...more
11min
May 29, 2026The Button That Says 'Mirror All Data' — and Doesn't
Mirrored Databases: When Zero-Code Replication Meets Real Architecture
Episode 8 • 2026-02-20
Duration: 8:18
Matthias and Fabia explore Fabric mirrored databases — the sweet spot between real-time eventstreams and batch ETL. They unpack CDC replication, the 500-table limit, schema change risks, and why setup simplicity doesn't excuse you from data modeling.
What we discuss
A real-world mistake from a pre-Fabric era
The one question that reframes the architectural debate
How we got here — predecessor products and evolution
Why the "obvious" answer is often wrong
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
Risks of the recommended path
What Microsoft is shipping that changes the calculus
The architectural principle to take home
Key takeaways
Today's takeaway — mirroring is the sweet spot between real-time eventstreams and batch ETL.
Now — let me steel-man the alternative. Hm, let me think... If your analytics can tolerate live remote queries, shortcuts are genuinely better. No data copy, no replication lag, no storage cost. In a team of eight under cost pressure,...
Kind of, yeah. The trap is skipping the data modeling conversation because setup was easy. You still need a medallion layer on top. Mirror gives you bronze — that's it. And your team will absolutely blame the mirror when queries are slow,...
Resources
Mirrored databases overview
Azure SQL DB mirroring
Azure SQL DB limitations
SQL Managed Instance limitations
SQL Server limitations
Cosmos DB mirroring
Cosmos DB limitations
Snowflake mirroring
Snowflake limitations
Troubleshooting
About the show
Built on ElevenLabs voice synthesis. 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.
Built on ElevenLabs voice synthesis. Brand design based on fabricperiodictable.com.
...more
9min

FAQs about Fabric Architecture Podcast:

How many episodes does Fabric Architecture Podcast have?

The podcast currently has 32 episodes available.