Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
My Organization has recently implemented Office 365 and a new SharePoint for roughly 430 employees.
Given the scale of our business, the Power BI Premium and Power BI Pro Licensing cost for all 430 employees is too much and something that we cannot make work at this time.
I have researched the new Power BI Embedded (ISV) as a potential solution to use Power BI on our SharePoint pages and pay for capacity and a few Pro Licenses, but have concerns as to whether or not Power BI Embedded will have issues showing on SharePoint and Office 365 as its an organization and not technically customer-facing.
It would be great if someone could confirm that this option would work on SharePoint without the dreaded "content is unavailable." If not the only option is Power BI Premium which is too much cost for our organization's size.
Solved! Go to Solution.
Hi @ehamrick,
Here is a good article which clearly explains the difference between A, EM and P SKUs, and what to use when.
What to use when
Sharing capabilities:
PBI Embedded A PBI Premium EM PBI Premium P Embed PBI Reports in your own application Embed PBI Reports in your own application Embed PBI Reports in your own application Embed PBI Reports in SaaS applications (SharePoint, Teams) Embed PBI Reports in SaaS applications (SharePoint, Teams) Share Power Reports, dashboards and datasets through Power BI Apps (workspaces) Ad hoc dashboard sharing from personal workspaces With the addition of the Power BI Embedded capacity based SKUs, many of the concerns around Premium pricing have been addressed. I would still like to see all EM SKUs available monthly, and to see a “P0” premium SKU, but it’s fairly clear as to which scenarios call out for which licenses.
An ISV that is embarking on the use of Power BI embedded will at the very least need a Power BI Pro license. When development gets to the point where sharing with a team is necessary, a Power BI Embedded A SKU can be purchased from Azure. Once 24/7 availability is required, the ISV may wish to switch to an Premium EM capacity. An ISV should never require a P SKU unless capacity demands it, or they have additional requirements.
An organization that has a few data analysts or Power Users that need to share reports with a broader audience would likely be well served with one of the EM SKUs. This scenario assumes that the organization is also using SharePoint Online, Microsoft Teams, or both. This approach will allow the power users (who will require a Pro license as well) to embed Power BI content within a SharePoint page or a Microsoft Teams tab where it can be accessed by users without a Pro license. This organization would need to include more than 63 users accessing the reports to be financially viable.
Finally, larger organizations with a significant investment in Power BI, or organizations that don’t currently utilize SharePoint Online or Microsoft Teams would benefit from a Premium P capacity. With this, the Power BI interface could be utilized by end users to access shared content without a Pro license. Given it’s monthly cost, compared to the monthly cost of Pro, the organization would need to have at least 500 active report consumers for this approach to practically considered.
Regards
Hi @ehamrick,
Here is a good article which clearly explains the difference between A, EM and P SKUs, and what to use when.
What to use when
Sharing capabilities:
PBI Embedded A PBI Premium EM PBI Premium P Embed PBI Reports in your own application Embed PBI Reports in your own application Embed PBI Reports in your own application Embed PBI Reports in SaaS applications (SharePoint, Teams) Embed PBI Reports in SaaS applications (SharePoint, Teams) Share Power Reports, dashboards and datasets through Power BI Apps (workspaces) Ad hoc dashboard sharing from personal workspaces With the addition of the Power BI Embedded capacity based SKUs, many of the concerns around Premium pricing have been addressed. I would still like to see all EM SKUs available monthly, and to see a “P0” premium SKU, but it’s fairly clear as to which scenarios call out for which licenses.
An ISV that is embarking on the use of Power BI embedded will at the very least need a Power BI Pro license. When development gets to the point where sharing with a team is necessary, a Power BI Embedded A SKU can be purchased from Azure. Once 24/7 availability is required, the ISV may wish to switch to an Premium EM capacity. An ISV should never require a P SKU unless capacity demands it, or they have additional requirements.
An organization that has a few data analysts or Power Users that need to share reports with a broader audience would likely be well served with one of the EM SKUs. This scenario assumes that the organization is also using SharePoint Online, Microsoft Teams, or both. This approach will allow the power users (who will require a Pro license as well) to embed Power BI content within a SharePoint page or a Microsoft Teams tab where it can be accessed by users without a Pro license. This organization would need to include more than 63 users accessing the reports to be financially viable.
Finally, larger organizations with a significant investment in Power BI, or organizations that don’t currently utilize SharePoint Online or Microsoft Teams would benefit from a Premium P capacity. With this, the Power BI interface could be utilized by end users to access shared content without a Pro license. Given it’s monthly cost, compared to the monthly cost of Pro, the organization would need to have at least 500 active report consumers for this approach to practically considered.
Regards
Thanks for the reply, I had just stumbled upon the same article quoted here and your right it solves everything we are looking for!
my only question is why isn't Microsoft advertising EM1-3 anywhere?
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.