Forum Discussion
PowerBI embedded - sharing
Hi everyone,
I have got a workspace backed up by A1 embedded capacity. I thought that reports from such a workspace can't be shared in the service but they need to be embedded into a web app. However, I have got free PowerBI users cosuming these reports in PowerBI service or SharePoint online just fine. Am I missing something here? I would like some clarification before I advise my company not to buy P1 but just simply use A sku instead?
Thank you,
WJ
My testing shows that free users can consume content from a workspace backed up by A SKUtrue, from PBI perspective that workspace is a premium workspace therefore free users can come in.
MS documentation suggests that both content creators and consumers must have PRO license?I would say true again AFAIK. accessing power bi portal works for free users but it's not covered by free license.
8 Replies
- collinqSuper User
HI wojciech ,
The A sku is designed for organizations that are embedding into an application. The A capacity/sku is using Embedded Capacity specifically. The P sku allows you to do more and embed in more scenaries (like O365). You also pay hourly for A skus whereas a P sku is a monthly bill. This means it is possible for an A sku to "ramp up" and cost you way more than a P sku. Also, you will have to translate the A level of capacity and the P level (a P1 is equal to an A4).
- wojciechHelper II
Hi collinq,
Thank you very much for coming back to me.
I do understand a difference between A and P SKU, and the fact that P SKU offers more.
However, I don't understand why I can embed PBI reports from A SKU workspace into SharePoint. On your point around O365 integration, this should not work with A SKU, should it?
Thank you,
WJ
- collinqSuper User
Hey wojciech ,
You can embed with either an A or a P sku. Either one works for embedding. The big difference is that the A sku is scaleable - perhaps that is what you are encountering - that users are using it and all appears well. BUT, more users hitting that embedded product might be driving up the usage, and therefore the cost, of the A sku?
Normally, I would advise that you use the P sku since it is an established monthly cost and you won't have a sudden shocking increase one day/week/month.
In thinking through a number of different scenarios in my mind I guess it it theoretical that if you have somebody closing monitoring the A sku and pausing it now and then that might be a cheaper license but you do have to pay to have somebody babysitting it all the time.