Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Join us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.

Reply
JosephMurphy
New Member

Power BI Embedded capacity optimisation for concurrent users

Hi,

We have created a power bi report which works fine in Desktop. However, as soon as we embed this using PowerBI embedded and do some load testing with 5 concurrent users, the report stops working (visual don't load, spinning bar). This occurs after a couple of minutes of all 5 users trying to quickly apply slicers at the same time. 

Please could someone advise on best practice for embedded configuration or if others have had a similar issue? 

 

Cheers

Joe

 

1 ACCEPTED SOLUTION
tancha
New Member

The issue you're encountering with Power BI Embedded where reports stop loading and show a spinning bar after multiple users interact with slicers could be due to performance bottlenecks, especially when handling concurrent user requests. Here are a few best practices to improve performance for embedded reports:

  1. Optimize your Power BI model: Ensure the data model is optimized. Large or complex models may slow down when multiple users interact with them.

  2. Consider direct query mode: Instead of using import mode, you could use DirectQuery to reduce the load on the Power BI report server by querying the data source in real time.

  3. Limit visuals and slicers: Too many visuals or slicers can strain the report's performance. Reducing the number or optimizing visuals may help.

  4. Use Azure capacity for embedded reports: Make sure you are using an appropriate Azure Embedded Capacity SKU, as this can significantly improve performance under load.

For detailed guidance, refer to the article here: Power BI Best Practices 

View solution in original post

5 REPLIES 5
v-prasare
Community Support
Community Support

Hi @JosephMurphy

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

 

 

 

Thanks,

Prashanth Are

MS Fabric community support

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

v-prasare
Community Support
Community Support

Hi @JosephMurphy,

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

 

 

 

Thanks,

Prashanth Are

MS Fabric community support

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

v-prasare
Community Support
Community Support

Hi @JosephMurphy

As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for your issue worked? or let us know if you need any further assistance here?

 

 

 

Thanks,

Prashanth Are

MS Fabric community support

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly and give Kudos if helped you resolve your query

JosephMurphy
New Member

JosephMurphy_0-1743515867354.png

SKU F2. Is this is the correct configuration for the report I am embedding? Would Premium resolve the issue of concurrent users?

tancha
New Member

The issue you're encountering with Power BI Embedded where reports stop loading and show a spinning bar after multiple users interact with slicers could be due to performance bottlenecks, especially when handling concurrent user requests. Here are a few best practices to improve performance for embedded reports:

  1. Optimize your Power BI model: Ensure the data model is optimized. Large or complex models may slow down when multiple users interact with them.

  2. Consider direct query mode: Instead of using import mode, you could use DirectQuery to reduce the load on the Power BI report server by querying the data source in real time.

  3. Limit visuals and slicers: Too many visuals or slicers can strain the report's performance. Reducing the number or optimizing visuals may help.

  4. Use Azure capacity for embedded reports: Make sure you are using an appropriate Azure Embedded Capacity SKU, as this can significantly improve performance under load.

For detailed guidance, refer to the article here: Power BI Best Practices 

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.

June 2025 Power BI Update Carousel

Power BI Monthly Update - June 2025

Check out the June 2025 Power BI update to learn about new features.

June 2025 community update carousel

Fabric Community Update - June 2025

Find out what's new and trending in the Fabric community.