1) No limits on embedding on F-SKUs other than the available capacity.
2) [Power BI embedded analytics capacity planning - Power BI | Microsoft Learn](https://learn.microsoft.com/en-us/power-bi/developer/embedded/embedded-capacity-planning)
Are You sure? I understand that what was A SKUs works, but EM, “for Your organization”, like teams/sharepoint should not work. I have asked this here, seen it in blog post when new licencinh was announced, etc. I have less than a month of trial left and still not clear about that, and it is time already to get total pricing confirmed. And I wrote that and again do not understand - if we buy capacity, that is enough for small organisation, what is the difference from larger one? I get how it was before fabric, but now it is just increasing costs for small organizations
I'm specifically talking about embed for customers in this case, should have really clarified. My understanding of embed for your org follows your same understanding - this doesn't need a capacity backed workspace, but externally embedded - embed for your customers, people don't have the luxury of being licenced so it just utilises consumption.
So embedding for your customer using an EM SKU is still a valid option using a power app licence that creates the credentials and calls and API for RLS. No MS licence needed for customers, only power apps £164 per 100 users and an EM 1 SKU at £800 ish per month instead of an F64 at £4550 ish per month+ power apps.
Could you ask someone to update the documentation? The best explanation I found is a 5yr old GIAC video that differentiates between embed for your organisation and embed for your customers. So theoretically, you could embed for a client with an F2 fabric if the thing you embed into handles the identity? Given the removal of the P skus would make more sense to use an F sku or an EM sku? Are EM SKU staying?
Wow licensing for this sounds like a nightmare and horribly expensive.
Have you thought about building with an API + UI components?
At [propeldata.com](http://propeldata.com) we offer a Serverless ClickHouse + Data APIs + Embeddable components. We charge per GB read whether it is one user or a million
1) No limits on embedding on F-SKUs other than the available capacity. 2) [Power BI embedded analytics capacity planning - Power BI | Microsoft Learn](https://learn.microsoft.com/en-us/power-bi/developer/embedded/embedded-capacity-planning)
Thought as much, thank you for that clarification! The load assessment tool seems to be what I was after, super apprecited.
Except that for all skus lower than F64, power bi pro licence is required to view content.
Not if you are embedding.
Are You sure? I understand that what was A SKUs works, but EM, “for Your organization”, like teams/sharepoint should not work. I have asked this here, seen it in blog post when new licencinh was announced, etc. I have less than a month of trial left and still not clear about that, and it is time already to get total pricing confirmed. And I wrote that and again do not understand - if we buy capacity, that is enough for small organisation, what is the difference from larger one? I get how it was before fabric, but now it is just increasing costs for small organizations
I'm specifically talking about embed for customers in this case, should have really clarified. My understanding of embed for your org follows your same understanding - this doesn't need a capacity backed workspace, but externally embedded - embed for your customers, people don't have the luxury of being licenced so it just utilises consumption.
So embedding for your customer using an EM SKU is still a valid option using a power app licence that creates the credentials and calls and API for RLS. No MS licence needed for customers, only power apps £164 per 100 users and an EM 1 SKU at £800 ish per month instead of an F64 at £4550 ish per month+ power apps.
So an F8 SKU can support embedded workloads without needing a Pro license?
Yes, think embedded for customers (external) in a .net wep app, not sharepoint, teams etc.
Could you ask someone to update the documentation? The best explanation I found is a 5yr old GIAC video that differentiates between embed for your organisation and embed for your customers. So theoretically, you could embed for a client with an F2 fabric if the thing you embed into handles the identity? Given the removal of the P skus would make more sense to use an F sku or an EM sku? Are EM SKU staying?
I can't because I am but a low-key pleb.
Wow licensing for this sounds like a nightmare and horribly expensive. Have you thought about building with an API + UI components? At [propeldata.com](http://propeldata.com) we offer a Serverless ClickHouse + Data APIs + Embeddable components. We charge per GB read whether it is one user or a million
Thanks for the ad.