1810
The general requirement is that visualizations (Power View, SSRS etc...) must not circumvent existing policies, or introduce yet another set of security policies on top of those already implemented at the source.

* For example, a visualization of sales data needs to reflect the policy that account managers can only read sales data for their region.
* For performance reasons, this is enforced at the source by injecting predicates into the query based on the end users identity. If identities for end users are not passed down the process chain into the data layer, it leaves us little option but to publish individual reports for every region, which results in an explosion of complexity and numbers of reports, or move the whole model to BISM and manage the policy in yet another place (namely the BISM model).

Impact
blocking migration to SPO/BI Sites. At least 412 Site Collections with more than 600 Power Views. Impacting Adoption or migration for majority of BPUs - e.g. Finance, LCA, HR, etc
STATUS DETAILS
Under Review

Hey all! We've continued to make progress here, so I wanted to update this thread with our current capabilities for maintaining security on dashboards/reports. As always, all of this information can be found in our Row-Level Security (RLS)documentation: https://powerbi.microsoft.com/en-us/documentation/powerbi-admin-rls/ > If you have set up RLS in Analysis Services, Power BI will send the signed-in user's credentials to Analysis Services, and respect the RLS rules set up on the on-premises model. > Separately, you can set up RLS in Power BI for data sources that you import or connect to via DirectQuery. This process starts in PBI Desktop, where you define roles, and write DAX to constrain what data these roles can see. As part of this process, can you use the UserPrincipalName () DAX function to get the current signed in user's UPN (e.g. joe@contoso.com). Then, once you publish to service, you can assign users to these roles. Does the above meet your requirements? Please let us know via comments or e-mail. Those of you who requested that the identity of the signed in Power BI user be pass through to Azure SQL, SQL DB, DWH, etc.: we hear you - that is under consideration. Thanks, -Sirui

Comments

R

This is one of those "deal-breaker" kind of features that will determine whether one can use Power BI or not. Absolutely has to be on the immediate roadmap for Power BI.

R

We have 1 common data source where we want to be able to show certain data based who is viewing the report, is this currently possible to do ?

R

It 's too important PowerBi has its own management system for row level security.
This will give access to PowerBi to companies that can not buy SQL Server Enterprise.

R

Am I understand this correctly that, it is an ability to link Logged in User to the Rows Level Data that the User Can see ? That's what I want to do now.

R

Please add this functionality as there is always requirement for sales firm to show saleperson user their own data when they logged in to office 365 tenat.


We should be able to write a query that allow us to filter data with the current user logged in

R

This feature should be implemented and rolled out at the earliest.

R

On August 19th, 2015 MS announced GA of Row-Level security in SQL Azure Database. See https://msdn.microsoft.com/library/dn765131.aspx for more information

R

DAX has a USERNAME () function which may help

R

I have role in tabular model
but in power bi site it's not working

in bi desktop it work great

somebody can explain

R

It's should be a part of the Power Bi platform if Microsoft want to seriously push as a coporate solution