Forum Discussion
Power BI Embedded pricing entry point
Hi,
We are currently looking at options for reporting but dont quite understand the limitations around using Power BI embedded.
It would be good to get clarification on the following...
1) Can we use Power BI embedded for a website that sits behind authentication?
2) What is the entry point in terms of Premium Tier machines (is it P1 or EM1) ?
3) Would each user of the embedded reports have to be counted as a 'frequent/occaisional' account within the premium tier?
I have checked many of the other forum answers but the responses are often conflicting, Either with other forum posts or blog posts/MSDN articles elsewhere.
Thanks in advance,
Matt
Anonymous wrote:
Hi,
We are currently looking at options for reporting but dont quite understand the limitations around using Power BI embedded.It would be good to get clarification on the following...
1) Can we use Power BI embedded for a website that sits behind authentication?2) What is the entry point in terms of Premium Tier machines (is it P1 or EM1) ?
3) Would each user of the embedded reports have to be counted as a 'frequent/occaisional' account within the premium tier?
I have checked many of the other forum answers but the responses are often conflicting, Either with other forum posts or blog posts/MSDN articles elsewhere.
Thanks in advance,Matt
1) What do you mean sit behind authentication? When Embedding with non-Power BI users, you can hard coded the account/password in your web application, see the demo App Owns Data.
2) It is all depends on how you'd like to use Power BI Service. See Premium capacity nodes matrix.
- P nodes can be used for embedded or service deployments
- EM nodes can be used for embedded deployments only
3) I think the so called "counted frequent/occaisional userd" are used to evaluate the visit traffic to your embedded reports so that proper tier would be proposed. Mind the "Max page renders at peak hour" in the forementioned matrix.
2 Replies
Anonymous wrote:
Hi,
We are currently looking at options for reporting but dont quite understand the limitations around using Power BI embedded.It would be good to get clarification on the following...
1) Can we use Power BI embedded for a website that sits behind authentication?2) What is the entry point in terms of Premium Tier machines (is it P1 or EM1) ?
3) Would each user of the embedded reports have to be counted as a 'frequent/occaisional' account within the premium tier?
I have checked many of the other forum answers but the responses are often conflicting, Either with other forum posts or blog posts/MSDN articles elsewhere.
Thanks in advance,Matt
1) What do you mean sit behind authentication? When Embedding with non-Power BI users, you can hard coded the account/password in your web application, see the demo App Owns Data.
2) It is all depends on how you'd like to use Power BI Service. See Premium capacity nodes matrix.
- P nodes can be used for embedded or service deployments
- EM nodes can be used for embedded deployments only
3) I think the so called "counted frequent/occaisional userd" are used to evaluate the visit traffic to your embedded reports so that proper tier would be proposed. Mind the "Max page renders at peak hour" in the forementioned matrix.
Thanks for your response, and appologies for my slow reply....
Authentication: I was unsure if the use of embedded was intended for use on fully public pages only. Some API providers occaisionally use this restriction to stop enterprise aplications from using functionality within closed sites - without first paying additional enterprise licencing costs. - My original question wasn't very clear but thank you for clearing this up.
P1 or EM1: Suddenly the 'EM' tier makes sense (Embedded) - cant believe i didn't work that one out.
Frequent/Occaisional users: I think we will have to crunch some numbers on this one. Its quite difficult to know exactly how many times someone may load the page hosting the reports. Will concentrate on that render limitation rather than number of real user accounts for now.I will have to do some testing to see what happens when you hit the max page renders. I am assuming that you get a suitable http response back (e.g. http: 429 too many requests)
Thanks again for your help.