PowerBI on Fabric get stuck

Hi Anonymous 

After migrating from Power BI Premium to F64 Fabric capacity, we’ve encountered significant issues with capacity utilization and governance. One major concern is that a single user can monopolize over 200% of the entire capacity, effectively starving all other users of resources. During such episodes, report usage across the organization becomes unresponsive, causing widespread disruption. Compounding the issue, Fabric currently lacks a built-in session management mechanism—there is no way to view, monitor, or terminate active user sessions. This leaves administrators powerless to reclaim capacity or take immediate corrective action.

What’s more troubling is the lack of transparent session logs or diagnostics to help pinpoint the exact report or query causing the overload. This is unlike other enterprise-grade platforms where session-level monitoring and control are considered standard. Microsoft’s current workaround—suggesting admins manually identify heavy datasets or reassign users to other capacities—is inefficient, reactive, and operationally impractical, especially in dynamic and large-scale environments. Overall, this gap in Fabric’s capacity governance undermines its promise as an enterprise-grade solution and urgently needs attention to support real-world production workloads effectively.

 

Hi Anonymous

 

• After moving to Fabric F64, one heavy user can eat >200% capacity and block others there’s no session log or kill switch, so troubleshooting is tough.
• Microsoft’s advice (reassign datasets / revoke access) is a temporary band-aid, not scalable.
• Near term: isolate high-load workspaces on their own capacity and tighten model/query optimization plus report usage limits.
• Long term: push for proper admin tools session visibility and control should be standard.

Hi Anonymous ,

Thank you for reaching out to the Microsoft Community Forum.

 

Please check below things to fix the issue.

 

1. Use the Fabric Capacity Metrics App, which provides Compute View (tracks Capacity Unit utilization across workloads and users). Storage View (Monitors lakehouse and KQL database usage). Throttling Events (Identifies operations causing capacity overloads).

 

Note: This app helps admins which users or workloads are consuming excessive resources and plan corrective actions.

2. Assign high-demand workspaces to separate capacities. Use incremental refresh to reduce memory spikes. Prioritize datasets based on size and refresh frequency.

 

3. Even small datasets (~6GB) can trigger memory errors due to temporary spikes during refresh. The 25GB limit for F64 is misleading because only 50% is available for refresh operations.

 

4. Microsoft recommends three strategies when facing throttling, Optimize (Use incremental refresh, reduce dataset complexity). Scale Up (Move to higher capacity SKUs). Scale Out (Distribute workloads across multiple capacities).

 

Please refer below Microsoft document and community thread.

Evaluate and optimize your Microsoft Fabric capacity - Microsoft Fabric | Microsoft Learn

Solved: Re: Fabric F64 gives an out of memory error on res... - Microsoft Fabric Community

 

If this information is helpful, please “Accept it as a solution” and give a "kudos" to assist other community members in resolving similar issues more efficiently.

Regards,

Dinesh