cancel
Showing results for 
Search instead for 
Did you mean: 

Web Interface performance problems when screen-sharing in Teams

The performance of screen rendering, data refreshing, slicer updates, etc. drops considerably if/when you start a screen-sharing session in a Teams meeting.  This is specific to PowerBI in the browser, as other applications/services continue functioning normally.  

Status: New
Comments
Ivancbarriga
Frequent Visitor

Latency has been increased when performing web browsing actions. Specifically when selecting a value from a filter, or when sorting columns in an array in the web version. The Desktop -Local- version does not present this delay.

v-qiuyu-msft
Community Support

Hi all, 

 

I would suggest you follow this document to troubleshoot the issue: https://docs.microsoft.com/en-us/power-bi/guidance/power-bi-optimization

 

If the issue still occurs, I would suggest you create a support ticket to get help. 

Support Ticket.gif

 

Best Regards,
Qiuyun Yu

KimberlyS
Regular Visitor

This is not an issue with optimization of the reports themselves.  Reports that work just fine in the service for individual viewers will have terrible latency when they are being screen shared on Teams.

BillColeman
Frequent Visitor

Confirming same issue. Reports run fine until being shared over a Teams meeting - for some reason sharing the screen slows the report down considerably. Only affects reports when screen sharing on Teams, i.e. not a general performance problem.

kelseypbi
Advocate I

Agreed.  This didn't seem to be an issue last year - I went on leave in Sept and when I came back in January it was an issue.

pclark7874
New Member

This issue is very prevalent in our environment as well. Anything that requires a visualization to refresh is at minimum 2x slower when sharing in MS Teams than if not.

 

I have found that if I share just the application (i.e. Chrome) that the performance is better. If I am sharing my actual screen it is almost unusable.

JRHans09
Resolver I

I agree. This is not a report optimization issue. Visualization refresh rates are drastically different when presenting inside of a Teams shared session.  Please investigate this issue and provide a workable solution, as it is currently impossible to present in this way.