<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How to incorporate using Azure SQL RLS Security Policy framework with PowerBI RLS in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/How-to-incorporate-using-Azure-SQL-RLS-Security-Policy-framework/m-p/1173769#M24316</link>
    <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Jun 2020 15:21:32 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2020-06-22T15:21:32Z</dc:date>
    <item>
      <title>How to incorporate using Azure SQL RLS Security Policy framework with PowerBI RLS</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/How-to-incorporate-using-Azure-SQL-RLS-Security-Policy-framework/m-p/1173769#M24316</link>
      <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jun 2020 15:21:32 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/How-to-incorporate-using-Azure-SQL-RLS-Security-Policy-framework/m-p/1173769#M24316</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2020-06-22T15:21:32Z</dc:date>
    </item>
  </channel>
</rss>

