**[CRITICAL] Azure PostgreSQL Flexible Server stuck in 'Updating' for 90 Minutes

Hello Tudor Moscalu

Greetings! Thanks for raising this question in Q&A forum.

I completely understand the urgency here a PostgreSQL Flexible Server stuck in "Updating" for 90+ minutes during a live outage is a critical situation that needs immediate action. Please note that as Q&A forum volunteers, we are not able to cancel or restart backend operations directly, but I want to help you get to the right place as fast as possible. Let me walk you through everything you can do right now.

Step 1: Check Azure Service Health for West US 2 First

Before anything else, check if there is an active platform incident in West US 2 that may be causing the stuck update. Go to https://status.azure.com and look for any active incidents under Azure Database for PostgreSQL in West US 2. If there is a platform incident, Microsoft is already working on it and your server should recover once the incident is resolved.

Step 2: Open a Free Basic Support Ticket Immediately — This is Your Fastest Path

Even without a paid support plan, every Azure subscription includes Basic support which covers service outages and stuck provisioning operations. Go directly to https://aka.ms/azuresupport and click New support request. Fill in the following issue type: Technical, Subscription: your subscription, Service: Azure Database for PostgreSQL, Problem type: Server Administration or Availability, Problem subtype: Server stuck in Updating state. Then click Next and describe the situation. Mark it as Severity A Critical Business Impact since you have an active outage. A Basic support ticket for a service outage will be picked up by the on-call Azure team and they can cancel or force-complete the stuck operation from the backend.

Step 3: Upgrade to a Developer Support Plan Right Now to Get Phone Support

If you are unable to get a response fast enough via the portal ticket, consider upgrading to the Developer support plan ($29/month) or Standard support plan ($100/month) directly from the Azure Portal under Help + Support → Support plans. The Standard plan gives you 24/7 critical business support with a 1-hour initial response time for Severity A issues. You can upgrade instantly and immediately open a Severity A ticket.

Step 4: Check the Activity Log for the Stuck Operation Details

While waiting for support, go to the Azure Portal, navigate to your PostgreSQL Flexible Server, and click Activity log in the left menu. Find the Update server operation that is stuck and note down the Operation ID and Correlation ID from the log entry. Include these in your support ticket they allow the Azure Database team to find and cancel the specific stuck backend job instantly.

Step 5: Check Server Connectivity in the Meantime

Even when a PostgreSQL Flexible Server shows "Updating" in the portal, the database itself may still be accepting connections depending on what operation triggered the update. Try connecting to your server using your normal connection string. If the database is responding, your application may still be able to operate while the portal status catches up. Common operations like parameter changes and minor version updates sometimes leave the portal in a stuck state while the server itself is healthy.

Step 6: Check for Any Maintenance Window or Automatic Update in Progress

Go to your server in the Azure Portal, click on Maintenance in the left menu, and check if an automated maintenance window was scheduled. Azure sometimes applies security patches or minor version updates automatically, and these can take 60–90 minutes on larger servers. If this is the case, the server will return to Available once the maintenance completes on its own.

Please open the support ticket right away at https://aka.ms/azuresupport that is the only channel through which the Azure backend team can intervene in the stuck operation and resolve your outage.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.