Forum Discussion
Fabric capacity overage feature
Hi Anonymous,
Fabric capacity overage is documented, but the control is not exposed in the admin experience yet. Right now, Fabric relies on burst smoothing and auto scale behavior tied to the SKU. There is no tenant or capacity level switch where an admin enables paid overage on demand.
What exists today
Fabric allows short burst usage within defined limits. Once those limits are crossed, throttling kicks in. Billing stays tied to the provisioned SKU, not transient spikes.
What the SKU page text signals
This reads like a forward-looking capability tied to capacity billing, similar in spirit to Azure consumption buffers. The wording suggests future support for paid overage windows and caps, not a feature already shipped.
Why you cannot locate it
No Fabric Admin portal setting
No Capacity settings blade
No PowerShell or REST surface
No documented preview enrollmentWhat is generally followed instead
Size one SKU tier higher for business hours only
Schedule heavy refresh and Spark workloads off peak
Split read heavy workloads across capacities
Monitor CU usage and throttling patterns aggressivelyThank you!
Proud to be a Super User!
📩 Need more help?
✔️ Don’t forget to Accept as Solution if this guidance worked for you.
💛 Your Like motivates me to keep helping
Super UserHi Anonymous,
Fabric capacity overage is documented, but the control is not exposed in the admin experience yet. Right now, Fabric relies on burst smoothing and auto scale behavior tied to the SKU. There is no tenant or capacity level switch where an admin enables paid overage on demand.
What exists today
Fabric allows short burst usage within defined limits. Once those limits are crossed, throttling kicks in. Billing stays tied to the provisioned SKU, not transient spikes.
What the SKU page text signals
This reads like a forward-looking capability tied to capacity billing, similar in spirit to Azure consumption buffers. The wording suggests future support for paid overage windows and caps, not a feature already shipped.
Why you cannot locate it
No Fabric Admin portal setting
No Capacity settings blade
No PowerShell or REST surface
No documented preview enrollment
What is generally followed instead
Size one SKU tier higher for business hours only
Schedule heavy refresh and Spark workloads off peak
Split read heavy workloads across capacities
Monitor CU usage and throttling patterns aggressively
Thank you!
Proud to be a Super User!
📩 Need more help?
✔️ Don’t forget to Accept as Solution if this guidance worked for you.
💛 Your Like motivates me to keep helping