Forum Discussion
Advocate IVRLS in Sep 2025
Hi Vanchy_Liao ,
Based on your testing, your understanding is correct. This issue appears to be caused by a version mismatch: reports created using Power BI Desktop (RS) 2024-09 and then uploaded to PBIRS 2025-09 can trigger an infinite refresh when a user is not assigned to any RLS role. Since the same behavior can be reproduced with a simple empty report, this strongly indicates a PBIRS regression, not a report design problem.
At the moment, the practical workaround is to open the existing reports in Power BI Desktop (RS) 2025-09 and republish them to the latest PBIRS. This aligns the report metadata with the server version and avoids the refresh loop.
This should not be necessary long-term, so raising a Microsoft support case is still recommended when possible, as this likely requires a product fix.
Regards,
Microsoft Fabric Community Support Team
Community ChampionDiscovering an infinite refresh bug in your production PBIRS environment is alarming, especially with 100+ reports at stake. The fact that unassigned users trigger this in the 202409 version creates both immediate user experience issues and long-term maintenance worries.
First, don't manually rebuild all reports - that's unnecessary work until we confirm the scope. Start by testing if this affects only newly created reports or all existing ones. Pick 3-4 older reports and see if unassigned users encounter the same issue. If it's limited to new reports, you've avoided a massive rework.
For immediate relief, consider adding all active users to a basic "Viewer" role in your RLS configuration, even with minimal access. This should prevent the infinite refresh loop while you investigate. Also check Microsoft's community forums - others may have reported this 202409 bug and found workarounds.
Finally, this warrants opening a support case with Microsoft, as it appears to be a version-specific regression. Document your reproduction steps clearly: empty report + RLS roles + unassigned user = infinite refresh. While waiting for a fix, you might consider whether temporarily reverting to your previous PBIRS version is feasible, as this bug could impact user adoption and trust in your reporting system.
(1) Solved: Can I update Row-level security via Rest API? - Microsoft Fabric Community
Row-level security (RLS) in Power BI Report Server - Power BI | Microsoft Learn
Change log for Power BI Report Server - Power BI | Microsoft Learn
Vanchy_LiaoHi 123abc ,
i revise my question. thank you 😀
More Information:
i upload the existing pbi report which made by 202409 desktop to 202509 PBIRS.
v-menakakotaCommunity Support
Hi Vanchy_Liao ,
Thanks for reaching out to the Microsoft fabric community forum.
Thanks for the clarification. Since the issue appears specifically when a report built in the 2024-09 Desktop for RS is uploaded into the 2025-09 PBIRS, it does point more strongly to a version-specific regression rather than a problem with your report design.
You’ve already done the right thing by confirming it’s reproducible with a simple empty report + RLS. This helps show that the behaviour didn’t exist in earlier PBIRS versions and likely started after the upgrade.
At this point, the best next step is to open a Microsoft support ticket with your exact reproduction steps, because this looks like something that needs engineering review.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn
Best Regards,
Community Support Team- v-menakakota
Hi Vanchy_Liao ,
We wanted to follow up and ask if you have submitted a support ticket. Could you let us know if the issue was resolved after creating the support case?If you have any further questions, please let us know. we can assist you further.
Regards,
Microsoft Fabric Community Support Team