Forum Discussion
Post PatronWorkspaces and Domains Vs Workspaces and Capacities
Dears,
If I am not wrong, domains can have one or more workspaces attributed to it. Meaning, if we think on a domain like Sales, we can have one or more workspaces attributed (bounded to it). And what is the relatioship of the domains with capacities? Can we correlate domains with capacities? or capacities can also only be correlated with workspaces?
Example, if I have only one workspace can I add that workspace to multiple different domains?
Your understanding is right: a domain like Sales can hold one or many workspaces, and each workspace belongs to at most one domain at a time.
For your second question: domains and capacities have no direct relationship — both attach at the workspace level only. Capacity is where a workspace's compute and billing live; domain is the logical business grouping. So a Sales domain can span workspaces on several capacities, and one capacity can host workspaces from many domains.
There is one touchpoint: on the domain page, Assign workspaces → Assign by capacity assigns every workspace currently sitting on the selected capacities to the domain — useful if you run dedicated capacities per department. Note it's a one-time action: workspaces added to that capacity later won't inherit the domain.
So if you want Sales capacity and Sales domain to stay aligned 1:1, treat it as a convention: set a default domain on the department's security group (that part is automatic for new workspaces) and re-run Assign by capacity occasionally to catch drift.
More detail: https://learn.microsoft.com/en-us/fabric/governance/domains
🔍Parchitect
Solutions Architect · Microsoft Fabric Specialist
💡Helpful? Kudos are appreciated.
✔️Solved? Mark as Solution so others can find it faster.
1 Reply
- Parchitect
Solution Sage
Your understanding is right: a domain like Sales can hold one or many workspaces, and each workspace belongs to at most one domain at a time.
For your second question: domains and capacities have no direct relationship — both attach at the workspace level only. Capacity is where a workspace's compute and billing live; domain is the logical business grouping. So a Sales domain can span workspaces on several capacities, and one capacity can host workspaces from many domains.
There is one touchpoint: on the domain page, Assign workspaces → Assign by capacity assigns every workspace currently sitting on the selected capacities to the domain — useful if you run dedicated capacities per department. Note it's a one-time action: workspaces added to that capacity later won't inherit the domain.
So if you want Sales capacity and Sales domain to stay aligned 1:1, treat it as a convention: set a default domain on the department's security group (that part is automatic for new workspaces) and re-run Assign by capacity occasionally to catch drift.
More detail: https://learn.microsoft.com/en-us/fabric/governance/domains
🔍Parchitect
Solutions Architect · Microsoft Fabric Specialist
💡Helpful? Kudos are appreciated.
✔️Solved? Mark as Solution so others can find it faster.