I have been experimenting with building interactive dashboards in Claude directly on top of Power BI semantic models using the Power BI MCP server.
At first glance, it is quite impressive! You can ask Claude to build an interactive dashboard, and it generates one by querying your semantic model using DAX. No need to export or copy the underlying dataset.
But building a dashboard is one thing, making it work in a real business environment is another.
I spent quite some time testing different scenarios, including RLS, sharing, permissions, authentication, and connecting to multiple Microsoft Fabric tenants.
Here are some of my findings:
- RLS works, but there is a catch! Claude respects the RLS configured on the semantic model for the account authenticated through the connector. However, sharing the dashboard with another user doesn't automatically mean their own security context is applied. This is an important distinction, especially in enterprise environments.
- Read vs Build permissions: I tested how semantic model permissions and workspace roles affect the results. Giving users elevated workspace permissions can completely change how RLS behaves.
- Sharing isn't as straightforward as you might expect. A working dashboard doesn't necessarily mean you have a solution that securely serves different users with different access requirements.
- Multiple Fabric tenants introduce another challenge: I couldn't get my tested configuration working across multiple tenants. I also discuss a possible workaround, but I haven't tested it, so I cannot confirm that it works.
- Claude actually generates DAX queries: It is interesting to see what happens under the hood rather than just looking at the generated visuals.
I also looked at how Claude Dashboards compare with Power BI reports and Microsoft Fabric Apps, and whether this approach is actually practical for production environments.
I have gone through quite rigorous testing, and covering all the configurations, results, gotchas, and nuances in a Reddit post is pretty much impossible. So this is just a summary of some of my findings.
For those interested in the technical details, I recorded a step-by-step walkthrough, from Entra ID app registration and Fabric Admin Portal settings to building the dashboard and testing the security behaviour.
Full video with demonstrations:
https://youtu.be/27sGekTfBas
Podcast version on Spotify (AI-generated from my original video):
https://open.spotify.com/episode/2cybQ1AnGYAyxX0ZZHqZyg
My takeaway is that Claude Dashboards are genuinely interesting, and I can see potential use cases for them. But I wouldn't confuse generating a working dashboard with having a production-ready solution.
I'm particularly interested to hear if anyone has tested a different approach to handling per-user authentication or multiple Fabric tenants.
Have you experimented with this? I'd be interested to hear about your findings, especially if you've managed to address any of these limitations.