Forum Discussion
Session issue while generating a paginated reports on Power BI Service using Edge browser
Hello,
Since last Microsoft Edge update (in december 2025), No one in my team is able to generate/look at a paginated report (built using Power BI Report Builder) in Power BI service using Edge browser.
When accessing the Paginated report on Power Bi Service we're getting this error:
There was an error when attempting to create a new session
Could not connect to the server. Please check your network settings and try again later.
If you contact support, please provide these details
Timestamp (UTC)2026-01-08T16:03:13.308Z
Session ID
Viewer version2025.12.3.1971
The workaround we found is to connect to Power BI Service using the Microsoft Teams Power BI App instead of Microsoft Edge.
It's a premium workspace and there's no issue with how the reports are shared with people as they are able to access/generate those reports via the Teams App.
Anyone getting the same issue ? and if yes were you able to find a permanent fix ?
Thank you !
Yes, others are seeing the same issue. This started after the December 2025 Edge update and only affects paginated reports opened in Power BI Service using Edge. It is not related to Premium capacity, permissions, or the report itself. The fact that it works in the Power BI Teams app confirms this.
There is no permanent fix on the Power BI side right now. Current workarounds are:
Open paginated reports via the Power BI app in Microsoft Teams
Use another browser (Chrome or Firefox)
In Edge, try InPrivate mode, allow third-party cookies, or disable “Enhance security on the web” (works for some, not all)
Re-publishing reports or refreshing datasets does not fix it.
please mark it as an accepted solution.Hi TheophileB59
Yes, this is a known Edge-only regression that started with the December 2025 Edge (Chromium) update — it breaks the WebSocket / iframe session that paginated reports use to spin up the report execution session in the Power BI Service, which is why you see “Could not connect to the server – failed to create a new session”. The reason it works in the Teams Power BI app is that Teams uses a different embedded WebView that isn’t affected by the Edge networking change. It has nothing to do with Premium, permissions, or the report itself. At the moment there is no tenant-side fix; the only real workarounds are use Chrome, use the Teams app, or roll back / wait for a patched Edge build from Microsoft — and Microsoft has already acknowledged this as a browser bug impacting Power BI paginated reports.
3 Replies
Yes, others are seeing the same issue. This started after the December 2025 Edge update and only affects paginated reports opened in Power BI Service using Edge. It is not related to Premium capacity, permissions, or the report itself. The fact that it works in the Power BI Teams app confirms this.
There is no permanent fix on the Power BI side right now. Current workarounds are:
Open paginated reports via the Power BI app in Microsoft Teams
Use another browser (Chrome or Firefox)
In Edge, try InPrivate mode, allow third-party cookies, or disable “Enhance security on the web” (works for some, not all)
Re-publishing reports or refreshing datasets does not fix it.
please mark it as an accepted solution.Hi TheophileB59
Yes, this is a known Edge-only regression that started with the December 2025 Edge (Chromium) update — it breaks the WebSocket / iframe session that paginated reports use to spin up the report execution session in the Power BI Service, which is why you see “Could not connect to the server – failed to create a new session”. The reason it works in the Teams Power BI app is that Teams uses a different embedded WebView that isn’t affected by the Edge networking change. It has nothing to do with Premium, permissions, or the report itself. At the moment there is no tenant-side fix; the only real workarounds are use Chrome, use the Teams app, or roll back / wait for a patched Edge build from Microsoft — and Microsoft has already acknowledged this as a browser bug impacting Power BI paginated reports.
Could you try the following steps below:
Edge → Settings
Privacy, search, and services
Tracking prevention → Balanced (not Strict)
Allow third-party cookies (temporarily)
Disable “Block trackers in all windows”
