Performance considerations pulling from a P1 Premium Capacity to a Power BI Pro Workspace

Hi YuenKelly 

Even if the report runs from a Pro workspace, pulling data from a Premium dataset still consumes resources on the Premium side. This includes XMLA reads, DAX queries, or live connections—all of which use Premium's CU.

To reduce the load:

 

• Review external tools hitting the dataset (e.g., Excel, Power BI Desktop, XMLA endpoints)

• Consider restricting access to heavy users

• Optimize large queries or refresh patterns where possible

Hi YuenKelly,

Thank you for reaching out to the Microsoft Fabric Community Forum.

 

Thank you, rohit1991, for your valuable input regarding the issue. I agree with the solution shared by the Super user.

 

After reviewing the details you provided, here are a few workarounds that may help resolve the issue. Please follow these steps:

 

Yes, extracting data from datasets in a premium capacity within a pro workspace can lead to capacity unit (CU) spikes in Microsoft Fabric. This is due to tasks that require substantial CU loads, which can cause spikes in CU usage, particularly during peak reporting periods. particularly if multiple interactive XMLA read operations are running simultaneously.

 

• If Pro users are running complex queries, consider pre-aggregating data to reduce processing load, optimizing DAX calculations for efficiency, and using Hybrid Tables (Import + Direct Query) to offload query processing.
• If Pro workspaces frequently access datasets in Premium, consider moving them to Premium Capacity to ensure efficient resource usage. Navigate to Power BI Admin Portal → Workspaces → Assign to Premium Per User (PPU) or Premium Capacity.
• If external tools (e.g., Excel, SSMS) are triggering XMLA queries, consider limiting XMLA Read access to reduce CU consumption.
• If CU consumption remains high, consider scaling up to a higher Premium capacity (e.g., P2), balancing workloads across multiple capacities, and monitoring capacity usage to limit non-critical workloads.

Please go through the below following links for better understanding:

Capacity and SKUs in Power BI embedded analytics - Power BI | Microsoft Learn
Understand your Fabric capacity throttling - Microsoft Fabric | Microsoft Learn

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

 

Best Regards.