Forum Discussion
AI functionality using Power BI Dataset
- 6 months ago
Hi visheshjain
Your concern is valid. Copilot workloads can spike CU consumption quickly, especially on smaller SKUs like F2. While CU smoothing averages usage over 24 hours, throttling can still occur during short-term bursts if the instantaneous consumption exceeds the allocated capacity.
Hi,
Yes I went through the solutions provided and none of them really work.
I turned on surge protection but in that case copilot usage is very limited and if I use the entire capacity as a Copilot capacity then the report refreshes stop completeley.
I spoke to Microsoft over multiple tickets and they said that I have depleted my 'compute units' which even they cannot tell that how long will it take to normalize. I did deploy the Fabric Metrics Capacity app but still no answer to this questions.
Upgrading it to a F4 capacity will increase the number of 'compute units' but it will also have the same limitations with higher thresholds, not to mention the cost associated with the F4 capacity will be double.
Is there some way to use an MCP server with Power BI service since users will not have access to the desktop files.
Or we can create a custom visual, which will be connected to a LLM in the backend...I'm just spitballing here.
Thank you,
Vishesh Jain
In my experience you need at least a F128 for a meaningful Copilot experience. Even a F64 can be brought to its knees by a handful of concurrent Copilot users. Ask me how I know.
CU smoothing happens over a 24 hour period, mostly.
- visheshjain6 months ago
Impactful Individual
Hi lbendlin,
F128 is going to be super expensive (not to mention Microsoft's billing isn't as transparent...my F2 capacity has different daily cost, even when in paused state) and as you correctly pointed out if a F64 capacity can be brought to its knees, then even F128 might fall short at some point of time. Eventually, it is going to spoil our user's experiences, cause Copilot goes through CU units in a snap.
I am trying to avoid going the Copilot route and probably figure something out using Model Context Protocols (MCP) instead.
P.S. - CU smoothening happens MAY happen over 24 hour period, but I might have consumed some 2000% of my daily units or something or thats what the Microsoft advisor told me. LOL!
- v-aatheeque6 months ago
Community Support
Hi visheshjain
Your concern is valid. Copilot workloads can spike CU consumption quickly, especially on smaller SKUs like F2. While CU smoothing averages usage over 24 hours, throttling can still occur during short-term bursts if the instantaneous consumption exceeds the allocated capacity.
- v-aatheeque6 months ago
Community Support
Hi visheshjain
Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.