Forum Discussion
Does Microsoft Fabric Automatically Autoscale SKUs Based on Compute Demand?
In Microsoft Fabric, if I have an F2 SKU running and my queries or models need more compute capacity, does Fabric automatically autoscale my workload to a higher SKU (like F4), or do I need to manually upgrade/purchase a higher SKU to handle increased compute demands?
Is there any built-in mechanism for dynamic scaling within or across SKUs based on workload?
Thanks in advance!
No, Fabric doens;t scale automatically to your capapcity from F2 to higher SKU's like F4. For example if your workload crosses the compute limits of your F2 SKU, you may face throttling issues.
Yes, you can do automatic scaling by using Azure Logic apps read this blog Microsoft Fabric: Automating Fabric Capacity Scaling with Azure Logic Apps - BI Insight it might helps you.
and if you want, you can do manual upgrading also to higher SKU's. read more about scaling here Scale your Fabric capacity - Microsoft Fabric | Microsoft Learn
Please let me know if it helps you.
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!Hi GhulamMustafa ,
The answer from suparnababu8 is correct - Fabric doesn't automatically scale between SKUs. But let me clarify a few important points about Fabric's scaling behavior:
What happens within your SKU: Fabric does provide some automatic scaling within your purchased capacity. For example, if you have F4, it can dynamically allocate compute units across different workloads (notebooks, pipelines, etc.) based on demand.
What doesn't happen:
- No automatic upgrade from F2 to F4 when you hit limits
- When you exceed your SKU's capacity, you get throttling or queuing
- You'll see slower performance rather than automatic scaling up
Your scaling options:
Manual scaling: Upgrade/downgrade through the Fabric portal anytime. Takes a few minutes and you only pay for what you use.
Automated scaling via Logic Apps: As @Sree1994 mentioned, you can build automation using Azure Logic Apps to monitor capacity metrics and scale up/down based on usage patterns.
Bursting behavior: Some Fabric SKUs allow short-term bursting above baseline capacity, but this isn't the same as scaling to a higher SKU tier.
Best practice: Monitor your capacity utilization in the Fabric portal. If you consistently hit limits, consider moving to the next SKU tier rather than dealing with throttling.
Cost consideration: Since Fabric charges per second of compute, it's often better to scale up temporarily for heavy workloads rather than staying throttled on a smaller SKU.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.
7 Replies
- suparnababu8
Super User
No, Fabric doens;t scale automatically to your capapcity from F2 to higher SKU's like F4. For example if your workload crosses the compute limits of your F2 SKU, you may face throttling issues.
Yes, you can do automatic scaling by using Azure Logic apps read this blog Microsoft Fabric: Automating Fabric Capacity Scaling with Azure Logic Apps - BI Insight it might helps you.
and if you want, you can do manual upgrading also to higher SKU's. read more about scaling here Scale your Fabric capacity - Microsoft Fabric | Microsoft Learn
Please let me know if it helps you.
Thank you!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User! - burakkaragoz
Hi GhulamMustafa ,
The answer from suparnababu8 is correct - Fabric doesn't automatically scale between SKUs. But let me clarify a few important points about Fabric's scaling behavior:
What happens within your SKU: Fabric does provide some automatic scaling within your purchased capacity. For example, if you have F4, it can dynamically allocate compute units across different workloads (notebooks, pipelines, etc.) based on demand.
What doesn't happen:
- No automatic upgrade from F2 to F4 when you hit limits
- When you exceed your SKU's capacity, you get throttling or queuing
- You'll see slower performance rather than automatic scaling up
Your scaling options:
Manual scaling: Upgrade/downgrade through the Fabric portal anytime. Takes a few minutes and you only pay for what you use.
Automated scaling via Logic Apps: As @Sree1994 mentioned, you can build automation using Azure Logic Apps to monitor capacity metrics and scale up/down based on usage patterns.
Bursting behavior: Some Fabric SKUs allow short-term bursting above baseline capacity, but this isn't the same as scaling to a higher SKU tier.
Best practice: Monitor your capacity utilization in the Fabric portal. If you consistently hit limits, consider moving to the next SKU tier rather than dealing with throttling.
Cost consideration: Since Fabric charges per second of compute, it's often better to scale up temporarily for heavy workloads rather than staying throttled on a smaller SKU.
If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes. 
v-echaithraCommunity Support
Hi GhulamMustafa ,
Thank you suparnababu8 , burakkaragoz for the inputs.We’d like to follow up regarding the recent concern. Kindly confirm whether the issue has been resolved, or if further assistance is still required. We are available to support you and are committed to helping you reach a resolution.
Thank you for your patience and look forward to hearing from you.
Best Regards,
Chaithra E.- Ayush05-gateway
Helper II
What are the options for autoscaling in the case of reserved capacity? We're currently running on F64, reserved pricing, and have observed throttling during periods of high load — not tied to any specific time of day.
In such scenarios, we’d like to temporarily scale up by a few additional capacity units (CUs). Is there a way to use Logic Apps (or any other automation) to scale up when capacity usage exceeds 98%, and then automatically scale back down to the reserved capacity once usage drops below 100%?
Thanks,
Ayush
- Ayush05-gateway
What are the options for autoscaling in the case of reserved capacity? We're currently running on F64, reserved pricing, and have observed throttling during periods of high load — not tied to any specific time of day.
In such scenarios, we’d like to temporarily scale up by a few additional capacity units (CUs). Is there a way to use Logic Apps (or any other automation) to scale up when capacity usage exceeds 98%, and then automatically scale back down to the reserved capacity once usage drops below 100%?
Thanks,
Ayush
Shubham_rai955Microsoft Fabric does not automatically autoscale F SKUs (like F2) to higher SKUs based on compute demand by default.
Instead, Fabric offers two key built-in capabilities related to scaling:
Bursting: Temporarily allows workloads to exceed the licensed capacity up to 12x for short periods to handle spikes.
Smoothing: Spreads capacity usage over 24 hours to avoid sudden spikes in demand.
However, these do not dynamically upgrade your SKU or permanently scale your capacity. If you need more compute capacity, you must manually scale or upgrade your Fabric capacity SKU through the Azure portal.
There are options to automate scaling through tools like Azure Logic Apps, ARM templates, and PowerShell, where you monitor capacity consumption and trigger scale-up or scale-down actions. But this is a custom automation you have to set up and is not fully dynamic or instantaneous.
Autoscaling is currently available in Power BI Premium SKUs (P SKUs) but not fully integrated into F SKUs.
https://learn.microsoft.com/en-us/fabric/enterprise/scale-capacityHello ghua
I have been using the Fabric SKU auto scale logic for the past year. It works based on the real time compute demand. I hope this helps,
https://medium.com/@vineethmsngr/fabric-sku-autoscaling-using-azure-logic-apps-300cb5048286 https://medium.com/@vineethmsngr/fabric-sku-autoscaling-using-azure-logic-apps-300cb504828
