06-16-2016 12:44 PM
Microsoft says the following regarding Power BI Embedded for internal use.
"Power BI Embedded is only intended for external use and may not be used within internal business applications. In order to embed Power BI content for use in internal business applications, you should use the Power BI service, and all users consuming that content must have a valid Power BI Free or Power BI Pro user subscription license." Quote Found here:
In the Power BI governance white paper the difference between the "Hybrid Implementation: Custom Application Integration" method and the "Hybrid Implementation: Public Website" option is that the former has a "Custom Application" that lives "on-premises" and with the later the application is moved to "cloud services" and re-titled "public website".
I think a "public website" is a website accessible from the internet. But it does not preclude requiring authentication. So if I go with public website but only allow authenticated individuals to view reports can I then use Power BI Embedded?
How is an internal application defined vs an external application by MS?
Is the distinction technical (web accesssible vs not accessible from web(intranet)) or is the distinction business/spirit driven (i.e If it is meant primarily to be used by individuals within the organization then it must be considered an internal application even if publicly accessible)?
I hope the answer is: If it is accessible from the internet power BI Embedded can be used even if the app is meant to only allow access to our corporate users.
For internal apps I must have a pro license and lose the ability to embed reports in an app that are interactive. Users must click through and be redirected to power bi services.
I am not trying to get around paying for pro user licenses. I am instead interested in having the technical/design freedom to render in the browser a branded app with other content available along side the power BI content that refreshes in browser. The URL must be our domain. It does not matter to me (yet) whether the app lives in azure or on premises. But if putting it in Azure makes it external and gives me Embedded I will do that. The redirect to Power BI Service is not the controlled experience we are looking for.
If I make the app available on the internet and require authentication against Azure AD can I use Power BI Embedded?
Other than a slightly elevated security concern (Azure uses ssl by default) what is wrong with deploying a Power BI dashboard meant for corporate users to a web app, authenticating against AD and having the Power BI embedded experience? Any insights on pros and cons of internal vs. external and how MS differentiates?
Thanks for any help
08-23-2016 10:15 AM
I'm trying to figure out if "Public" refers to the whole world, or just my Office 365 tenant. I want to embed my report on a SharePoint site....so I wouldn't worry about anyone external seeing it because they have to get through to SharePoint first. Isn't that correct?
09-08-2016 08:04 PM
IF you sahre to public so that it gives you a URL to embed then that URL is discoverable on the web or accessable by anyone that knows the URL so nothing that you don't wish the world to have access to should be shared that way.
09-27-2016 11:55 AM
It's unfortunate that the licensing seems to preclude use within internal enterprise applications. Is it really the case that every user of an internal web app leveraging Powe BI Embedded would been to be licensed for Power BI Pro and incur the Power BI Embedded service charge? If so it's unfortunately not financially feasible for a lot of what my clients need.
03-03-2017 01:24 AM
I realise your post was a while ago but have you seen the recently released the Power BI preview web part for SharePoint online? It will only work for the modern SharePoint sites on O365