Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hi,
I'm trying to make sense of the different kind of Power BI Embedded SKUs and what they are good for. As far as I understand if I want to make use of Azure AD Authentification I have to use "user owns the data" method, since the user has to login instead of using a app registration. For this scenario I can only use Power BI Premium Capacity, since Power BI Embedded is not supporting "user owns data". There are two SKUs to choose from EM-SKU and P-SKU. So I have a custom application, where I want to embed reports and make it accessible for internal audience, that have to login with Azure AD first.
1. What I don't understand here, the internal audience who will access the reports later on don't need a power bi license right? Or is it only for P-SKU and not for EM-SKU (just view the reports not access power bi applications)?
2. Is EM-SKU enough if the audience should only view the reports or do you need a P-SKU for that?
3. Only for publishing you need a power bi premium license?
4.Is it also possible if you have a pro license?
5. In this link under comparison of both methods: https://learn.microsoft.com/en-us/power-bi/developer/embedded/embedded-analytics-power-bi#embed-for-.... What is meant with "Each app user needs a Power BI license"? I thought according my understanding above, the audience does not need a license?
it's not "owner owns data", It's the decision between "app owns data" and "user owns data". Based on that decision the licensing is different.
Power BI embedded analytics overview - Power BI | Microsoft Learn
Embed for your customers |
Embed for your organization
|
---|---|
Also known as app owns data |
Also known as user owns data |
Hi,
of course I mean User owns data.