Fabric Capacity Pause

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:

1. 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.
2. 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.
3. 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!