Premium EM SKU vs PBI Pro -downsides?

[OneWithQuestion]

Looking at the newer offerings for PBI Premium EM SKU (as opposed to Premium P that starts at $5K a month) I am wondering how valid it would be to use that inplace of PBI Pro licenses.

Basically: does the end user lose any functionality in Premium EM that they have in PBI Pro (export data, save and reset filters, etc...).  Other than no longer being able to go to Powerbi.com to see their dashboards?

Assuming we already have O365 / SPO then we could post all our PBI Pro dashboards that we currently have deployed in PBI work spaces and apps into SPO via the Premium EM SKU, yes?

Meaning we would no longer have any users accessing PowerBI.com but instead they would all navigate to whatever SPO  / teams page we have setup for them to view their dashboards on, is that correct?

Do they still retain full functionality with exporting data from PBI, changing pages, etc...?

[v-shex-msft]

HI @OneWithQuestion ,

According to your description, I think you are misunderstood premium license.

Premium license is for tenant, it will provide specific capacity which allow you to publish your contents to it so that other users case access these contents without pro licenses. (power bi sharing features required pro license)

Premium EM is a specific version for embedded feature, you can take a look at following links to know more about these: Frequently asked questions about Power BI Embedded  What is Power BI Premium?

#1, If they are in the premium workspace, they can use all pro feature without license. If they are in personal workspace, they only has free features.

#2, As document said, this feature requires pro or above license.

#3, Nope, they can view power bi contents at both power bi and sharepoint site.

#4, Yes, they still have full free functions on power bi service side.

Regards,

Xiaoxin Sheng

[OneWithQuestion]

What about PowerBI.com applications how I can create a workspace, then deploy it as an App.

Can I do that with the EM licenses, or would I have to deploy those to Teams sites in SPO instead?