Fabric capacity, attributed to the workspace that burned it.
CloudMonitor turns capacity-unit (CU) consumption into cost per workspace, item, and team, so the Microsoft Fabric capacity that powers your analytics is governed like the rest of your estate.
Microsoft Fabric bills as a shared capacity, and a single noisy notebook or dataflow can burn through capacity units that everyone else then waits on. CloudMonitor attributes CU consumption to the workspace, item, and team behind it, so smoothing, bursting, and throttling become decisions someone owns rather than a capacity nobody can explain.
- Attributes capacity-unit (CU) consumption to workspaces, items, and teams.
- Surfaces the heaviest items and the workspaces driving burst and throttling.
- Tracks capacity utilization against what you pay for, reserved or pay-as-you-go.
- Reports alongside your Azure spend in one allocation model.
Capacity attribution
Tie CU consumption to the item behind it.
CloudMonitor maps capacity-unit usage to the workspaces and items that generated it, so a spike points to a specific notebook, pipeline, or semantic model rather than a shared capacity total nobody owns.
- Per-workspace and per-item CU attribution
- Burst and throttling traced to the heaviest workloads
- Reconciled against the rest of your Azure estate
Capacity right-sizing
Pay for the capacity you actually use.
CloudMonitor tracks utilization against your reserved or pay-as-you-go capacity, so you can right-size the SKU, schedule capacity, and decide when smoothing is hiding a real problem.
- Utilization versus paid capacity, over time
- Reserved versus pay-as-you-go modeled together
- Ranked by saving, the largest opportunity first
CloudMonitor runs on Microsoft Fabric, so monitoring Fabric’s own capacity is a natural fit. The connector turns capacity-unit consumption into cost per workspace, item, and team, so the platform that powers your analytics is governed with the same discipline as everything else.
A dedicated Microsoft Fabric page is on the way. If Fabric capacity is a growing line in your bill, the beta team would like to know which workspaces and item types you most need attributed.
More data platforms
Other integrations like this.
Govern Microsoft Fabric spend on real data.
The beta runs against your own tenant: your spend, your allocation, your alerts.
