Forum Discussion
Helper IVReserved Fabric Pricing
Hi AJAJ ,
You’re correct that a single reserved capacity (e.g., F10) can be shared across multiple workspaces. Fabric allows workspaces to use the full capacity if others are idle, so Prod and Dev can dynamically consume available compute. Currently, there is no built-in setting to strictly cap a workspace (e.g., Dev at F4) only when both are running. For more control, you can create separate capacities for guaranteed allocation. To monitor and manage usage, go to Admin Portal next Capacity next Metrics to view consumption per workspace, and use Workspaces then Edit then Capacity to assign or reassign capacities as needed. This allows you to track usage and optimize workload distribution even within shared capacity.
Super UserEither yourself or somebody with high-enough permissions can purchase the capacity themselves in the Azure Portal:
Save costs with Microsoft Fabric Capacity reservations - Microsoft Cost Management | Microsoft Learn
In addition to the Microsoft articles about it various community members such as Marc Lelijveld also cover it in detail:
Purchasing Fabric Capacities as Reserved Instance – Data – Marc
I hope this helps.