Forum Discussion
Power BI RS January 2026 – Reports Using RLS Enter Infinite Reload Loop
Hello mrusu,
If a report in Power BI Report Server uses Row-Level Security (RLS) and a user is not assigned to any role, the user cannot access the dataset because no RLS filter context can be applied.
In previous builds this typically returned an access error. In the January 2026 release (15.0.1120.122), it appears the UI may enter a reload/spinning loop instead of showing the error when a user has no RLS role.
Check the report’s Manage → Row-level security settings and ensure the user or an AD group they belong to is assigned to a role.
Microsoft documentation for RLS in Power BI Report Server:
https://learn.microsoft.com/power-bi/report-server/row-level-security-report-server
In short, the loop occurs when the user has no RLS role assigned; adding the user or group to a role should resolve access.
Thank you Olufemi7, yes, assigning a role to the user resolves the issue, however the "reloading loop" behavior is confusing. It did not occur in previous versions
Hi mrusu ,
Thank you for reaching out to the Microsoft fabric community forum.According to the official Power BI Report Server changelog, the March 5, 2026 build (15.0.1120.122) includes a fix for an issue where reports using Row-Level Security RLS could get stuck spinning.
Change log for Power BI Report Server - Power BI | Microsoft Learn
Since you are still experiencing the reload loop when a user is not assigned to any RLS role, it may help to check the Report Server logs ReportServerService or RSPortal log to see if any authentication or RLS-related errors appear during the reload.
Additionally, a similar discussion about the January 2026 PBIRS update is available here and may be helpful:
Solved: Re: PowerBI January 2026 Update - On-Premise Repor... - Microsoft Fabric Community
Hope the above provided information help you resolve the issue, if you have any further concerns or queries, please feel free to reach out to us.
Regards,
Community Support Team.Thank you v-hjannapu, will have to analyze the logs as suggested.
Regards
Hi mrusu,
Thanks for the update. Please check the logs when you get a chance and see if any RLS or authentication related entries appear during the reload. That information should help identify what is causing the behavior.
If you notice anything unusual in the logs, feel free to share the details here and we can take a look further.
Regards,
Community Support Team.
