CU Utilization Above 100% Due to Copilot

Hi tarima,
Thank you for using Microsoft Fabric Community Forum.

I understand your concern regarding the unexpected spike in CU utilization above 100%. This can occur when Copilot initiates background tasks such as schema analysis or query preparation, even if no users are actively engaged. While disabling Copilot stops new sessions, it does not terminate queries that have already started, which may result in continued high utilization.

To verify this, please review the Capacity Metrics app or the Activity Log in your workspace. Often, the two “users” you notice are system principals associated with Copilot or other background processes, rather than actual individuals. Examining these logs should clarify whether the activity is system-generated.

Currently, there is no direct method to terminate Copilot workloads once initiated. If high utilization persists, you may consider temporarily pausing or scaling the capacity to clear active operations; however, this will impact all workloads on that capacity. For ongoing or stuck operations, it is advisable to submit a support ticket to the Fabric product team for assistance in identifying and stopping these background jobs.

If Copilot is unnecessary for your environment, keeping it disabled at the admin level will prevent future unexpected activity. Additionally, configuring alerts for CU utilization thresholds in Fabric can help you proactively manage and respond to usage spikes.

You may go through the official documents provided below:
Fabric Copilot capacity - Microsoft Fabric | Microsoft Learn
Monitor and manage copilot capacity | Microsoft Learn

Regards,
Sahasra.