Azure PostgreSQL server is stuck in 'updating' state

IgorU-3602 20 Reputation points
2026-06-04T21:24:17.79+00:00

I have a Flexible PostgreSQL server in my development subscription which is stuck in updating state after an attempt to scale it down.

There should be no long-running queries, because the server isn't actively used.

Can you please help?

Thanks!

Azure Database for PostgreSQL
Answer accepted by question author
SAI JAGADEESH KUDIPUDI 3,650 Reputation points Microsoft External Staff Moderator
2026-06-08T09:40:46.98+00:00

Hi @IgorU-3602 ,

The server remained in the 'Updating' state longer than expected due to an underlying issue where the VM containers became unhealthy during the maintenance operation. Our Product Group has taken action and restarted the impacted containers.

The server is now recovering and should return to a Ready state shortly. We will continue to monitor to ensure stability.

Please let us know if you still face any issues.

Was this answer helpful?

1 person found this answer helpful.
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Rayyan Fawad 1,170 Reputation points
    2026-06-04T21:30:52.9133333+00:00

    Hi Igor, hitting a persistent 'Updating' hang on an Azure PostgreSQL Flexible Server after a scale-down attempt usually means the control plane operation has decoupled from the underlying compute instance, effectively locking the ARM resource. Since you’ve confirmed there are no long-running queries or active workloads blocking the operation, the platform is likely stuck waiting on an internal infrastructure timeout that can take hours to clear on its own. To force a resolution without waiting, try running an explicit restart command via the Azure CLI (az postgres flexible-server restart), as firing a direct management operation can sometimes override the stuck state. If the CLI rejects the command because the resource is locked in an updating transition, you will need to open a quick support ticket in the Azure Portal so an engineer can issue a backend force-cancel on the provisioning state and safely release your server.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.