Forum Discussion
Power BI Template App – Viewer users unable to access reports since 27 July 2026
Hello,
We are experiencing an issue that started on 27 July 2026 affecting multiple independent customer environments using the same Power BI Template App solution.
Summary
Since 27 July 2026, users with Viewer permissions are no longer able to open reports connected directly to the semantic model created during the Template App installation.
The reports previously worked correctly for several years without any issues.
The problem occurs when Viewer users access either:
The published Power BI App
Individual reports directly
Instead of displaying the report, the browser becomes unresponsive and eventually shows a message similar to:
"Page Unresponsive"
No Power BI authorization error, RLS error, dataset permission error or other service error is displayed.
The issue has been reproduced in both:
Microsoft Edge
Google Chrome
Behaviour Observed
Test Result
| Viewer accessing reports connected directly to the Template App semantic model | ❌ Browser becomes unresponsive |
| Contributor accessing the same reports | ✅ Works correctly |
| Member accessing the same reports | ✅ Works correctly |
| Admin accessing the same reports | ✅ Works correctly |
| Removing users from all RLS roles | ❌ Issue remains |
| Completely removing RLS from the semantic model | ❌ Issue remains |
| New semantic model created manually in the same workspace (with RLS) | ✅ Works correctly for Viewer users |
| New semantic model created manually in the same workspace (without RLS) | ✅ Works correctly for Viewer users |
| Composite model consuming the affected Template App semantic model together with another data source | ✅ Works correctly for Viewer users |
| Multiple independent customer environments affected | ✅ Yes |
Pattern Identified
From our investigation, the behaviour is consistent across all affected environments:
Only semantic models created through Power BI Template App installation are affected.
Only users with Viewer permissions experience the issue.
Contributors, Members and Admins can access the same reports without any problems.
The issue is not related to Row-Level Security (RLS), as removing RLS entirely does not resolve it.
Semantic models created manually in the same workspace work correctly for Viewer users.
Composite models that consume the affected semantic model also work correctly.
The issue affects multiple independent customer tenants using the same Template App solution.
What Has Not Changed
The solution has been operating successfully for several years across multiple customer tenants.
Immediately before the issue started, no changes were made to:
Semantic model design
Report design
Row-Level Security configuration
Workspace permissions
Template App deployment process
Report publishing process
The only observable change is that the behaviour started on 27 July 2026.
Request
Based on the testing performed, we believe this is unlikely to be a report design, semantic model configuration or security configuration issue.
The consistent behaviour across multiple independent customer tenants strongly suggests a possible Power BI Service regression affecting Viewer access to semantic models generated through Template App installations.
Could you please investigate whether any backend or service changes were deployed around 27 July 2026 that could explain this behaviour?
If required, we can provide:
Workspace IDs
Semantic Model IDs
Report IDs
Activity IDs
Correlation IDs
Example customer environments where the issue can be reproduced
We appreciate your assistance and look forward to your investigation.
Kind regards,
Nuno Duarte
Solutions Consultant
Hi nuno_m_duarte
We would like to inquire whether have you got the chance to check the solutions provided by arvindsingh802 in community to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
4 Replies
- v-csrikanth
Community Support
Hi nuno_m_duarte
We would like to inquire whether have you got the chance to check the solutions provided by arvindsingh802 in community to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community. - arvindsingh802
Community Champion
This is a known issue reported on 24th July, Please refere workaround mentioned -https://support.fabric.microsoft.com/known-issues/?product=Power%2520BI&active=true&fixed=true&sort=published&issueId=1893
- nuno_m_duarteFrequent Visitor
The published workaround cannot be implemented because it fundamentally breaks the security model of the solution.
- arvindsingh802
Community Champion
Then would suggest to raise incident with Microsoft and wait for there resolution.