Episodes

  • Do You Need Purview for a Fabric-Only Estate?

    Do You Need Purview for a Fabric-Only Estate?
    Nov 6 2026

    Do You Need Purview for a Fabric-Only Estate?

    Episode 44 • 2026-11-06 Duration: 8:39

    Purview is a brand and an account — two different purchases. We break down what a Fabric-only tenant already gets from Govern, where native lineage stops, and why buying a Purview account for lakehouse lineage doesn't close the gap.

    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
    • Risks of the recommended path
    • The concrete recommended architecture
    • The architectural principle to take home

    Key takeaways

    • Somewhere in your Fabric tenant there's a Govern page that refreshes once a day, reads metadata no one had to scan, and quietly counts what you own.
    • One platform, one metadata service. The catalog reads it in place.
    • And the lineage gaps on the lakehouse side don't close by adding a Purview account.

    From the video

    • Demo 1: Govern, Seen by Three People
    • Demo 2: Lineage Until It Stops
    • Architecture film: When you need a purview account
    • Architecture film: What you already have

    Resources

    • Use Microsoft Purview to protect Microsoft Fabric
    • Governance overview and guidance
    • enable labels
    • DLP planning
    • DLP get started
    • audit solutions
    • billing models
    • register and scan Fabric
    • data governance billing
    • free version
    • OneLake catalog overview
    • Catalog - Search
    • item details
    • What's new
    • Govern your Fabric data estate

    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
  • 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
  • Throttled by Yesterday's Refresh

    Throttled by Yesterday's Refresh
    Oct 16 2026
    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 abstractionWhere the obvious answer breaksA real Reddit/Microsoft Q&A question unpackedF-SKU realism — what this actually costsWhen the rejected approach is actually rightRisks of the recommended pathThe 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 Spread9:51 The Throttling Staircase, and Who Skips Steps2:50 Demo: Read the Metrics App12:46 Sizing From the Smoothed Line Resources Fabric capacity throttling policySmoothing and throttling in Fabric Data WarehouseThrottle triggers and throttle stagesCapacity planning guideAutoscale Billing for SparkFabric operations: interactive and backgroundUnderstand the metrics app timepoint pageUnderstand the metrics app timepoint summary pageSurge protectionCapacity and SKUsBurstable capacity in Fabric Data WarehouseConsumption rates and billing for Copilot in FabricAzure 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.
    Show More Show Less
    9 mins
  • The Fence That Isn't There — Fabric Domains

    The Fence That Isn't There — Fabric Domains
    Oct 9 2026

    The Fence That Isn't There

    Episode 38 • 2026-09-18 Duration: 9:13

    Fabric domains look like security boundaries. They're metadata. Every user in your tenant can see every domain name, the contributor role only matters in the hands of someone who is already a workspace admin, and the default domain keeps running when nobody's watching. This episode opens up what a domain actually is — and the specific trap teams walk into when they treat a label as a wall.

    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
    • Risks of the recommended path
    • The architectural principle to take home

    Key takeaways

    • There is, in somebody's tenant tonight, a domain named after something a dozen people weren't supposed to know about.
    • The lesson transfers anywhere. A domain answers 'whose data is this'. It doesn't answer 'who may see it'. Those are different questions, they live at different layers, and every time someone collapses them, they end up with structure that...
    • If you come expecting a boundary, you'll be frustrated.

    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.
    Show More Show Less
    9 mins
  • Where Do the Columns Come From?

    Where Do the Columns Come From?
    Oct 6 2026
    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 abstractionThe pattern we keep seeing in the fieldA real Reddit/Microsoft Q&A question unpackedWhere the obvious answer breaksRisks of the recommended pathF-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 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 Schema16:20 Nested Data Arrives as a String18:47 Stop Is Not Pause2:53 Demo: Create the Mirror, Count the Rows Resources Mirroring Azure Cosmos DBCosmos DB mirroring FAQcontinuous backupCosmos DB mirroring limitationsMigrate an Azure Cosmos DB account from periodic to continuous backup modeMigrate from Azure Synapse Link to Cosmos DB mirroringAccess mirrored data in Lakehouse and notebooksHow to: Query nested dataConfigure private networks for Azure Cosmos DB Fabric MirroringtutorialMonitor Fabric mirrored database replicationMirroring public REST APICost of mirroringMirrored 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.
    Show More Show Less
    9 mins
  • The Permission Split Inside Read-Only

    The Permission Split Inside Read-Only
    Sep 4 2026
    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 abstractionThe pattern we keep seeing in the fieldA real Reddit/Microsoft Q&A question unpackedWhere the obvious answer breaksF-SKU realism — what this actually costsWhen the rejected approach is actually rightRisks of the recommended pathThe 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 Routes12:28 Demo: Watch the Override14:35 Who Can Claim Your Workspace Resources Roles in workspacesPermission modelGive users access to workspacesOneLake security access control modelCapacity reassignment restrictionsUnderstand Fabric licenses and capacityManage workspacesWhat is a lakehouseReassign a workspace to a different capacityCreate a workspaceWorkspace roles in Fabric Data WarehouseWorkspace roles in LakehouseRoles in workspaces in Power BIBuild permission for shared semantic modelsGet 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.
    Show More Show Less
    8 mins