Microsoft Fabric Architecture Podcast

Microsoft Fabric Architecture Podcast

By Matthias FallandBusinessTechnology
Download on the App Store

Microsoft Fabric Architecture Podcast episodes

  • Zero ETL, Thirty Times the Price — SQL Database in Fabric

    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 —...

        • Watch the episode

        The Fabric Friday video on this topic: https://youtu.be/Jv0zQBB2Fd0

        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.

          11 min
        • The Fifteen-Minute Blind Spot — SQL Analytics Endpoint

          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...

              • Watch the episode

              The Fabric Friday video on this topic: https://youtu.be/te3TjK0z4uI

              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.

                11 min
              • The SQL Endpoint That Can't Write Back — Fabric Warehouse

                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...

                    • Watch the episode

                    The Fabric Friday video on this topic: https://youtu.be/hnADNoZcm14

                    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.

                      11 min
                    • The Button That Says 'Mirror All Data' — and Doesn't | Fabric Mirroring

                      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,...

                          • Watch the episode

                          The Fabric Friday video on this topic: https://youtu.be/rOvhLsUYDTI

                          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.

                            11 min
                          • The Pipeline That Succeeded at Nothing — Fabric Data Pipelines

                            Data Pipelines: When Orchestration Helps and When It Hurts

                            Episode 7 • 2026-02-13

                            Duration: 9:53

                            Matthias and Fabia debate when Fabric Data Pipelines earn their complexity. They unpack the orchestra-conductor mental model, walk through a real green-checkmark-but-no-data failure, and steel-man the case for skipping pipelines entirely.

                            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 it. One activity, no dependencies — schedule it directly. Multiple steps with conditional logic — pipeline. But always validate outputs. Never trust the green checkmark without checking row counts.
                              • Completely fair. If you have existing ADF, keep using it. ADF connects to Fabric natively — orchestrate Fabric items from ADF, no problem. You get the richer connector library, managed private endpoints today, event-based triggers. For...
                              • And your team will absolutely add a pipeline anyway because it feels more 'enterprise.

                                • Watch the episode

                                The Fabric Friday video on this topic: https://youtu.be/6A6ZlyIuvkw

                                Resources

                                • Data Pipelines in Fabric
                                • Activity Overview
                                • Control flow activities
                                • Pipeline Overview
                                • Copy Activity
                                • Parameters and Expressions
                                • Monitor Pipeline Runs
                                • Decision Guide: Pipeline vs Dataflow vs Spark
                                • Data Integration Strategy Guide
                                • Reddit r/MicrosoftFabric
                                • MS Q&A
                                • Stack Overflow

                                  • 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.

                                  12 min
                                • The 3 AM Variable — Spark Job Definitions

                                  Spark Job Definitions: Notebooks Are for Humans, SJDs Are for Machines

                                  Episode 6 • 2026-02-06

                                  Duration: 10:23

                                  Matthias and Fabia break down Spark Job Definitions in Microsoft Fabric — the production wrapper most teams skip until their scheduled notebook fails at 3 AM. They cover the notebook-to-SJD promotion path, why state leakage kills overnight runs, retry policies, and when a plain notebook schedule is actually fine.

                                  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

                                    • And wrap it in a Pipeline. Even if just for the alerts.
                                    • Fair. Solo workflows where the output includes visualizations — scheduled notebook is the right call. The line I draw: the moment a second person depends on that output, or it feeds a downstream system, promote it. Solo analyst with a...
                                    • Every SJD run starts clean. No leftover variables, no stale session. That's — I mean, that's the whole point. Reproducibility by design, not by discipline.

                                      • Watch the episode

                                      The Fabric Friday video on this topic: https://youtu.be/7oEBYgYZNrk

                                      Resources

                                      • What is a Spark Job Definition?
                                      • Create SJD
                                      • Run SJD
                                      • SJD Git Integration
                                      • Pipeline SJD Activity
                                      • Streaming Data into Lakehouse
                                      • Spark Best Practices
                                      • Job Queueing
                                      • Decision Guide: Pipeline vs Dataflow vs Spark
                                      • Fabric vs Synapse Spark Comparison
                                      • MS Q&A
                                      • Reddit r/MicrosoftFabric
                                      • Stack Overflow

                                        • 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.

                                        10 min
                                      • The Install Tax Nobody Counted — Fabric Environments

                                        Spark Environments: When Your Starter Pool Isn't Enough

                                        Episode 5 • 2026-01-30

                                        Duration: 9:09

                                        Matthias and Fabia dig into Spark Environments in Microsoft Fabric — the dependency management layer most teams adopt too early. They cover the Starter Pool trade-off, why publishing takes fifteen minutes, the SJD gotcha, and when percent-pip install is actually the right call.

                                        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

                                          • Fair. For pure experiments, percent-pip is the right call — session-scoped, instant, no friction. But across a team? Five people installing different versions every morning. No persistence between sessions. And good luck getting consistent...
                                          • They just added fifteen minutes to every first session for zero benefit.
                                          • Because of the publish step. When you create or update an Environment, Fabric resolves every dependency, downloads packages, builds what's basically a container image, and distributes it to compute nodes. That takes five to fifteen...

                                            • Watch the episode

                                            The Fabric Friday video on this topic: https://youtu.be/jlhWv3gcsV4

                                            Resources

                                            • Create and manage environments
                                            • Configure Starter Pools
                                            • Manage libraries
                                            • Environments GA
                                            • Reddit r/MicrosoftFabric
                                            • MS Q&A
                                            • Stack Overflow

                                              • 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.

                                              10 min
                                            • The Lakehouse You Never Created — Dataflow Gen2

                                              Dataflow Gen2: When Power Query Meets Enterprise Scale

                                              Episode 4 • 2026-01-23

                                              Duration: 11:20

                                              Matthias and Fabia unpack Dataflow Gen2 — the low-code transformation layer in Fabric. They cover staging architecture, the Gen1-to-Gen2 leap, why your dataflow is slow, multi-destination patterns, and when you should skip the visual editor entirely and reach for a notebook.

                                              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

                                                • Low-code where you can, full-code where you must.
                                                • Completely fair. And for teams with strong engineering backgrounds, notebooks are often the right call. But — here's the thing. Not every team has five Python engineers. I've worked with organizations where the data people are Excel and...
                                                • They get Gen1 performance on a Gen2 label.

                                                  • Watch the episode

                                                  The Fabric Friday video on this topic: https://youtu.be/MikCyAEmsis

                                                  Resources

                                                  • What is Dataflow Gen2?
                                                  • Dataflow Gen2 architecture
                                                  • Connector overview
                                                  • Power Query M reference
                                                  • Staging settings
                                                  • Incremental refresh
                                                  • Schedule Dataflow Gen2
                                                  • Best practices
                                                  • Create your first Dataflow Gen2
                                                  • Monitor Dataflows

                                                    • 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.

                                                    10 min
                                                  • Why Your Notebook Breaks at 2 AM — Fabric Notebooks

                                                    Fabric Notebooks: When Interactive Spark Meets Production Reality

                                                    Episode 3 • 2026-01-16

                                                    Duration: 11:26

                                                    Matthias and Fabia dig into Fabric Notebooks — the code-first data engineering workhorse. They cover starter pools vs. custom environments, the new native Python mode, the notebook-to-production gap, and why your notebook that runs perfectly at 2pm crashes in the pipeline at 2am.

                                                    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

                                                      • Completely fair. And I'll go further — I've seen teams spin up Spark to process ten megabytes of CSV. That's like renting a crane to hang a picture frame. If your transformation is row-level, SQL-expressible, and under a gig? A warehouse...
                                                      • Nope. It's one or the other. And your team will absolutely discover this at the worst possible moment — usually during a demo. The play is: develop and explore on starter pools, switch to a custom Environment only for final testing and...
                                                      • And teams do exactly that. Until they need great_expectations, or dbt-core, or some internal package. Starter pools give you the default library set — pandas, scikit-learn, plotly, the usual. But the moment you need anything custom, you...

                                                        • Watch the episode

                                                        The Fabric Friday video on this topic: https://youtu.be/FUAQZEhQtFI

                                                        Resources

                                                        • What is a notebook?
                                                        • Python experience in notebooks
                                                        • Configure Starter Pools
                                                        • Lakehouse and notebooks
                                                        • Data Wrangler
                                                        • Manage libraries
                                                        • Schedule notebook
                                                        • High Concurrency mode
                                                        • VS Code extension
                                                        • Spark Job Definition
                                                        • Notebook best practices
                                                        • Author and execute notebooks
                                                        • Notebook visualization

                                                          • 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.

                                                          11 min
                                                        • The Folder That Isn't There — OneLake Shortcuts

                                                          OneLake Shortcuts: Virtual Pointers, Real Tradeoffs

                                                          Episode 2 • 2026-01-09

                                                          Duration: 9:21

                                                          Matthias and Fabia break down OneLake shortcuts — virtual pointers that unify multi-cloud data without copies. They cover the read-write boundary, the shared credential security model, caching economics, and when a good old copy is actually the better architecture call.

                                                          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 it. Don't shortcut the architecture thinking just because the feature is called Shortcut.
                                                            • Completely fair. And in plenty of cases, that IS the right answer. I mean, architecture is not religion — if a nightly copy gives you better performance, lower cost, and simpler security? Do that. Shortcuts shine when data governance says...
                                                            • Security model. External shortcuts use stored credentials — one credential, shared by everyone who accesses that shortcut. That's a fundamentally different security posture than internal shortcuts, where your own identity passes through....

                                                              • Watch the episode

                                                              The Fabric Friday video on this topic: https://youtu.be/zjhbVF8NhWY

                                                              Resources

                                                              • OneLake Shortcuts
                                                              • Shortcut types
                                                              • Where to create shortcuts
                                                              • Shortcut authorization
                                                              • Shortcut caching
                                                              • Limitations
                                                              • Shortcut security
                                                              • Create OneLake Shortcut
                                                              • Create ADLS Gen2 Shortcut
                                                              • Create S3 Shortcut
                                                              • Create GCS Shortcut
                                                              • Shortcuts REST API
                                                              • On-premises Shortcuts
                                                              • Dataverse Shortcuts
                                                              • OneLake Overview

                                                                • 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.

                                                                11 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.