topic Re: CU Utilization Above 100% Due to Copilot in Fabric platform

CU Utilization Above 100% Due to Copilot

tarima — Fri, 22 Aug 2025 15:41:48 GMT

Our CU background utilization started rising and eventually went above 100%.

Usually, it's around 10%. The culprit is Copilot.

No one was on the system at that time (9 pm local time) so I'm not sure why Copilot started. I disabled Copilot but utilization hasn't gone down. Any help with stopping Copilot and bringing our CU utilization down is greatly appreciated!!!

Re: CU Utilization Above 100% Due to Copilot

tarima — Fri, 22 Aug 2025 16:07:52 GMT

I am also unable to determine who the two users are.

Re: CU Utilization Above 100% Due to Copilot

tarima — Fri, 22 Aug 2025 19:13:50 GMT

Does anyone know how to kill that Copilot in Fabric operation?

Re: CU Utilization Above 100% Due to Copilot

v-sgandrathi — Mon, 25 Aug 2025 04:49:47 GMT

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.

Re: CU Utilization Above 100% Due to Copilot

v-sgandrathi — Thu, 28 Aug 2025 09:55:58 GMT

Hi tarima,

I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.

Thank you.

Re: CU Utilization Above 100% Due to Copilot

v-sgandrathi — Sun, 31 Aug 2025 12:50:40 GMT

Hi tarima,

we haven't heard back from you regarding our last response and wanted to check if your issue has been resolved.
If you need any further assistance, feel free to reach out.

Thank you.

Re: CU Utilization Above 100% Due to Copilot

v-sgandrathi — Wed, 03 Sep 2025 07:01:29 GMT

Hi tarima,

We wanted to follow up since we haven't heard back from you regarding our last response. We hope your issue has been resolved.

If you need any further assistance, feel free to reach out.

Thank you for being a valued member of the Microsoft Fabric Community Forum!