Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi,
We embed reports in our web application for our clients using the Javascript API (App Owns Data). I have a question about the best way of securing the data of a PowerBI report/model.
My simple scenario:
I could assume that because in my report I don't display the sales data in a table (I only have a card with my measure) that the user can't see the underlying data of the sales table. But someone with knowledge of the Javascript API could modify the code in the browser and could see that data (for example by activating edit mode, by using it in a custom app with the PowerBI Report Authoring library, etc...).
Am I right in assuming that the only way to prevent this is to aggregate the table in the model and using RLS on the sales tables?
I don't want to scare our clients, but should we say "the model should only have the tables that you want your end users to see. If you don't want users to see some data, don't put it in the model without RLS"?
Thanks!
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Experience the highlights from FabCon & SQLCon, available live and on-demand starting April 14th.
| User | Count |
|---|---|
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |