Fabric Governance - Domains, Workspaces & Lineage

🎯 The Problem: Your Fabric POC was a success. Now 15 teams want in. Suddenly you have 47 workspaces, no naming convention, random data everywhere, and the CFO asking why the capacity bill tripled.

💡 This Evening: We’ll show you governance patterns that ENABLE teams (not block them). Domains, Workspaces, Capacities, Lineage - the structure that scales.

⏱️ Save yourself: The governance mess that makes everyone hate the data platform. Get it right from the start.

What you’ll learn

#

• 📁 Workspace Design Patterns – Dev/Test/Prod, medallion, team-based structures, and WHY workspace design impacts everything
• 🏛️ Domains – Data Mesh principles in Fabric, and WHY domains enable decentralized ownership
• ⚡ Capacity Management – CU consumption, smoothing, bursting, and WHY capacity planning prevents budget surprises
• 🔍 Data Lineage – Impact analysis and dependency tracking, and WHY lineage is non-negotiable for compliance

Governance Hierarchy

#

Tenant → Domain (Sales, Finance, HR) → Workspace (Dev, Test, Prod) → Items (Lakehouse, Reports) → Data (Tables, Files)

Agenda

#

Who should attend

#

Fabric administrators, Enterprise architects, Compliance and security teams.

📚 Featured Resources

#

📥 Handout (PDF, 99 pages)

#

Fabric Governance: Domains, Workspaces & Lineage (handout) – All 70 slides of the evening with clickable links (each demo replaced by its poster frame and a link to the exact moment in the episode), the appendix «All scenes» with every diagram the talk skipped, and the three cheat sheets as A4 pages.

📋 Cheat sheets

#

• On the slides: Workspace (pages 20–21) · Domain (pages 41–42) · Capacity (pages 61–62, with the throttling staircase)
• Full A4 cheat sheets: Workspace (pages 85–89) · Domain (pages 90–94) · Capacity (pages 95–99)

🎬 The Fabric Friday episodes behind tonight

#

📁 Workspace

#

• Episode: Fabric Workspace Roles, OneLake Security and Capacity Explained
• Short: Why OneLake security can’t fence in a Contributor
• Architecture in Minutes (one film per diagram):
  • What a Fabric Workspace Really Is: Four Boundaries in One Object
  • The Viewer Line: One Table, Two Routes (public from Tue 13 Oct, 09:00 CEST)
  • Why OneLake Security Cannot Fence In a Contributor (premieres Wed 14 Oct, 09:00 CEST)
  • Who Can Claim Your Workspace (premieres Thu 15 Oct, 09:00 CEST)

🏛️ Domain

#

• Episode: Microsoft Fabric Domains Explained: Roles, Default Domain, Labels
• Short: A domain is a label, not a lock

⚡ Capacity

#

• Episode: Capacity Deep Dive: Your Bill and Your Outage Are Not the Same Moment (premieres Fri 16 Oct, 09:00 CEST)
• Short: The spike is a receipt (premieres Sun 18 Oct, 09:00 CEST)

🔍 Lineage

#

Lineage goes deeper in an upcoming Fabric Friday episode. Until then, the two Microsoft Learn pages below cover the difference between the lineage view and impact analysis.

🎞️ Related explainer films

#

Short architecture explainers from the series «What It Means for Your Architecture»:

• Fabric Policies: Who May Create What, Decided per Capacity
• OneLake Outbound Access Protection: Which Way Does Your Data Leave?
• Fabric Capacity Overage: Pay Instead of Throttle, and When Not To
• Fabric Branch Workspaces: One Workspace per Feature, Without the Mess (a preview of the November meetup)

🎧 Fabric Architecture Podcast

#

• The Folder That Carries Four Boundaries: Fabric Workspaces
• The Fence That Isn’t There: Fabric Domains

💬 Questions from the community

#

Real questions asked in public, from the reserve slides (pages 64–68 of the handout):

• Workspace: “Two users can see all data, rather than being restricted by the configured security rules.” Row-level security filters Viewers only; Contributor, Member and Admin bypass it. (Microsoft Q&A: RLS Issue in PowerBI)
• Domain: “Does Domain permissions grant workspace roles?” No. A domain is a governance scope; workspace roles grant access. (Fabric Community: Domain permissions & workspace roles)
• Domain: “If I have only one workspace can I add that workspace to multiple different domains?” No. A workspace belongs to at most one domain: choose, or split the workspace. (Fabric Community: Workspaces and Domains Vs Workspaces and Capacities)
• Capacity: “The throttling counter is increasing the day long for no reason.” Background work is smoothed over 24 hours, so yesterday’s jobs still pay into today. (Fabric Community: Why is there CU usage while no activity running?)
• Capacity: “At 01:00 AM, the capacity should automatically downscale (for example from F64 → F32) since usage is low.” The night still carries smoothed daytime work, and halving the SKU doubles the percentage. (Fabric Community: Support for Time-Based Auto Scaling of Microsoft Fabric Capacity)

📖 Microsoft Learn

#

Workspace

#

1. Workspaces in Microsoft Fabric
2. Roles in workspaces
3. OneLake data access control model

Domain

#

4. Fabric domains

Capacity

#

5. Understand your Fabric capacity throttling
6. Fabric operations (interactive vs. background)
7. Microsoft Fabric Capacity Metrics app

Lineage

#

8. Lineage in Fabric
9. Impact analysis

📅 Next meetups

#

• Tue 10 Nov 2026, 18:30: DevOps for Fabric: Git & Deployment Pipelines
• Tue 8 Dec 2026, 18:30: Fabric Year in Review 2026: Highlights & Outlook
• Join the group on meetup.com: AI and Intelligent Cloud

Part of the monthly Fabric Meetup Series by The Trusted Advisor.