top of page

Fabric Workspace Architecture Patterns

The way you organize workspaces in Microsoft Fabric influences everything that follows: who can access information, how you manage capacity costs, the complexity of your deployments, and the ease with which teams can work independently without interfering with one another. 

 

There is no single "correct" topology; the right choice depends on your team size, governance requirements, and the number of distinct groups that need to consume the data. What works for a small central team may not scale effectively for a large enterprise with multiple domains and various consuming teams.

 

This guide presents workspace topology patterns, ranging from the simplest to the most distributed. Each pattern includes trade-offs and example scenarios to help you determine which one best suits your situation.

Starter Topology

Single workspace, folder separation

Small teams, simple governance, getting started quickly

Split Topology

Separate DE and DA workspaces

Clear ownership boundaries, capacity or access separation

Hub and Spoke Topology

One DE workspace, multiple DA workspaces

Central platform team serving multiple consuming teams

Domain Mesh Topology

Each domain owns its own topology

Enterprise scale, federated ownership, data mesh alignment

bottom of page