Microsoft Fabric capacity overage lets work keep running when it goes past the size of your capacity, instead of being slowed down. It's on by default when you create a capacity. It's useful for an occasional spike that would otherwise throttle reports.
It also has a cost: Microsoft bills the extra usage at three times the pay-as-you-go rate, and only for the usage above your capacity.
You can set an overage threshold. Microsoft's own documentation says that threshold isn't a hard spending cap, so treat it as a guardrail, not a guarantee.
A five-minute check:
- In the Fabric admin portal, open your capacity settings and find Capacity overage (capacity admins only).
- Decide whether you want overage at all. Some teams prefer a slowdown to a surprise.
- If you keep it on, set a threshold that matches your budget.
- Add an Azure Cost Management budget with an alert to the people who own the bill.
If capacity regularly runs over, the cheaper answer is usually a right-sized capacity or better-scheduled workloads, not paying three times the rate.
