topic Re: Power BI Embedded in Developer

Power BI Embedded

kuldeep_kumar — Fri, 23 Jun 2017 02:40:38 GMT

HI Team,

Power BI embedded gives two ways to embed reports into Custom Web App.

For Power BI users (will need only Power BI Pro license for each users). [assuming this model as PB1 ]
Other with having at least one PowerBI pro and PowerBI premium. [assuming this model as PB2 ]

What are the pros and cons using one over the other?
Is there any Per report/Visual rendering kind of licensing model in any of the cases?
Say Production Deployment is for 100 users.
- For PB1 => 100 * $9.99/ month = $999/month
- For PB2 => $5005/month
- Definitely in this case first option is better. But is there any disadvantage of using PB1, other than the advantage that I might have dedicated resources(in case of PB2) for my workspace.
Is any of embedding going to be deprecated in coming future?
Does PB2 necessarily require Power BI premium? Because Once I register my Custom Web APP in AAD, I can share URL with anyone in my organization. And then the users can use the app to see embedded reports.
How Power BI restricting the webapp to not work without Power BI premium license for Production Deployment in case of PB2?

Thanks

Kuldeep

Re: Power BI Embedded

Anonymous — Fri, 23 Jun 2017 07:58:49 GMT

Power BI Embedded will die according to https://powerbi.microsoft.com/en-us/blog/microsoft-accelerates-modern-bi-adoption-with-power-bi-premium/

The benefit of embedding is that you can handle the users in your application and have not to add them manually to a subscription. Also some other benefits are coming with reserved capacity, if they pay out or not for you depends on your case. Anyway there will be no choice for embedding in the future.

Your case PB2 requires premium.

Re: Power BI Embedded

kuldeep_kumar — Fri, 23 Jun 2017 13:51:57 GMT

@Anonymous Thanks for the response.

If I am not wrong Power BI Embedded Azure is going to deprecate , but embedding would continue with Power BI Rest API and Embedded client lib

Re: Power BI Embedded

Anonymous — Fri, 23 Jun 2017 13:54:57 GMT

Yes that is correct. The Product of "Power BI embedded" is going to be deprecated. Embedding is from now on supported by the PowerBI Service. The APIs are merged to one API now. They C# part of the API is running as "V2".

Re: Power BI Embedded

kuldeep_kumar — Fri, 23 Jun 2017 14:04:06 GMT

So now we have two scenarios.

1) Users owns data (PB1)

2) App owns data (PB2)

So in case of PB2 I still have doubts

Is there any Per report/Visual rendering kind of licensing model in any of the cases?
In case of PB2, what I did is :
- Registered my webapp in Azure AD
- Share the URL with all users
- Users can see embedded reports
- Where do I require Power BI premium license in this case, cause users are already available to see the reports.

Re: Power BI Embedded

Eric_Zhang — Sat, 24 Jun 2017 07:07:22 GMT

@kuldeep_kumar wrote:

So now we have two scenarios.

1) Users owns data (PB1)

2) App owns data (PB2)

So in case of PB2 I still have doubts

Is there any Per report/Visual rendering kind of licensing model in any of the cases?

In case of PB2, what I did is :

Registered my webapp in Azure AD

Share the URL with all users

Users can see embedded reports

Where do I require Power BI premium license in this case, cause users are already available to see the reports.

@kuldeep_kumar

I think it is a license issue, you can develop PB2 with a pro license, however when promoting your solution to production, you need to purchase a premium license. Also, the different premium capacities determin the performance. See this link.

Re: Power BI Embedded

kuldeep_kumar — Wed, 28 Jun 2017 08:27:30 GMT

@Eric_Zhang Thanks

But as per the link given
If you are using a separate tenant for development, then you will need to make sure your app workspaces, along with dashboards and reports, are available in your production environment.

what exactly production environment means. Because for development purpose, I have created custom AAD in my portal account and registered the app.