How to count the CU of Copilot operations in power bi

[Sophie__]

hello,

How to count the CU of Copilot operations in power bi how per day and per user ?

Regards,

Sophie

[Shubham_rai955]

Hi @Sophie__ , If my solution helped you to understand the solution of your problem, please mark it as a Solution, It will motivate me to help more.

[v-nmadadi-msft]

Hi @Sophie__ 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[Sophie__]

Hello @v-nmadadi-msft ,

Thank you for your helpful reply

Sophie

[v-nmadadi-msft]

Hi @Sophie__ 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[Shubham_rai955]

To track Copilot Capacity Units (CU) usage per day and per user in Power BI, currently there isn’t a built-in direct way to monitor Copilot CUs like in Fabric. Copilot usage in Power BI Premium is measured by tokens processed, and each request consumes CUs based on input and output tokens.

To get insights on Copilot consumption, you’d typically need to rely on your Power BI Premium capacity metrics and reports provided by your admin or billing tools that show overall capacity consumption spikes linked to Copilot usage. Detailed per-user or per-day tracking of Copilot operations CU is currently a Fabric feature and not exposed directly in standalone Power BI.

For more precise monitoring, you may want to discuss with your Power BI admin about advanced telemetry or audit logs, but native per-user/day Copilot CU reports are not available in standalone Power BI as of now.

[Sophie__]

hi @Shubham_rai955 ,

thanks for your answer.

i try to user Fabric Capacity Metrics model and filter on the opération Copilot in Fabric but i don't understand the calculation of sum_CU metric in  MetricsByItemandOperationDay table.

[Shubham_rai955]

The sum_CU metric in the MetricsByItemandOperationDay table of the Microsoft Fabric Capacity Metrics app represents the total Capacity Units (CUs) consumed by a specific item and operation on a particular day.

Here’s how the calculation and concept work:

• Capacity Unit (CU) measures compute power consumed, roughly proportional to CPU and memory usage over time.

• The metric sums usage over the collection period (often 30 seconds intervals) for the given operation and item.

• The calculation takes into account how many resources (vCores) the operation consumed and for how long.

• Copilot operations consume CUs based on token usage (input/output tokens), and these are aggregated into sum_CU.

• The sum_CU total is essentially the total compute resource seconds consumed to serve those operations.

Using the sum_CU metric helps admins assess the compute impact of Copilot (and other operations) on capacity, useful for scaling and cost planning.

For detailed formula or internal calculation logic, this is managed by Fabric’s telemetry backend and typically not exposed at granular level beyond the sum_CU aggregation shown in the app.

If you want to understand sum_CU related to your Copilot filtering:

• sum_CU = sum of all CU seconds consumed by Copilot requests for that day and user in the table.

• Filtering on “Copilot in Fabric” operations isolates the CU consumption caused by AI operations.

[tayloramy]

Hi @Sophie__, 

Capacity Metrics is where this data will come from. The other audit logs don't have CU usage in them. 

Remember that Fabric uses capacity smoothing, so some operations that only happen momentarily can be using CU for an extended period of time. Generally background operations are smoothed over a 24 hour window, and interactive over a 10 minute window, but there are exceptions. 

Right now there is no nice way to see only copilot data unless your admin sets up a capacity specifically for copilot and only allows copilot to run on that capacity. 

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.