Forum Discussion
Best Practices for Assigning Different Workspaces to Different Fabric Capacities
I am currently setting up Microsoft Fabric in our organization and would like to clarify the best approach for assigning different capacities to different workspaces.
- Is it possible to assign different workspaces to different Fabric capacities within the same tenant?
example F2 Dev F8 Prod workspace. - What are the best practices for managing this setup efficiently?
- How does capacity switching impact workspace performance and governance?
- Are there automation options for capacity assignment (via APIs or PowerShell)?
Hi Amiral
Great question.
This is how most of the organisations working with Fabric has setup capacities.
You can assign different workspaces to different Microsoft Fabric capacities within the same tenant, such as assigning a Dev workspace to an F2 capacity and a Production workspace to an F8 capacity. Each capacity is its own pool of resources that determines how much compute power is available to the workspaces it hosts.
Best Practices for Management
• Separate Environments: Use smaller capacities (for example, F2) for development or testing, and larger ones (like F8) for production to keep workloads isolated and prevent competition for resources.
• Monitor Usage: Track resource consumption and potential overload by using Fabric capacity monitoring tools. If you see recurring heavy usage, consider scaling up, scaling out, or optimizing contentWorkspace Assignments: Moving a workspace between capacities cancels running jobs in that workspace. Plan migrations carefully and choose capacity SKUs that match performance and concurrency needs
This is great blog to learn about Capacity migration:
You can use Semantic Link Labs for automation.A very good video is in the blog itself.
Please note, that if your workspaces contain Fabric artifacts, they cannot be reassigned to capacities located in a different geography.
Please accept this answer if this is helpful
Thanks
2 Replies
Hi Amiral
Great question.
This is how most of the organisations working with Fabric has setup capacities.
You can assign different workspaces to different Microsoft Fabric capacities within the same tenant, such as assigning a Dev workspace to an F2 capacity and a Production workspace to an F8 capacity. Each capacity is its own pool of resources that determines how much compute power is available to the workspaces it hosts.
Best Practices for Management
• Separate Environments: Use smaller capacities (for example, F2) for development or testing, and larger ones (like F8) for production to keep workloads isolated and prevent competition for resources.
• Monitor Usage: Track resource consumption and potential overload by using Fabric capacity monitoring tools. If you see recurring heavy usage, consider scaling up, scaling out, or optimizing contentWorkspace Assignments: Moving a workspace between capacities cancels running jobs in that workspace. Plan migrations carefully and choose capacity SKUs that match performance and concurrency needs
This is great blog to learn about Capacity migration:
You can use Semantic Link Labs for automation.A very good video is in the blog itself.
Please note, that if your workspaces contain Fabric artifacts, they cannot be reassigned to capacities located in a different geography.
Please accept this answer if this is helpful
Thanks
Thanks for the best practices, i am managing different teams, and as a first step i am thinking of placing the dev environment in a large capacity and then splitting/ isolating prod environment in its own capacity. Then i will keep an eye on the capacity usage in the dev + prod environment, and thinking of assigning dev workspaces to the prod capacity, if i see that the dev can fit under the prod capacity then i would move it, if not i can always upscale my prod capacity to fit the dev and prod capacity later. Do you think that is a good practice? Thanks in advance
