<?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 Re: Power BI Embedding Multiple Customers in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2490434#M35875</link>
    <description>&lt;P&gt;@Anonymous&lt;/a&gt;&amp;nbsp;In case it answered your question please mark this as a solution for community visibility. Appreciate Your Kudos &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 03 May 2022 08:48:48 GMT</pubDate>
    <dc:creator>SpartaBI</dc:creator>
    <dc:date>2022-05-03T08:48:48Z</dc:date>
    <item>
      <title>Power BI Embedding Multiple Customers</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2483516#M35769</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have a requirement where we need to take 1000s of customers' data in a single dataset and embed it in a third-party application. We need to ensure customers only see their data and not any other customers' data.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have gone through this official documentation (&lt;A href="https://docs.microsoft.com/en-us/power-bi/developer/embedded/embed-multi-tenancy)" target="_blank" rel="noopener"&gt;https://docs.microsoft.com/en-us/power-bi/developer/embedded/embed-multi-tenancy)&lt;/A&gt;&amp;nbsp;and seems to be a promising solution.&amp;nbsp; However, the only thing that is concerning is that it does not viable creating 1000s of workspaces for 1000s of customer in a single Power BI Tenant.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a better way to achieve this?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 13:59:50 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2483516#M35769</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-04-28T13:59:50Z</dc:date>
    </item>
    <item>
      <title>Re: Power BI Embedding Multiple Customers</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2483667#M35772</link>
      <description>&lt;P&gt;Hi&amp;nbsp;@Anonymous&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;This is not a limitation on the total number of workspaces in a Power BI Tenant.&lt;BR /&gt;A &lt;STRONG&gt;single&lt;/STRONG&gt; service principal cannot be a member of more than 1000 workspaces (although I can tell you that, in practice,&amp;nbsp;it works).&lt;BR /&gt;&lt;BR /&gt;The recommended approach is to use service principal profiles. Have a look at:&amp;nbsp;&lt;A href="https://powerbi.microsoft.com/en-us/blog/announcing-general-availability-of-service-principal-profiles-in-power-bi-embedded/" target="_blank" rel="noopener"&gt;https://powerbi.microsoft.com/en-us/blog/announcing-general-availability-of-service-principal-profiles-in-power-bi-embedded/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 14:54:32 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2483667#M35772</guid>
      <dc:creator>SpartaBI</dc:creator>
      <dc:date>2022-04-28T14:54:32Z</dc:date>
    </item>
    <item>
      <title>Re: Power BI Embedding Multiple Customers</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2483691#M35773</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.fabric.microsoft.com/t5/user/viewprofilepage/user-id/377293"&gt;@SpartaBI&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your reply!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;From the diagram I can see that Service Prinipcal Profile have a one-to-one mapping with Power BI workspaces. This means for my situation 1000s customer = 1000s workspaces which I want to avoid. Any other way around this?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 15:00:23 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2483691#M35773</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-04-28T15:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: Power BI Embedding Multiple Customers</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2483816#M35774</link>
      <description>&lt;P&gt;Hi&amp;nbsp;@Anonymous&lt;/a&gt;,&lt;BR /&gt;&lt;BR /&gt;Sure. You do not have to create a workspace per customer.&lt;BR /&gt;It is usually convenient from a logical point of view. Especially if you plan to allow end-users to create reports/plan to use the Power BI Service for QA.&lt;BR /&gt;&lt;BR /&gt;You can arrange the datasets and reports any way you like in any number of workspaces.&amp;nbsp;Just note the limitation on the number of artifacts per workspace:&amp;nbsp;&lt;A href="https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-new-workspaces#considerations-and-limitations" target="_blank" rel="noopener"&gt;Workspace Limitations&lt;/A&gt;&lt;BR /&gt;You will be the one who controls the access through the embedding application.&lt;BR /&gt;&lt;BR /&gt;For example, you can create 1 workspace for all of your reports (up to 1000) &amp;amp; 1 workspace for all of your datasets (1 per customer, up to 1000).&lt;BR /&gt;Reports will be &lt;A href="https://docs.microsoft.com/en-us/javascript/api/overview/powerbi/bind-report-datasets" target="_self"&gt;dynamically bound&lt;/A&gt; to different datasets as part of the embedding process.&lt;BR /&gt;If you'll have 1500 customers or 1500 reports- Just add a second or third workspace.&lt;BR /&gt;&lt;BR /&gt;If you wish to reduce the development &amp;amp; management effort, and have no objection to combining different customers in the same DB- Consider using a single dataset with&amp;nbsp;&lt;A href="https://docs.microsoft.com/en-us/power-bi/developer/embedded/embedded-row-level-security" target="_blank" rel="noopener"&gt;Row Level Security (RLS)&lt;/A&gt;.&lt;BR /&gt;If implemented correctly, this will ensure customers only see their own data.&lt;BR /&gt;Note that this approach will have some performance impact and will increase the amount of resources needed for processing (subject to the implementation).&lt;/P&gt;</description>
      <pubDate>Thu, 28 Apr 2022 15:51:17 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2483816#M35774</guid>
      <dc:creator>SpartaBI</dc:creator>
      <dc:date>2022-04-28T15:51:17Z</dc:date>
    </item>
    <item>
      <title>Re: Power BI Embedding Multiple Customers</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2490434#M35875</link>
      <description>&lt;P&gt;@Anonymous&lt;/a&gt;&amp;nbsp;In case it answered your question please mark this as a solution for community visibility. Appreciate Your Kudos &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 03 May 2022 08:48:48 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/Power-BI-Embedding-Multiple-Customers/m-p/2490434#M35875</guid>
      <dc:creator>SpartaBI</dc:creator>
      <dc:date>2022-05-03T08:48:48Z</dc:date>
    </item>
  </channel>
</rss>

