Microsoft Fabric Architecture Podcast

Matthias Falland
  • 0.0 (0)
  • Technology

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

  1. Sep 4

    The Folder That Carries Four Boundaries — Fabric Workspaces

    The Folder That Carries Four Boundaries Episode 36 • 2026-09-04 Duration: 10:19 A Fabric workspace isn't a folder — it's a cut through OneLake carrying every access rule, capacity bill, and residency commitment. Fabia and Matthias trace the boundaries hiding inside one object, starting with the documented fact that Contributor overrides OneLake security and ending with why a cross-region move is a deletion disguised as a dropdown. 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 Risks of the recommended path F-SKU realism — what this actually costs When the rejected approach is actually right The architectural principle to take home Key takeaways Somewhere in your tenant right now, a workspace someone created in thirty seconds is quietly running up a bill in a region nobody chose. Four boundaries. Creating a workspace means deciding who reads the data, what capacity it burns, which region holds it, and how it moves through your release cycle. The one people hear is the first. The other three sit there, quietly... If your team needs to build inside the workspace, Contributor is the minimum role that lets them do the work. Resources Roles in workspaces Permission model Give users access to workspaces OneLake security access control model Capacity reassignment restrictions Understand Fabric licenses and capacity Manage workspaces What is a lakehouse Reassign a workspace to a different capacity Create a workspace Workspace roles in Fabric Data Warehouse Workspace roles in Lakehouse Roles in workspaces in Power BI Build permission for shared semantic models Get 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.

    The Folder That Carries Four Boundaries — Fabric Workspaces

  2. Aug 28

    When Your Graph Query Lies to You — Fabric Graph

    When Your Graph Query Lies to You Episode 35 • 2026-08-28 Duration: 9:41 Graph in Fabric materialises a snapshot of your data's relationships the moment you save the model. That one decision explains the stale queryset, the failed-to-load error and the corruption right after a save. The 64 MB truncation is a separate limit, and it is the one nobody warns you about. What we discuss How it actually works underneath the abstraction Where the obvious answer breaks A real Reddit/Microsoft Q&A question unpacked Risks of the recommended path The concrete recommended architecture F-SKU realism — what this actually costs When the rejected approach is actually right The pattern we keep seeing in the field The architectural principle to take home Key takeaways A graph in Fabric is a photograph of your data's relationships. Three products, zero overlap. Good luck with that steering committee. Show me the query pattern. If the question is about paths between entities, and the audience is the team that owns the data, graph gives you something SQL genuinely cannot express. If the audience needs to leave the workspace, or if a join... Resources How graph in Microsoft Fabric works Current limitations of graph in Microsoft Fabric Troubleshooting and FAQ for graph Quickstart: Create your first graph Tutorial: Introduction to graph Tutorial: Query the graph by using the query builder Example graph datasets Optimize GQL query performance GQL language guide GQL quick reference GQL query API (REST) Graph data models Design a graph schema Fabric Data Agent OneLake security 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.

    When Your Graph Query Lies to You — Fabric Graph

  3. Aug 21

    The Radio Button That Sets Your Security Architecture — API for GraphQL

    The Radio Button That Sets Your Security Architecture Episode 34 • 2026-08-21 Duration: 10:47 Fabric generates a GraphQL API from your warehouse in under a minute. But the connectivity dialog you see once decides your security posture, your RLS enforcement, and whether your production deployment silently reads development data. We trace the consequences. What we discuss How it actually works underneath the abstraction Where the obvious answer breaks The pattern we keep seeing in the field A real Reddit/Microsoft Q&A question unpacked The concrete recommended architecture Risks of the recommended path F-SKU realism — what this actually costs When the rejected approach is actually right The architectural principle to take home Key takeaways Somewhere right now there's a GraphQL API returning clean JSON, passing every health check, serving an app that went live last quarter — and the table it's describing hasn't looked like that since May. — which means the schema-drift problem we've been circling for ten minutes now applies to whatever your agents are reading too. And look — saved credentials are genuinely the right answer in a real set of cases. Resources Fabric API for GraphQL FAQ Limitations of Microsoft Fabric API for GraphQL Connect AI Agents to Fabric API for GraphQL with a local MCP server What is Microsoft Fabric API for GraphQL? Create an API for GraphQL in Fabric and add data Connect applications to Fabric API for GraphQL Source control and deployment pipelines in API for GraphQL Fabric API for GraphQL editor Query multiple data sources in Fabric API for GraphQL Use service principals with Fabric API for GraphQL Expose stored procedures Performance best practices Create GraphQL API from your SQL database Develop GraphQL applications in Visual Studio Code Private Links overview 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.

    The Radio Button That Sets Your Security Architecture — API for GraphQL

  4. Aug 14

    The Permission Broker That Outlives You — Org Apps in Fabric

    The Permission Broker That Outlives You Episode 33 • 2026-08-14 Duration: 9:45 Org apps solved the decade-old broken-visual problem by managing permissions along the dependency chain. But the same engine that grants access on your behalf can leave records behind that you no longer have the rights to remove, and a single audience toggle can blow open an entire app. 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 The concrete recommended architecture Risks of the recommended path The architectural principle to take home Key takeaways Somewhere right now, there's a semantic model with an access record that was created by an org app edit, by someone who no longer has the authority to undo it. Pattern dictates platform. If your consumers need curated views of live workspace content, and you don't need dashboards, scorecards, or a publish gate — the org app is genuinely better at that job than workspace apps have ever been. The... The thing I'd carry out of this episode is simpler than the feature list. Resources Get started with org apps Collaborate with Power BI in Teams CI/CD for org apps in Fabric How to integrate notebooks with Org app Share Fabric Maps: Org apps Workspace roles in Microsoft Fabric Publish an app in Power BI Apps in Power BI (consumer view) Direct Lake overview – permission requirements Email subscriptions for reports Get started with Git integration Source code format – automatically generated system files Focus mode in Fabric Fabric preview features Power BI add-in for PowerPoint 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.

    The Permission Broker That Outlives You — Org Apps in Fabric

  5. Aug 7

    When Publish Succeeds and Nothing Changes — Power BI Apps

    When Publish Succeeds and Nothing Changes Episode 32 • 2026-08-07 Duration: 9:10 Power BI workspace apps promise a clean publish boundary between builders and consumers. But the mechanism that makes that boundary work — the copy, the separate IDs, the audience arithmetic — carries five traps that all fail in silence. 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 Risks of the recommended path F-SKU realism — what this actually costs When the rejected approach is actually right The architectural principle to take home Key takeaways Pattern dictates platform. And this platform's pattern is silence. Somewhere right now, a team published their app, added three reports, and is waiting for users to call about them. The call's never coming. The reports are there,... The thing I'd take from today is that this system was designed to succeed without confirming the outcome. Which is exactly right for teams where speed matters more than ceremony. Resources Apps in Power BI Get started with org apps Publish an app in Power BI – Considerations and limitations Power BI enhanced report format (PBIR) Collaborate with Power BI in Teams Workspaces in Power BI Create a workspace in Power BI End-to-end: From raw data to a shared Power BI app The deployment pipelines process Best practices for lifecycle management in Fabric App tenant settings What are Power BI template apps? Create a template app in Power BI Create your first Fabric app Strategy for using groups 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.

    When Publish Succeeds and Nothing Changes — Power BI Apps

  6. Jul 31

    The Database Hiding Inside Your Scorecard — Fabric Scorecards

    The Database Hiding Inside Your Scorecard Episode 31 • 2026-07-31 Duration: 10:32 A scorecard silently creates its own semantic model the moment you hit New. That one architectural fact — that it's a stateful writer, not a read-only lens — explains why RLS doesn't carry over, why refresh breaks upstream, and why rollups leak across permission boundaries. 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 The concrete recommended architecture Key takeaways Somewhere right now, a scorecard with forty goals is showing all-green because nobody's checked in since March. So the lesson from all of this — a scorecard's the right tool when you need to know who promised what, and what they said when it slipped. That's the correct choice for more teams than you'd expect. Resources Get started with goals Deprecation of Metric Sets in Power BI Fabric Community updates blog Create scorecards Scorecard subscriptions Create subgoals Hierarchies in scorecards Create connected goals in Power BI Stay on top of your goals (check-ins) Create automated status rules for goals Protect your scorecards with goal-level permissions Create linked goals in the Power BI service (preview) Refresh goals and scorecards automatically Use Power Automate to update goals automatically Use Power BI metrics to track goals in Microsoft Teams 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.

    The Database Hiding Inside Your Scorecard — Fabric Scorecards

  7. Jul 24

    One Expression Halves Your Data Ceiling — Paginated Reports

    One Expression Halves Your Data Ceiling Episode 30 • 2026-07-24 Duration: 10:13 Paginated reports carry no data model, and that one design decision explains every limit teams hit in production. This episode traces the consequences from silent data drops to a tenant-wide security door that only opens one way, and lands on the question that makes the tool choice for you. 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 Where the obvious answer breaks 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 And a Diagnostics button nobody's pressed is sitting there, ready to explain why. Somewhere right now, a Monday-morning subscription is carrying a Weekday expression nobody remembers, heading for a ceiling that used to be a slope and is now a cliff. Show me the query pattern. If the aggregation's in the right place, the report scales. If it isn't, no capacity tier saves you. That's the decision that actually matters. Resources What are paginated reports in Power BI? When to use paginated reports Paginated reports in the Power BI service Performance and scalability FAQ Paginated Report definition Access the paginated report editor SQL Server Reporting Services (Wikipedia) RDL Schema Specification Plan to migrate .rdl reports Supported data sources Connect via Power Query Create and use the paginated report visual Email subscriptions Export Power BI paginated reports 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.

    One Expression Halves Your Data Ceiling — Paginated Reports

  8. Jul 17

    The Dashboard That Can't Filter — Power BI Dashboards

    The Dashboard That Can't Filter Episode 29 • 2026-07-17 Duration: 9:51 A Power BI dashboard can show tiles from six different semantic models. It cannot filter a single one of them. We explain why the architecture makes that tradeoff inevitable, and what it means for choosing between dashboards and reports. 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 Where the obvious answer breaks 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 Both problems solve the moment you understand what you pinned. Somewhere right now, someone's pinning a tile and wondering where the slicer went. Show me the query pattern. If the pattern is 'monitor five numbers from five models,' the dashboard's exactly right. If the pattern is 'explore, filter, drill,' you wanted a report from the start. Resources Introduction to dashboards for Power BI designers Compare Report Server and the Power BI service Introduction to dashboard tiles Pin Reporting Services items to Power BI dashboards Pin an entire report page as a live tile Reports in Power BI Create a Real-Time Dashboard What is Fabric Embed (preview) Conduct proof of concept to migrate to Power BI mobile-apps-view-dashboard service-dashboard-pin-tile-from-excel service-pin-tile-to-another-dashboard Dashboards for business users Create a Power BI dashboard from a report, Considerations and limitations Create or edit a dashboard tile 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.

    The Dashboard That Can't Filter — Power BI Dashboards
See All (37)

Trailer

About

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

Information