1809
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

Very useful improvement, and would simplify a lot the managing of the data.

R

This is very much needed feature to restrict the data based on logged in user. Is there any plan to implement this feature?

R

I would like to ask the Power BI team if there is a current work around for this?

Indeed - I would consider this an ´enterprise´grade feature ... so many things you could do in sales reporting for example: Store / Sales area performance, Sales commission etc.)

R

We currently have a large number of leaders and they work on different clients and we need to control what clients they can see. Glad to see that this have been started . Many thanks Power BI team !

Joe

R

This is a very very importante feature. It would be a great thing to see this in the near future.

R

We are working on a Azure Portal to host PowerBI reports for the healthcare domain. Using AAD credentials would be very helpful as most of the users are federated by their current id providers.

R

Would be great improvement for those who cannot build "SSAS with row-level secutiry + Enterprise gateway etc." that in fact very complex scenatio for many companies. Would be much easier if Power BI could manage this. For example, reserved table in data model with reserved Username field that can be "lookup" table for the rest model.

R

We're working to Implement Power BI for all the schools in our district but we need to control what the user sees based on the school they work for or we run up against FERPA violations!

R

we are now facing this problem, how to provide customer personalized views of reports. no workaround found. Any guess of compleiting this features?

R

Definitely needed. Users want to log in and see only what pertains to them.