[CRITICAL] Azure PostgreSQL Flexible Server stuck in 'Updating' state for 3 days — Production Down

Question

[CRITICAL] Azure PostgreSQL Flexible Server stuck in 'Updating' state for 3 days — Production Down

Rumsan Associates 20

Environment

Service: Azure Database for PostgreSQL – Flexible Server
PostgreSQL version: 17
SKU: Standard_DC2eds_v5 (Confidential Compute)
Resource group: staging

Problem Description

Our PostgreSQL Flexible Server has been stuck in an Updating state for approximately 2–3 days. We did not initiate any changes — no SKU modification, no version upgrade, no configuration change was made by our team. The update appears to have been triggered automatically by Azure.

This has taken down our production environment and all dependent services are currently unavailable.

Current server state (verified via CLI):


az postgres flexible-server show \

  --name <resourc-name> \

  --resource-group staging \

  --query "{state:state, version:version, skuName:sku.name}"


{

  "skuName": "Standard_DC2eds_v5",

  "state": "Updating",

  "version": "17"

}

What we have tried

Attempted az postgres flexible-server restart — no effect, server remains in Updating
Checked activity logs via az monitor activity-log list — no clear error returned
Attempted to raise an Azure Support ticket — the portal only redirects to Q&A and does not allow us to open a ticket

Any help or guidance from the community or Azure engineers monitoring this forum would be greatly appreciated.

Saraswathi Devadula 16,040 Reputation points Microsoft External Staff Moderator

2026-05-05T11:06:05.95+00:00

Hello **Rumsan Associates

**Kindly I request you to please share the server details to mitigate the issue.

Rumsan Associates 20

{
    "apiVersion": "2025-08-01",
    "id": "/subscriptions/f6b92451-9d9d-4865-a045-c43eccedf5f5/resourceGroups/staging/providers/Microsoft.DBforPostgreSQL/flexibleServers/giga-staging",
    "name": "giga-staging",
    "type": "microsoft.dbforpostgresql/flexibleservers",
    "sku": {
        "name": "Standard_DC2eds_v5",
        "tier": "GeneralPurpose"
    },
    "location": "westeurope",
    "tags": {},
    "properties": {
        "replica": {
            "role": "Primary",
            "capacity": 5
        },
        "storage": {
            "type": "",
            "iops": 500,
            "tier": "P10",
            "storageSizeGB": 128,
            "autoGrow": "Disabled"
        },
        "network": {
            "publicNetworkAccess": "Enabled"
        },
        "privateEndpointConnections": [],
        "dataEncryption": {
            "type": "SystemManaged"
        },
        "authConfig": {
            "activeDirectoryAuth": "Disabled",
            "passwordAuth": "Enabled"
        },
        "fullyQualifiedDomainName": "giga-staging.postgres.database.azure.com",
        "version": "17",
        "minorVersion": "8",
        "administratorLogin": "giga_stage",
        "state": "Updating",
        "availabilityZone": "2",
        "backup": {
            "backupRetentionDays": 7,
            "geoRedundantBackup": "Disabled",
            "earliestRestoreDate": "2026-04-28T18:35:55.7829297Z"
        },
        "highAvailability": {
            "mode": "Disabled",
            "state": ""
        },
        "maintenanceWindow": {
            "customWindow": "Disabled",
            "dayOfWeek": 0,
            "startHour": 0,
            "startMinute": 0
        },
        "replicationRole": "Primary",
        "replicaCapacity": 5
    },
    "systemData": {
        "createdAt": "2025-10-30T09:56:19.5052007Z"
    }
}

Rumsan Associates 20 Reputation points

2026-05-06T06:05:49.17+00:00

I also tried to restore the database but i got this error during restore process

