Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowData Days is here! Join us now for 60+ days of learning, challenges, and connection. Learn more
Until now I have read that row level security can be only achieved by tabular SSAS.
Speaking about row level security, we can see it has been implemented in SQL Server 2016 and Azure SQL DB v12.
According to this. Does it mean that also user logged in Power BI which pulls data from aforementioned data sources will inherit row level security and see only data he has permission to?
Has anyone had any luck implementing row level security using Azure SQL DB v12?
This is a very new feature and I would have to test to be sure but I would think that this would be the case. However, note that this is entirely different than using the Analysis Services Connector to connect to a tabular SSAS model. The reasons is that the Analysis Services Connector is a LIVE connection to the tabular model and implements the user-based/row level security on-the-fly.
Currently, with SQL Server 2016 and Azure SQL DB v12, there is nothing that currently supports a live connection and thus if it does work, it is strictly supported at the time of import and refresh (when data is pulled into the data set). I think that this is an important distinction.
In the first case, you could publish a single dashboard that could be used by everyone and they would only see what they are allowed to see. In the second case, you would have to publish an organizational content pack and everyone would essentially have their own personal version of the dashboard/reports
Don't miss out on Data Days, June 15 through August 7. Learn Fabric, Power BI, SQL, AI and more.
Check out the May 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 1 |
| User | Count |
|---|---|
| 11 | |
| 11 | |
| 5 | |
| 4 | |
| 3 |