Forum Discussion
Solved
Fabric Capacity Pause
hi, I have the following questions regarding pausing/suspending a MS Fabric Capacity (F64, currently paid via Azure credits) from the Azure Resource Group management page:
- Maximum suspension duration. When I pause/suspend a Fabric Capactiy resource from the Azrue Resource Group portal, is there a maximum length of time it can remain in the "Suspended" state? is there any limit after which the capacity or its associated data would be automatically deleted or require re-provisioning?
- Validity of prior workloads during suspension. While the capacity is suspended, is the work/data previously produced by Fabric workloads preserved as-is, and will it remain fully valid and accessible once the capacity is resumed? Or is there any retension/expiration policy that could cause data or job history to be lost during the suspension period?
- Billing during suspension. Since we currently consume the F64 capacity through Azure credits, if we suspend the capacity, sill only Onelake storage costs continue to be charged during the suspension period, with all compute-related capacity charges stopped?
Please confirm exacty which cost components (if any) continue to accrue while the capacity is suspended.
Thank you....😢
Hi seoyeon123​ ,
pausing an F64 Fabric capacity is specifically intended to stop compute charges when the capacity isn't being used. A few distinctions are important:
- Maximum suspension duration
I don't see a Microsoft-documented maximum suspension period for an F-SKU capacity. Pausing doesn't delete or de-provision the capacity; you can resume it later. Microsoft describes pause/resume as a reversible operation, not a temporary deletion mechanism. - Data and existing Fabric items
Your OneLake data and Fabric items remain stored. However, while the capacity is paused, content assigned to it can become unavailable because the compute isn't running. Once you resume the capacity, the content becomes available again.
So I would distinguish data retention from data accessibility: pausing doesn't mean your Lakehouse/Warehouse data is deleted, but you shouldn't expect reports, queries, pipelines, etc. to operate while the capacity is suspended. - Billing
Your understanding is correct. When the capacity is paused, the compute billing meters for Fabric workloads stop, while OneLake storage continues to be billed on a per-GB basis. OneLake transactions against the paused capacity are rejected, so they don't generate CU consumption there.
I hope this helps!?
If so, consider leaving kudos or mark it as solution.Best regards!
- Maximum suspension duration
2 Replies
Hi,
- Maximum suspension duration: There is no maximum time limit; the capacity can remain suspended indefinitely without being automatically deleted or requiring reprovisioning.
- Workload and data validity: All OneLake data, item definitions, and historical job logs are preserved indefinitely and become immediately accessible once resumed.
- Billing during suspension: Compute charges stop completely, so you only continue paying for OneLake storage (plus any provisioned Azure networking/Private Endpoints and any one time settlement for previously smoothed compute). You have to consider Azure credits at this point because depending on your work load you can burn through credit for storage
Look for following components for credit usage after pausing the capacity.
- OneLake Standard Storage
- OneLake BCDR and Soft-Delete Storage
- Accrued smoothed compute carryforward (one-time settlement at pause)
- Azure Private Endpoints and Networking infrastructure (if provisioned)
- Azure Capacity Reservations (if purchased under a 1- or 3-year commitment since you are in pay as you go Azure credit based system this might not be applicable)
Hi seoyeon123​ ,
pausing an F64 Fabric capacity is specifically intended to stop compute charges when the capacity isn't being used. A few distinctions are important:
- Maximum suspension duration
I don't see a Microsoft-documented maximum suspension period for an F-SKU capacity. Pausing doesn't delete or de-provision the capacity; you can resume it later. Microsoft describes pause/resume as a reversible operation, not a temporary deletion mechanism. - Data and existing Fabric items
Your OneLake data and Fabric items remain stored. However, while the capacity is paused, content assigned to it can become unavailable because the compute isn't running. Once you resume the capacity, the content becomes available again.
So I would distinguish data retention from data accessibility: pausing doesn't mean your Lakehouse/Warehouse data is deleted, but you shouldn't expect reports, queries, pipelines, etc. to operate while the capacity is suspended. - Billing
Your understanding is correct. When the capacity is paused, the compute billing meters for Fabric workloads stop, while OneLake storage continues to be billed on a per-GB basis. OneLake transactions against the paused capacity are rejected, so they don't generate CU consumption there.
I hope this helps!?
If so, consider leaving kudos or mark it as solution.Best regards!
- Maximum suspension duration
