Forum Discussion
Helper IVHigh Copilot and AI cost
Hello AJAJ,
Thank you for posting your query in Microsoft Fabric Community Forum. Also, thanks to lbendlin , for those inputs on this thread.Copilot doesn’t charge based on how big your tables are. Even if the data is small, Copilot runs multiple background steps for every question a user asks. Because of that, the compute usage becomes a bit higher than what we normally expect with simple SQL or Power BI queries. So the cost you are seeing right now is normal behaviour.
When this goes to a bigger user base, the load comes mainly from the AI requests, not from the data size. That’s why higher capacities are usually suggested it’s just to handle the AI workload smoothly.
At the moment there isn’t any special setting to reduce Copilot-related cost. The best way is to limit who can use Copilot during the POC and keep checking the capacity metrics to understand where the usage is coming from.
Your current setup is fine, and you’re not using it incorrectly. This is simply how Copilot processes queries in the background.
Let me know if you want me to check anything specific.
Regards,
Community Support Team.
the simplest way to reduce it use less tokens. i think the ai copilot that you are currently using the just dumping the data into the context window of the model which is causing it to bloat and increase cost very rapidly. it is costly to run for even 1 user and here we are talking about about 300+ users. the best way is to give your ai some memory, and store intermidiate outputs there, aggregate the data before giving it to ai copilot and let math be math, do not let ai do the maths for you.