Power BI Embedded Licensing

[ITM6107]

I have seen a lot of posts regarding licensing of Power BI Embedded, but nothing that describes the distribution model we are looking at.

We would like to integrate Power BI Embedded reports on our commercial web app, which is licensed to end users as an on-premise application. End users would then be able to publish their own Power BI reports, using their existing Azure Services portal account and keys. Any rendering charges would be paid by the end users, as owners of their own Azure portal subscription. 

Would this type of distribution model be acceptable within the Power BI Embedded licensing model?

Thanks in advance for any suggestions. 

[v-sihou-msft]

@ITM6107

Licensing for Microsoft Power BI Embedded is on the developer of the app that is consuming the visuals, and are charged to the subscription that owns those resources. It's not for each end users. You can't have each user create its own Power BI reports, and charge them for renders with their own Azure portal subscription. It only charges developers subscription. Your distribution model is not acceptable. For more information, please see: https://azure.microsoft.com/en-us/documentation/articles/power-bi-embedded-what-is-power-bi-embedded...

Regards,

[ajithmg]

 @v-sihou-msft

Thanks for the clarification on the Power BI embedded licensing. Could you confirm whether the below scenario is a correct understanding of the licensing.

We have power BI Pro users in the organization and admin users who generates the report and publish it an Azure Power BI workspace collection. This is consumed by another Azure web application and there are internal users who access these reports from the web app. None of these are Power BI pro users, they are purely the end web app users. So in this scenario, we shall be charged for the Azure Power BI embedded user sessions at $5/100 session pack and there are no additional Power BI licenses to be purchased.

[ITM6107]

@v-sihou-msft

Thanks for the reply.

I have already seen that link and it does not contain any reference to the type of distribution model we are looking into.

Just to make things clear, we are not planning on charging the end user for any renders. They will pay for their own renders directly their through own Azure subsription. We are not going to receive any compensation for those renders.

If we cannot use Power BI Embedded, what other option do have?

[Vicky_Song]

@ITM6107, I'm sorry that I'm still a little bit confused about your issue. 

In your initial post, you said "End users would then be able to publish their own Power BI reports, using their existing Azure Services portal account and keys." Do you mean these end users will publish their own Power BI reports to PBI Service or embed their reports in the app? If you mean embed their reports in the application, in this situation, these users are not end users, they are actually developers. Then rendering charges would be paid by these end users (actually developers), as owners of their own Azure portal subscription. 

And in your last post, you said "Just to make things clear, we are not planning on charging the end user for any renders. They will pay for their own renders directly their through own Azure subscriptions."

So, for the "End users" you mentioned who can publish PBI reports, do you want them to pay for the Embedded or not?  

[ITM6107]

@Vicky_Song

Thank you for your reply. 

The end users will publish their own Power BI reports using our app, which is licensed to them. Our app provides distribution and subscription capabilities and is an on-premise licensed web app. So the end user will design their own Power BI reports, then publish them through our app. Our applicaiton would provide the ability to view and render these Power BI reports using our own interface.

The end user has an Azure subscription already and will pay for the rendering fees themseleves.

Can we use Power BI Embedded in this scenario?