The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredCompete to become Power BI Data Viz World Champion! First round ends August 18th. Get started.
Solved! Go to Solution.
Hi @Umram,
As we can see from the document, Power BI Embedded price depends on the node type and the number of nodes. So even the customer doesn't use it, Power BI Embedded will charge it unless the capacity is paused.
The question is how you can buy proper capacities for your customer now. Please download the white page from this page.
>>>Refer to the “How to plan capacity for Power BI Embedded” white paper for a description of v-cores.
You will find how to forecast the usage and estimate the nodes. Don't worry, you can scale-up or scale-down the Capacity as you need.
Best Regards,
Hi @Umram,
As we can see from the document, Power BI Embedded price depends on the node type and the number of nodes. So even the customer doesn't use it, Power BI Embedded will charge it unless the capacity is paused.
The question is how you can buy proper capacities for your customer now. Please download the white page from this page.
>>>Refer to the “How to plan capacity for Power BI Embedded” white paper for a description of v-cores.
You will find how to forecast the usage and estimate the nodes. Don't worry, you can scale-up or scale-down the Capacity as you need.
Best Regards,
It needs to be billed on an API-call or volume basis and should be elastic -- like IoT-Hub or Event-Hub -- starting at 0. If I have a great solution in Power BI that I embed and publish, I still do not have a guaranteed set of users and, as such, a significant budget based on users. Also, I cannot predict when my users will use the system (worldwide). Delivering the system and recruiting users/usage for it should be independent of another: usage-based services should start around 0 and ramp smoothly.