Security - Ability to maintain source security for reports published on BI Sites

[RAMUK1]

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

[tim65]

Hi Sirui, Any update on identity pass through to Azure SQL. We know it is under consideration, but we need to know if it will be implemented. Thanks, Tim

[conniecorredor]

We really need the ability to connect to an SQL database with AD authentication for a live gateway connection when publishing to the web. PowerBI has this feature on the desktop, it should work on the web as well.

[pbiideas1]

Agreed - we are also looking at RLS and through desktop, definately slows things down. There needs to be better ways to link back to DB.

[swapnil_crapmai]

We are using an Odata feed to CRM Online and to mimic the entire security model already customized in CRM is not very practical.

[krishnak1]

Importantly when the RLS Security is enabled and the workbook has been downloaded to PBI Desktop by an end user they should not be able to edit the security configuration setup.