Forum Discussion
Reserved Fabric Pricing
- Anonymous10 months ago
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.
Hi AJAJ ,
The reason you’re not seeing the reserved option is that it’s not managed in the Fabric admin portal. Reserved Fabric capacity is purchased through the Azure Portal under Cost Management - Reservations, and it appears only if your account has billing permissions like Owner, Contributor, or Billing Account Contributor. Once the reservation is bought, it’s automatically applied to your Fabric workloads, and you can check or reassign it in Capacity settings in the Fabric admin portal. Regarding workspaces, you can run several workspaces on a single reserved capacity and assign them by going to Admin Portal - Workspaces - Edit - Capacity. With this information and what’s already been shared, you should be set to move from pay-as-you-go to reserved capacity.
Thank you for your reply. I will explore that and circle back.Since im a subscription admin as well. I think im a billing contributor. let me check.
Regarding capacity shared by worksspace. If I understand, i can buy F10 (for example), assign F6 for prod workspace and F4 for Dev workspace by going into Workspace capacity? is that how the compute math works?
or F10 compute can be shared whoever has the workload. If prod is quite, dev can use full F10. if dev is quite prod can use full f10. when both are doing some heavy compute, is there a way to cap dev at F4? remember capping only if both are running else they should use full compute available. Any setting like that?
- lbendlin10 months ago
Super User
Fabric SKUs come in powers of 2. F2, F4, F8, F16 etc. So no F6, and no F10, but you could have a F4 and a F8. Note that these are tiny and will most likely need to be upgraded for actual production scenarios.
- Anonymous10 months agoNot applicable
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.