You don’t have a data platform.
You have a staged illusion. Power BI pretending to be glue. Pipelines hiding drift. Access you can’t explain. Lineage you can’t prove. You call it analytics. It’s chaos. In this episode, we rip the mask off “modern data” and walk through what a real end-to-end platform looks like with Microsoft Fabric, OneLake, and Medallion—and why most teams quietly sabotage it by smuggling business logic into the wrong layers. By the end, you’ll know how to:

• Stop using Power BI as duct tape
• Design a single access path from raw → insight
• Enforce Bronze / Silver / Gold contracts for real (not just in slides)
• Use Fabric, OneLake, Purview, and workspaces to kill copy storms, shadow truth, and governance theater
• Stand in front of an exec and prove where a number came from

No vibes. No “modern stack” buzzwords. Just the architecture and discipline that keep your platform from rotting.
🧨 Part 1 — The Problem You’re Pretending Isn’t There We start by naming the thing nobody wants to say out loud:

• Power BI is acting as glue code, not as a BI layer
• Pipelines are masking schema drift instead of surfacing it
• You have 15 places that claim to be “truth” and none are authoritative
• Access, lineage, and logic live in people’s heads and buried notebooks

You blame “slow BI.”
It’s not BI. It’s entropy. We walk through:

• How copy storms happen: each team spins up their own warehouse, mart, or lake
• Why “just one more semantic model” creates seven conflicting truths
• How schema drift silently kills metrics at 2 a.m. while dashboards still “refresh”
• Why security is a split-brain mess of service principals, tokens, and made-up “access matrices”

Then we drop the uncomfortable line: If you can’t name your access path and your contracts, you don’t have a platform. You have sprawl.
🧩 Part 2 — Why Fabric Exists (The Autopsy Version) This isn’t a product pitch. It’s an autopsy. We break down why Fabric exists in brutally simple terms: to attack fragmentation. You’ll hear how Fabric compresses surface area:

• One identity: Entra — the same identity that hits your inbox hits your lake
• One storage layer: OneLake — open Delta tables, shortcuts instead of copies
• One governance plane: Purview + workspaces — lineage, sensitivity, and roles in one place
• One monitoring view: capacities, pipelines, warehouses, notebooks, and reports on a single heartbeat

We connect this to the real cost you’re already paying:

• Cognitive load: every engineer keeping a mental map of “which thing runs where”
• Delay-as-a-habit: nobody wants to touch the mess, so fixes lag
• Shadow truth: users stop trusting dashboards, export to Excel, and build their own numbers

Fabric is not “more.”
It’s less: fewer places to lie, fewer tools to misconfigure, fewer excuses.
🥇 Part 3 — What Fabric Actually Is: The One Platform Moment We walk through what Fabric actually gives you when you stop treating it as another logo:

• OneLake as the single organizational lake, backed by Delta/Parquet
• Experiences on top of that same storage:
  • Data Factory for ingest & orchestration
  • Data Engineering for Spark & lakehouses
  • Data Science, Warehouse, Real-Time Analytics, Power BI, Data Activator
• All sharing the same:
  • Identity (Entra)
  • Security boundary (workspaces)
  • Governance (Purview)
  • Monitoring & capacity

Key ideas we break down:

• Tables, not pipelines, are the real contract
• Shortcuts instead of copies to connect external stores without duplication
• How Direct Lake changes Power BI:
  • Semantic models read Delta in OneLake directly
  • No import bloat, no DirectQuery latency tax
  • Freshness and performance without copy storms

You’ll hear how Fabric takes Medallion from slideware to actual structure you can point at.
🪙 Part 4 — Medallion for Grown-Ups: Bronze, Silver, Gold as Contracts We reframe Medallion from “nice diagram” into enforceable contracts: Bronze — Evidence

• Immutable, append-only, source-granular
• No business rules. No deduping. No joins.
• You keep schema drift and bad data visible.
• In Fabric: Lakehouse Files (Bronze folders, Delta logs, arrival metadata)

Silver — Truth

• Validated schema, types, deduplication, conformance
• Late-arriving logic, SCDs, and reference joins properly encoded
• Tests for row counts, uniqueness, referential integrity, drift
• In Fabric: Lakehouse Tables (Delta), notebooks/Dataflows Gen2, idempotent transforms

Gold — Meaning

• Consumption-specific dimensional models and measures
• Clean star schemas, conformed dimensions, fact tables at stable grain
• Business logic in DAX measures, not buried upstream
• In Fabric: Gold Delta tables surfaced as Direct Lake semantic models

We hammer one rule home: Bronze answers what happened.
Silver answers what is true.
Gold answers what it means.
Mix them, and you lose the plot.
🧱 Part 5 — Multi-Workspace Architecture (The Nordwand Approach) We introduce the Nordwand approach: multiple workspaces with boring, consistent names and sharp boundaries:

• Platform workspaces (Dev/Test/Prod):
  • Core Lakehouse
  • Core Warehouse
  • Shared dimensions
  • Medallion pipelines
  • Monitoring artifacts
• Domain workspaces (Finance, Sales, Ops, HR, Supply Chain):
  • Dev/Test/Prod per domain
  • Shortcuts into Platform Silver
  • Domain-specific Gold models only
• Shared Analytics workspace:
  • Certified semantic models
  • Official cross-domain metrics

We show how this solves:

• Clear ownership (Platform owns Silver, domains own Gold)
• Reuse instead of copying (Shortcuts vs. shadow tables)
• Certified truth (one place for “official” metrics)
• Controlled promotion (Dev → Test → Prod via deployment pipelines and Git)

The result: fixed anchors, clear lanes, and less room for quiet corruption.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-show-podcast--6704921/support.

Follow us on:
LInkedIn
Substack