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
To begin with, we already have a RLS applied to our database using Security Policy. Assuming we dont want to change that as it's doing fine for our other reporting solutions.
With POWER BI, we plan to use App Own Data approach to embed PBI Reports in our application. This approach does not pass through any user credentials but allows application to specify username at the time of generating embed token etc. which is all good and DAX expressions can be used to filter data out. However since PBI does not pass the username to the Database, the RLS Security Predicate filters forbid access to data. So unless we remove the RLS from Database, we won't get the data in PBI report.
Is there a bit I am missing here that could make them work together? Or that is how things are designed and the only way is to remove RLS from database with App own data approach.
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 |
| User | Count |
|---|---|
| 8 | |
| 8 | |
| 4 | |
| 3 | |
| 2 |