Power BI Service - More than 1 Microsoft custom visual not displayed in service when using MS Edge

Dear all,

I am experiencing an issue with displaying multiple Microsoft owned and/or certified custom visuals in one page of a report published to the Power BI service. In contrast to displaying all the visuals correctly in the pages in Power BI Desktopclient, the same page displayed in the published report only shows one visual. The issue occurs with browser MS Edge.

Please consider the following screenshot comparing display of page in service (left) and client (right):

The issue occurs with the internet browser MS Edge, which is our corporate standard. The business impact hence is, that we currently cannot use multiple custom visuals in one page of any corporate report.

Following observations have been made:

• The issue only seems to occur with MS Edge, in Chrome or even in MS Teams, the pages are displayed correctly, and all custom visuals are loaded. However, standard browser is MS Edge, and using alternate browsers is not an option.
• In MS Edge the missing visual can be displayed by refreshing the respective frame via right click context menu, however, upon refresh of the entire page or navigating to another page of the same report the visual disappears again. This is no option either.
• In MS Edge when accessing the same report in the service whith private mode the visual loads correctly. Again, not a reasonable workaround.

Following versions are used:

Power BI Service 13.0.22589.88
Microsoft Edge 121.0.2277.106
Visuals used in report (for example) Word Cloud 2.2.0.0, Timeline 2.4.0, Gantt 2.2.3 (all MS certified/owned visuals from Power BI store)
From web research I found some other cases where no custom visual was displayed in Power BI service, however, I didn't find any case, where only the "first" visual is loaded and no additional.

What we've currently assessed are interdependencies with any browser extension in use and browser policies. However deactivating any extension and currently also going through the individual browser policies hasn't yet brought any insights, except for that the one browser extension we have in use doesn't seem to be the root cause, as issue persists after deactivation.

Did anybody experience a similar issue or has some ideas how to proceed?

Thank you and kind regards,
Petter