Isolate Fabric Copilot Operations to Dedicated Capacity
Currently, Copilot records Capacity Consumption on Capacity associated with artifacts that are using Copilot. Considering that Copilot Operations are categorized as background operations, this imposes huge risk of killing the Capacity when overconsuming for longer than 24 hours.
However, there is an exception for Power BI Desktop, where we could charge Copilot Operations against a Capacity, which could even be totally empty. To avoid the scenario where Copilot Abuse could impact the critical workloads on Capacities, it would be great to have an option to isolate all the Copilot Operations to dedicated Capacity.
This could be even greater if Copilot could be used on lower SKUs, and companies could decide how much money they want to pay for Copilot. Because, by all means it is not free and could be very dangerous.
Thank you in advance for reviewing my idea!
Paweł.
2 Comments
- fbcideas_migusrNew MemberStatus added:New
- AnonymousNot applicable
Good news! We shipped the Fabric Copilot Capacity option in January 2025. Check it out here:
Introducing Fabric Copilot capacity: Democratizing AI usage in Microsoft Fabric | Microsoft Fabric Blog | Microsoft Fabric
Recent ideas
SQL Analytics Endpoint host name - CNAME or defined alias
The host name for a SQL Analytics endpoint is ugly. They look like this: random_ugly_alphanumeric-random_ugly_alphanumeric.datawarehouse.fabric.microsoft.com The first segment looks like it...Mike_Diehl1 hour agoNew MemberNew27Views2likes1CommentFix links generated in multi tenant setups
When I log into Fabric, and I have access to multiple tenants, the links generated for things like monitoring URLs in pipeline runs do not include "ctid=<tenantguid>" query string value, which appear...jwisemanfs4 hours agoNew MemberNew3Views0likes0Comments