Forum Discussion
Fabric CU Usage
- 1 year ago
Rica ederim, diğer kişilerin faydalanması için bundan sonrasına ingilizce devam edeceğim. 😊
Yes, you're right. If you're using the CUDetail page and summing up the CU values per day, that gives you a good estimate of daily usage. No need for custom DAX if you're sticking with the default metrics.
Now about the billing part:
- Threshold breaches (like hourly spikes) don’t automatically mean extra charges.
- What matters is whether your total daily CU usage exceeds the daily quota (in your case, ~5.5M CU for FT1).
- As long as your daily total stays under that limit, you won’t be billed extra, even if some hours spike above the average.
So you’re safe unless your daily usage consistently goes over the quota. But it’s smart to monitor those spikes — they can become an issue if they start pushing your daily total up.
Hi tolgakurt ,
Thanks for reaching out to the Microsoft Fabric Community. Also thank you burakkaragoz for your inputs.
You are correct the CUDetail table is the right place to look for per-interval CU usage, and aggregating from there gives you a good picture of daily CU consumption.
Regarding your main question:
- During the trial period (FT1), there is no billing, regardless of spikes or daily usage levels.
- In general Fabric capacity (including paid SKUs), you are not billed based on how much CU you consume on a given day.
- Instead, billing is based on the SKU tier (e.g., F64, F128) that your capacity is assigned to, and it’s charged per hour.
- Short-term usage spikes that do not cause capacity scale-up or reconfiguration will not trigger additional charges.
So, as long as you stay within your assigned capacity tier (even with some peak usage moments), there’s no extra cost beyond your base SKU rate. Monitoring daily average usage is still a good practice for long-term planning and sizing, especially when moving beyond the trial.
I hope this gives you an idea, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thankyou.