Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowFabric Data Days Monthly is back. Join us on March 26th for two expert-led sessions on 1) Getting Started with Fabric IQ and 2) Mapping & Spacial Analytics in Fabric. Register now
Hi everyone!
I’m trying to share the Fabric Capacity Metrics App with a wider group of users in my organization.
My goal is:
However, I’m not sure whether RLS is supported for this scenario or if there is a recommended workaround (e.g., copying the model, building a custom metrics semantic model, or ....).
My questions:
Any insights or experiences would be greatly appreciated!
Solved! Go to Solution.
Hi @fb200
Understand the metrics app compute page - Microsoft Fabric | Microsoft Learn
What is the Microsoft Fabric Capacity Metrics app? - Microsoft Fabric | Microsoft Learn
Hope this helps you
Thank you!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
I ended up using the third option you suggested. As a parameter, I applied the capacity name as a global report‑level filter across all pages and then locked it. For a first attempt, this works well and already gives users a focused view on their own consumption patterns. I hope it will be helpful for optimizing their solutions too.
However, this approach still requires manually rebuilding or adjusting the reports whenever the Metrics App gets updated or reinstalled.
If someone with more advanced semantic‑link‑labs experience has sample code or best practices for automating this workflow, that would be extremely valuable. Ideally, I’d love to automate the cloning, rebinding, and filter injection steps so the restricted‑view reports could be recreated automatically whenever the underlying app changes.
Any hints or code snippets would be greatly appreciated!
Hi @fb200,
Thank you for reaching out to the Microsoft Fabric Forum Community, and special thanks to @lbendlin and @suparnababu8 for prompt and helpful responses.
Just following up to see if the Response provided by community members were helpful in addressing the issue. if the issue still persists Feel free to reach out if you need any further clarification or assistance.
Best regards,
Prasanna Kumar
@v-pgoloju : I shared my solution based on the suggestion from @suparnababu8. Could you please forward it to one of the semantic link labs owerns. Maybe they can add a function to support this manual task.
I believe it would be extremely valuable for users to optimize their solutions, if they had access to their capacity consumption, without being capacity owner.
Please keep in mind that the capacity Metrics app also consumes CUs, and lots of it. Don't give users direct access to it.
I use the Power BI Pro License for this workspace (SM + Reports).
Why would you use it with a Fabric Capacity?
Licenses have nothing to do with capacity types.
The capacity metrics app is based on a Kusto Eventhouse. There's no RLS for that AFAIK.
Best practice is to share screenshots with users. Do not ever give direct access, ever.
Hi @fb200
Understand the metrics app compute page - Microsoft Fabric | Microsoft Learn
What is the Microsoft Fabric Capacity Metrics app? - Microsoft Fabric | Microsoft Learn
Hope this helps you
Thank you!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
Thanks
I ended up using the third option you suggested. As a parameter, I applied the capacity name as a global report‑level filter across all pages and then locked it. For a first attempt, this works well and already gives users a focused view on their own consumption patterns. I hope it will be helpful for optimizing their solutions too.
However, this approach still requires manually rebuilding or adjusting the reports whenever the Metrics App gets updated or reinstalled.
If someone with more advanced semantic‑link‑labs experience has sample code or best practices for automating this workflow, that would be extremely valuable. Ideally, I’d love to automate the cloning, rebinding, and filter injection steps so the restricted‑view reports could be recreated automatically whenever the underlying app changes.
Any hints or code snippets would be greatly appreciated!
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Fabric update to learn about new features.
| User | Count |
|---|---|
| 25 | |
| 11 | |
| 10 | |
| 7 | |
| 7 |
| User | Count |
|---|---|
| 50 | |
| 42 | |
| 25 | |
| 15 | |
| 14 |