Fabric capacity stuck in Pausing, resume rejected with "Service is not ready to be updated"

Question

my capacity stuck for several hours in the following state, and i cannot pause or resume it:

Current State: State = Pausing

ProvisioningState = Updating

Answer 1

Hello Suchkov Sergey

Could please share the error details and also confirm which endpoint you have configured if it is managed or private. MS Fabric is currently not supported in the Q&A forums, the supported products are listed over here Supported products on MS Q&A (more to be added later on).

You can ask the experts in the dedicated MS Fabric community forum.

Can you please open as a new thread in MS Fabric community: https://community.fabric.microsoft.com/t5/General-Discussion/bd-p/ac_generaldiscussion

For better visibility and quicker triage by the Fabric engineering and community experts, Could you please post this issue in the Microsoft Fabric Community under the Fabric platform / Capacity management category?

Microsoft Fabric Community: https://community.fabric.microsoft.com/

Please also include:

1. Capacity name and region
2. Current State and ProvisioningState
3. How long it has been stuck in Pausing
4. Any recent pause/resume/scale attempts

Answer 2

A Fabric capacity stuck in the Pausing / Updating state and rejecting resume with messages like “Service is not ready to be updated” is effectively in an unstable provisioning state. The supported actions from documentation are:

1. Verify the capacity state in Azure Portal
   • Go to the Azure portal.
   • Open Microsoft Fabric and select the affected capacity.
   • Confirm whether the UI still shows Pausing or if it has moved to Paused or Active.
2. Try a controlled pause/resume cycle
   • If the portal allows it, attempt:
     • Pause the capacity (if the button is enabled), confirm the action.
     • Wait a few minutes after it reaches Paused.
     • Then Resume the capacity and confirm.
   • Resuming should return the capacity to a healthy state and resume billing; content becomes available again once resumed.
3. Use REST APIs if the portal buttons fail
   • If the portal keeps rejecting the operation but the resource is reachable, call the Fabric capacity REST APIs:
     • Pause or suspend your capacity
     • Resume your capacity
   • Ensure the caller has the required Azure RBAC permissions:
     • Microsoft.Fabric/capacities/read
     • Microsoft.Fabric/capacities/write
     • Microsoft.Fabric/capacities/suspend/action
     • Microsoft.Fabric/capacities/resume/action
4. Check for throttling/overload and clear it
   • If the capacity is overloaded and throttled, pausing and then resuming is the documented self-service recovery path:
     • Pausing collects payment for the spike and resets throttling.
     • After a successful resume, the capacity should be in a clean state.
5. Ensure no dependent operations are blocking
   • If workspace capacity reassignment is in progress or recently failed, make sure:
     • The source capacity (this one) is not deleted or paused mid-migration.
     • No reassignment is currently running that might be changing capacity state.
   • If reassignment failures with “retries exhausted” occurred, first ensure the capacity is stable (not being scaled or paused) and then retry the reassignment only after the capacity is healthy.
6. If the state does not change for an extended period
   • A capacity stuck for several hours in Pausing / Updating with all operations rejected indicates a backend provisioning issue that cannot be resolved from the portal alone.
   • In this case, open a support ticket with Microsoft, include:
     • Capacity ID and region.
     • Timeline of when Pausing started.
     • Any failed pause/resume or API attempts and their error messages.

Once Microsoft clears the provisioning state, use a normal Pause → Resume cycle to confirm the capacity transitions cleanly between states and that workloads (Data Warehouse, mirroring, etc.) behave as expected after resume.

---

References:

• Pause and resume your capacity
• Pause and resume in Fabric Data Warehouse
• Understanding how Fabric capacity throttling impacts Activator
• Capacity reassignment restrictions and common issues
• Troubleshoot Fabric mirrored databases