Fabric and Power BI Embedded Capacity Monitoring
Every report view and refresh in the Embedsy Portal uses compute from your capacity. If the capacity regularly needs more than it has, Microsoft throttles it: report queries are first delayed and then rejected, and your users see slow or failing reports. If it rarely gets busy, you are paying for a size you don't need. Monitoring tells you which of the two applies.
Microsoft's tools and guidance
- Microsoft Fabric Capacity Metrics app: shows how much of the capacity each semantic model, report and refresh uses, when it peaks and whether it is throttled. It covers Fabric (F), Power BI Embedded (A) and Premium (P, EM) capacities. A capacity admin installs it once from AppSource.
- The Fabric throttling policy: how usage is smoothed over time, when throttling starts and how to stop it.
- Evaluate and optimize your Microsoft Fabric capacity: sizing, monitoring and reducing consumption.
Pausing settles the smoothed usage. When a capacity is paused, usage that Fabric had spread over the coming hours is added to your Azure bill at once. If the portal pauses an overloaded capacity, that cost shows up at the pause (Pause and resume your Fabric capacity).
How we can help
If your capacity is throttling or costs more than it should, our capacity optimization service finds out which models, queries and refreshes use it and fixes them, so you can often stay on a smaller SKU. We don't sell capacity, so a bigger SKU earns us nothing.