`` ```The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. (Code: ResourceDeploymentFailure, Target: /subscriptions/f6b92451-9d9d-4865-a045-c43eccedf5f5/resourceGroups/staging/providers/Microsoft.DBforPostgreSQL/flexibleServers/giga-staging-4-30)
Saraswathi Devadula 16,040 Reputation points Microsoft External Staff Moderator

2026-05-08T15:44:48.4033333+00:00

Hello **Rumsan Associates

Please be informed that the Standard_DC2eds_v5 (Intel V5 confidential compute SKU) is now deprecated. We should use the AMD V5 confidential SKUs, Dcadsv5 or Ecadsv5, in the WEU region instead.
Saraswathi Devadula 16,040 Reputation points Microsoft External Staff Moderator

2026-05-10T05:08:51.64+00:00

Hello **Rumsan Associates I hope you had the opportunity to review the information shared earlier, and I hope this information was helpful! If you still have questions, please let us know what is needed in the comments so that the question can be answered.

Your answer

Saraswathi Devadula 16,040 Reputation points Microsoft External Staff Moderator

2026-05-05T11:06:05.95+00:00

Hello **Rumsan Associates

**Kindly I request you to please share the server details to mitigate the issue.
Rumsan Associates 20 Reputation points

2026-05-06T04:36:35.4833333+00:00

{ "apiVersion": "2025-08-01", "id": "/subscriptions/f6b92451-9d9d-4865-a045-c43eccedf5f5/resourceGroups/staging/providers/Microsoft.DBforPostgreSQL/flexibleServers/giga-staging", "name": "giga-staging", "type": "microsoft.dbforpostgresql/flexibleservers", "sku": { "name": "Standard_DC2eds_v5", "tier": "GeneralPurpose" }, "location": "westeurope", "tags": {}, "properties": { "replica": { "role": "Primary", "capacity": 5 }, "storage": { "type": "", "iops": 500, "tier": "P10", "storageSizeGB": 128, "autoGrow": "Disabled" }, "network": { "publicNetworkAccess": "Enabled" }, "privateEndpointConnections": [], "dataEncryption": { "type": "SystemManaged" }, "authConfig": { "activeDirectoryAuth": "Disabled", "passwordAuth": "Enabled" }, "fullyQualifiedDomainName": "giga-staging.postgres.database.azure.com", "version": "17", "minorVersion": "8", "administratorLogin": "giga_stage", "state": "Updating", "availabilityZone": "2", "backup": { "backupRetentionDays": 7, "geoRedundantBackup": "Disabled", "earliestRestoreDate": "2026-04-28T18:35:55.7829297Z" }, "highAvailability": { "mode": "Disabled", "state": "" }, "maintenanceWindow": { "customWindow": "Disabled", "dayOfWeek": 0, "startHour": 0, "startMinute": 0 }, "replicationRole": "Primary", "replicaCapacity": 5 }, "systemData": { "createdAt": "2025-10-30T09:56:19.5052007Z" } }
Rumsan Associates 20 Reputation points

2026-05-06T06:05:49.17+00:00

I also tried to restore the database but i got this error during restore process

`` ```The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. (Code: ResourceDeploymentFailure, Target: /subscriptions/f6b92451-9d9d-4865-a045-c43eccedf5f5/resourceGroups/staging/providers/Microsoft.DBforPostgreSQL/flexibleServers/giga-staging-4-30)
Saraswathi Devadula 16,040 Reputation points Microsoft External Staff Moderator

2026-05-08T15:44:48.4033333+00:00

Hello **Rumsan Associates

Please be informed that the Standard_DC2eds_v5 (Intel V5 confidential compute SKU) is now deprecated. We should use the AMD V5 confidential SKUs, Dcadsv5 or Ecadsv5, in the WEU region instead.
Saraswathi Devadula 16,040 Reputation points Microsoft External Staff Moderator

2026-05-10T05:08:51.64+00:00

Hello **Rumsan Associates I hope you had the opportunity to review the information shared earlier, and I hope this information was helpful! If you still have questions, please let us know what is needed in the comments so that the question can be answered.

**[CRITICAL] Azure PostgreSQL Flexible Server stuck in 'Updating' state for 3 days — Production Down**