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.
Helper IVThank 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?
Super UserFabric 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.