Fabric now charges triple for extra compute instead of slowing reports
Reviewed by Helen Jones
Microsoft has made capacity overage generally available on Fabric F SKUs. On newly created capacities it is on by default. When demand briefly exceeds the purchased SKU, Fabric can keep work running instead of throttling it. Eligible extra usage is billed at three times the pay-as-you-go rate, up to a rolling 24-hour CU-hour spending threshold set by the capacity admin. That threshold is not a hard cap. Jobs already running can keep going, so charges can overshoot the number on the screen. After the window is spent, normal throttling returns.
Until now, a heavy refresh or a busy dashboard hour usually announced itself. Visuals lagged, scheduled refresh failed, and someone asked why the pack was late. The pain sat with the report owner, not with a line item on a capacity bill. The new default trades that delay for a billed continuation. A model that used to fail in the morning can now finish, look healthy, and still cost three times the overflow rate until the 24-hour budget is gone. If you do not own the capacity, you can lose the only signal you had that the report was too heavy, while someone else absorbs the invoice.
Analysis
Treat this as a change to watch, not a reason to ignore refresh design. Before the next monthly pack, ask whoever owns the F SKU whether overage is enabled and what CU-hour threshold they set, then keep a note of it next to your refresh schedule so a quiet success is not mistaken for a cheap one.
Source note
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Fabric now charges triple for extra compute instead of slowing reports", Collab365 Spaces. 2 sources referenced.