Microsoft Fabric cost
See what your Microsoft Fabric capacity costs.
CloudMonitor reads Fabric capacity charges from your Azure FOCUS export and shows them beside the rest of your Azure spend. CU attribution and throttling appear only in the sample-data demo until a production Fabric telemetry feed is connected.
Sample-data preview
Fabric chargeback in CloudMonitor.
The screen at right uses sample CU data. Capacity cost from the Azure FOCUS export is live today; CU, throttling, and workload allocation are not connected yet.
From bill to root cause
Check the workload before you change the SKU.
CloudMonitor shows the billed and effective cost of your Fabric capacity. When that charge changes or the capacity slows, Microsoft’s Capacity Metrics app supplies the operational evidence.
-
Start with Health.
Find the capacities consuming the most compute or showing throttling and query rejections. Compare the last hour with the last 24 hours.
-
Open Compute.
Review 14 days of CU demand, peak loads, and throttling. The app separates interactive demand from background work.
-
Pick a timepoint.
Drill into a 30-second interval around an overload to see which item, operation, or user contributed to CU usage.
-
Check Storage.
Review 30 days of current and billable storage by workspace, including soft-deleted data that still incurs storage charges.
FAQ
Fabric monitoring questions
What Microsoft Fabric data is live in CloudMonitor today?
CloudMonitor reads capacity-level Fabric F SKU charges from your Azure FOCUS export. It shows billed and effective cost, period trends, and the same reporting context as the rest of your Azure services.
Does CloudMonitor track CU consumption and throttling?
The CloudMonitor demo includes a sample-data preview of CU usage, throttling, and workload allocation. Those views are not connected to a production Fabric telemetry feed yet. For CU analysis today, use Microsoft's Fabric Capacity Metrics app.
Can CloudMonitor break Fabric capacity cost down by workspace and team?
Not from live data yet. Capacity-level spend is live; CU-based workspace, item, domain, and user allocation is a preview capability. Microsoft's Fabric Chargeback app provides that CU breakdown today.
How is CloudMonitor different from Microsoft's Fabric apps?
CloudMonitor puts the Fabric capacity charge into your wider Azure cost view. The Fabric Capacity Metrics app provides detailed capacity health and performance telemetry, while the Fabric Chargeback app attributes CU consumption to workspaces, items, domains, and users. They are complementary views.
What does setup involve?
CloudMonitor onboarding usually takes a couple of hours, depending on how quickly your team provisions and authorizes the service principal and FOCUS export. CloudMonitor uses scoped, least-privilege access, deploys no compute into your capacity, and never changes your Fabric workloads.
See your Fabric capacity in CloudMonitor.
Connect your Azure billing and bring the real Fabric capacity charge into the same governed reports.