Forum Discussion
Advocate IICopilot using capacity despite not being active
Hi NotebookEnjoyer ,
since May, copilot features are available for all F SKUs and not only for F64 and higher.
We have experienced that some copilot features are now enabled by default and could therefore consume resources. For instance, both Fabric warehouse and SQL database items inherit a copilot auto complete capability which might be turned on by default now since it is available for your capacity.
You can check this by navigating to Settings --> Copilot --> Show Copilot completions and see if the toggle is turned on.
Hope this helps! 🙂
I see. Can confirm that it does not seem possible to disable code completion for a SQL endpoint since the option doesn't exist in the lakehouse settings.
What's possible is to disable copilot features on tenant/capacity level as specified in the documentation . This of course requires according user privileges. This will help you control your capacity usage in the short term.
Will be curious to see if other users face similar problems and if there is a way to disable auto completions on lakehouse level in a way that we are currently missing. 🙂
Advocate IISpot on, I'm in a SQL endpoint and see the button as expected in a "real" warehouse. However: Copilot is consuming capacity from a SQL endpoint (without me actively using it!) and I need to shut it off there. So what do I do?
Resolver IIII see. Can confirm that it does not seem possible to disable code completion for a SQL endpoint since the option doesn't exist in the lakehouse settings.
What's possible is to disable copilot features on tenant/capacity level as specified in the documentation . This of course requires according user privileges. This will help you control your capacity usage in the short term.
Will be curious to see if other users face similar problems and if there is a way to disable auto completions on lakehouse level in a way that we are currently missing. 🙂
- NotebookEnjoyer
I have done that and will carefully observe whether the capacity load disappears. From an UI perspective, Copilot is off. Thanks a lot!
Edit: The missing button in the SQL endpoint is still wrong though, I think. What if I don't want hidden capacity load while writing SQL queries but Copilot generally available?- ObungiNiels
HI NotebookEnjoyer ,
I am back with news! I revisited this problem and made the following observation:
When I check the settings of a lakehouse without schema, the copilot tab is missing.
In a lakehouse with schema enabled, the copilot tab is there.
Could it be possible that your lakehouses were created without schema?
- NotebookEnjoyer
They were. But since Copilot still was using capacity in my schema-less lakehouse, that's kind of a moot point.