Microsoft Fabric Architecture Podcast cover art

Microsoft Fabric Architecture Podcast

Microsoft Fabric Architecture Podcast

By: Matthias Falland
Listen for free

Season's Savings | £0.99/mo for 3 months

£5.99/mo after 3 months - terms apply. Cancel monthly
Architecture decisions for Microsoft Fabric. Anonymized real customer scenarios, cost realism, counter-arguments included. Weekly episodes aligned with Fabric Friday recordings.© 2026 Matthias Falland Economics
Episodes
  • A Label Is Not a Lock

    A Label Is Not a Lock
    Oct 30 2026
    A Label Is Not a Lock Episode 43 • 2026-10-30 Duration: 9:02 A sensitivity label says Highly Confidential in the header, but inside Fabric it never decides who opens the item. This episode traces where labels actually control access and where the appearance of a lock is just a sign. What we discuss The pattern we keep seeing in the fieldHow it actually works underneath the abstractionWhere the obvious answer breaksA real Reddit/Microsoft Q&A question unpackedF-SKU realism — what this actually costsWhen the rejected approach is actually rightThe concrete recommended architectureRisks of the recommended pathThe architectural principle to take home Key takeaways Right now, somewhere, there's a lakehouse with Highly Confidential in the header.Show me the query pattern. If the pattern is "restrict who opens this," design the workspace. If the pattern is "protect what leaves," design the label. Conflating them is where every thread on that forum starts.And the protection policy sits in between. From the video Demo 1: The Label Changed NothingArchitecture film: Two questions two mechanismsArchitecture film: Eight routes onto an itemArchitecture film: Where protection startsArchitecture film: Where label and permission meet Resources Sensitivity labels in Power BISensitivity labels troubleshootingProtected sensitivity labels in Fabric and Power BIRoles in workspacesPermission modelRow-level security (RLS) with Power BIInformation protection in Microsoft FabricProtection policies in Microsoft FabricRestrict access to content by using sensitivity labels to apply encryptionExport data from a Power BI visualizationApply sensitivity labels to Fabric itemsDefault label policy for Fabric and Power BIMandatory label policy for Fabric and Power BIDomain-level default sensitivity labelsInformation protection 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.
    Show More Show Less
    9 mins
  • Five Thousand Files From a Blank Report

    Five Thousand Files From a Blank Report
    Oct 23 2026
    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 abstractionThe pattern we keep seeing in the fieldWhere the obvious answer breaksA real Reddit/Microsoft Q&A question unpackedF-SKU realism — what this actually costsWhen the rejected approach is actually rightThe concrete recommended architectureThe 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 blocksArchitecture film: Each layer is a contractDemo 1: Bronze That Copies NothingDemo 2: Silver as a ContractArchitecture film: When recipe is wrong Resources Understand medallion architecture for Fabric with OneLakeOneLake patterns and foundational capabilitiesCommon dbt job patternsModern data warehouse medallion architecture in Microsoft FabricWhat are materialized lake views?Spark SQL referenceOptimal refreshCross-workload table maintenance and optimizationWhat's newLakehouse Maintenance activityApache Spark billing and utilizationextended capabilitiesCDF pageData quality in materialized lake viewsManage 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.
    Show More Show Less
    10 mins
  • Five Doors and One Credential

    Five Doors and One Credential
    Oct 22 2026
    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 abstractionWhere the obvious answer breaksThe pattern we keep seeing in the fieldA real Reddit/Microsoft Q&A question unpackedF-SKU realism — what this actually costsWhen the rejected approach is actually rightRisks of the recommended pathThe concrete recommended architectureThe 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 Data3:17 Demo: Mirror a Catalog from Unity Catalog8:37 Demo: One Credential for Everyone, and a Revoke That Takes an Hour23:49 Who Pays17:02 The Reverse Direction Is Three Different Things Resources Mirroring Azure Databricks Unity CatalogSecure Fabric mirrored databases from Azure DatabricksTutorial: Configure Microsoft Fabric mirrored databases from Azure DatabricksEnable external data access to Unity CatalogPublish a Unity Catalog catalog to Microsoft FabricLimitations in Microsoft Fabric mirrored databases from Azure DatabricksEnable OneLake catalog federationIntegrate OneLake with Azure DatabricksConnect Azure Databricks to a OneLake external locationFabric capacity and OneLake consumptionOneLake compute and storage consumptionUnderstand your Azure bill for a Fabric capacityShortcuts in a lakehouseMirrored Azure Databricks Unity Catalog definitionOneLake 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.
    Show More Show Less
    9 mins
adbl_web_anon_alc_button_suppression_t1
No reviews yet