Forum Discussion
Licensing / Pricing / Sharing.
Super UserAnonymous I will try but there is a lot more when it come to licensing and sharing:
#1 - This is the cheapest. But there are free viewing licenses if you have Power BI Premium, P1 cost $5000 USD/month (I think). So if you have 600 viewers, instead of paying $10 per month which will cost $6000, P1 will be cheaper in this case. It is a decision tree and there are other things why you go for a premium, in your case, we are purely talking about licensing.
#2.3 - Sharing outside org, assuming everyone using Pro, either your external client needs to buy a Pro license under their tenant, you share with them and they will log in with their credentials (assuming they have Pro) and they will able to view the report but if they are not buying pro license then you will buy under your tenant and give them new ID ([email protected]) and they will use that to login to access the reports. End of the day someone has to pay for Pro license.
#3.2 - you don't want to use this, It is not secure, whoever so ever has that link will able to see the report. You will be putting org data at risk, also if tomorrow you want to use RLS (Row Level Security), you will not be able to use this method. End of the day, this is generally used where you have some public information and want to share it with the general public without any data security risk.
Hi Parry2K,
Sincere apologies for the delay. Thanks a lot for the detailed answer.
A little more elaboration will help.
From your answer 2.3 above: bottomline is any end user has to have a p bi pro lic to view the report.
Now from your 3.2 i also understand that file-> embed-> portal is not necessarily a great idea from data security perspective.
Elaborating my use case a bit more better sharing my idea:
Our application has its own authentication ( user name / pwd ) and hosted on https. Inside this applicaiton after the customers login with their respective credentials, they will see the so called "PBI dashboard" BUTTON ONLY. This button is custom configured to point to this embedded link. Now when a customer after logging in our application, clicks the button, am assuming he will be directed to the report page / link, where he will be asked to signin ( as he would need a pbi pro lic either from his org or we buy for his specfic email id in our tenant) and then he would need to request access, which we will give and hopefully only then he will see the report.
Therefore in this case in order for the customer to see the report that we as service provider are generating:
1. 1st authentication in our app
2. 2nd authentication in P BI Pro lic check ( PBI Signin )
3. Report access
Therefore, is there the data security risk still there? Or am i missing something?
I mean we arent publishing that link anywhere on a public portal / site etc...so just trying to understand.
Thanks,
Gaurav.