<?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: Using Report Server for Internal and External users in Report Server</title>
    <link>https://community.fabric.microsoft.com/t5/Report-Server/Using-Report-Server-for-Internal-and-External-users/m-p/776755#M11384</link>
    <description>&lt;P&gt;After talking with Microsoft on this, i feel like my initial thought is correct, seperate out the external portal and expose it however you normally would do that within your network security model. It didnt really seem like there was one way to solve it, rather a bunch of smaller options.&lt;/P&gt;</description>
    <pubDate>Tue, 27 Aug 2019 11:41:12 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2019-08-27T11:41:12Z</dc:date>
    <item>
      <title>Using Report Server for Internal and External users</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/Using-Report-Server-for-Internal-and-External-users/m-p/756345#M11174</link>
      <description>&lt;P&gt;I have a requirement on a project that prohibits us from using the Power BI cloud service, but we still need to be able to support users within our organization and our external clients.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would i look towards multiple instances of PBiRS (One for Internal, n for External) with varying security methods (AD for internal and another method for external)? I feel like this is the right choice but i haven't seen much in terms of documantation on this, so i wanted to ask around before setting down any path.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 12:28:02 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/Using-Report-Server-for-Internal-and-External-users/m-p/756345#M11174</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-08-02T12:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: Using Report Server for Internal and External users</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/Using-Report-Server-for-Internal-and-External-users/m-p/774720#M11377</link>
      <description>&lt;P&gt;asking same questions.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Aug 2019 20:14:55 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/Using-Report-Server-for-Internal-and-External-users/m-p/774720#M11377</guid>
      <dc:creator>tltl666</dc:creator>
      <dc:date>2019-08-23T20:14:55Z</dc:date>
    </item>
    <item>
      <title>Re: Using Report Server for Internal and External users</title>
      <link>https://community.fabric.microsoft.com/t5/Report-Server/Using-Report-Server-for-Internal-and-External-users/m-p/776755#M11384</link>
      <description>&lt;P&gt;After talking with Microsoft on this, i feel like my initial thought is correct, seperate out the external portal and expose it however you normally would do that within your network security model. It didnt really seem like there was one way to solve it, rather a bunch of smaller options.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Aug 2019 11:41:12 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Report-Server/Using-Report-Server-for-Internal-and-External-users/m-p/776755#M11384</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2019-08-27T11:41:12Z</dc:date>
    </item>
  </channel>
</rss>

