Postgres Flexible Server stuck on updating state

Question

Postgres Flexible Server stuck on updating state

Dávid Vig 40

Hi,

Our Azure Database for PostgreSQL Flexible Server has been stuck in the

'Updating' state for over 90 minutes following a compute and storage tier

change operation (UpdateComputeAndStorage). The server is completely

unavailable and we are unable to perform any management operations.

Diagnostics performed:

CLI state check confirms 'Updating' state:

az postgres flexible-server show --name partnertechpsqldb \

--resource-group partnertech-rg --query "{state:state,sku:sku.name}"

→ Output: { "state": "Updating", "sku": "Standard_B1ms" }

Restart attempt failed:

az postgres flexible-server restart --name partnertechpsqldb \

--resource-group partnertech-rg

→ Error: (ServerIsNotReady) Restart and stop operations are only supported

on servers that are in 'Ready' state. Server 'partnertechpsqldb' is in

'Updating' state.

Resource lock check returned empty – no locks present.
No active incidents found on https://status.azure.com for Austria East.

Impact:

This is a test environment, however customer UAT is scheduled for

today/tomorrow and the environment is required to be available.

We do not have a paid technical support plan. Backend intervention is

required to cancel or force-complete the stuck UpdateComputeAndStorage

operation.

Could someone from the Azure PostgreSQL team please investigate and resolve

this on the backend?

Thank you.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Pilladi Padma Sai Manisha 11,715 Microsoft External Staff Moderator

Hi @Dávid Vig

Thank you for reporting this issue.

We investigated the backend operation and can confirm that the stuck UpdateComputeAndStorage operation has now been mitigated. The server should have transitioned back to a healthy state and become available for normal use.

Could you please verify that the server is now accessible and that your applications can connect successfully? If you continue to experience any issues, please share the current server status and any recent error messages so we can investigate further.

Please let us know if the still issue persists.

Pilladi Padma Sai Manisha 11,715 Reputation points Microsoft External Staff Moderator

2026-06-10T04:13:23.6833333+00:00

Hi @Dávid Vig
Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 2

Hello David !

Thank you for posting on MS Learn Q&A.

This is not something that can usually be fixed from the customer side once the Flexible Server is locked in Updating after UpdateComputeAndStorage.

The restart failure is expected because restart or stop operations are only supported when the server is in Ready state. At this point, I would not keep retrying restart, stop, scaling or delete operations, because the current provisioning workflow needs to either complete, fail, or be cleared by Azure backend support.

If the server uses private access or VNet integration check the delegated subnet for available IP addresses because subnet capacity issues have caused Flexible Server update/maintenance operations to get stuck in similar cases.

For immediate UAT mitigation, try creating a point-in-time restore or latest restore point to a new Flexible Server, if the restore operation is still available. PITR creates a new server and does not overwrite the existing one.

If the restore succeeds, point the UAT application to the restored server while Microsoft investigates the stuck original resource.

Azure support is required if the operation remains stuck.