Organisations using Power BI / Fabric Capacities must carefully monitor and manage usage of these capacities.

When capacities are not managed properly, performance can be reduced, and ultimately, users will receive error messages stating that limits have been reached until the "overuse" has been repaid.

As Power BI capacities become Fabric capacities, managing this properly needs even greater focus.

This session will outline:
- The importance of managing Fabric capacities and what can go wrong
- Using the Fabric Capacity Metrics App
- Best practices on setting notifications for capacities
- Different throttling scenarios, and the action you might take in each scenario (for example, identifying a page of a report which might be problematic and hiding it until it can be improved, or temporarily re-allocating cores from one capacity to another if the organisation has >1)
- Guidance on using Autoscale
- A real life example of a capacity migration used to re-balance content across two capacities
- What Fabric developers should be thinking about when using capacities - to safeguard performance and cost for everyone else.