Azure failed to provision a service and now I cannot create it at all

David Hirst 20 Reputation points
2025-05-20T13:27:40.4133333+00:00

I have tried to provision a server on this service and whilst validation was successful it failed to create the service with a meaningless error. When I have attempted to recreate the provisioning, again succeeding the validation step it tells me it cannot create the service because it already exists. I then check the index to see that there is a server in the dropping state and it has been that way for several hours.

Azure Database for PostgreSQL
{count} votes

Accepted answer
  1. PratikLad 1,830 Reputation points Microsoft External Staff Moderator
    2025-05-23T17:28:51.2066667+00:00

    Hi David Hirst

    It looks like the error you're seeing is due to a provisioning failure that left the server in a stuck or "Dropping" state. This is preventing you from either cleaning it up or trying to provision it again.

    Here’s what you can do to check if the server still exists in Azure:

    az postgres server list [--resource-group]
    

    This will show all existing servers. If the problematic server is still listed, you can manually delete it using:

    az resource delete [--resource-group]
                       [--name]
                       [--resource-type]
    
    • Don’t try to re-create the resource immediately: After a failed provisioning attempt, the system might still think the resource exists. Trying again too soon can lead to more failures.
    • Clear your browser cache or try a different browser: Sometimes the Azure portal behaves unpredictably due to cached data.
    • Use a different name if you try again: Even if a deployment fails, the resource name might still be temporarily reserved. Choosing a new name can help avoid conflicts
    • Retry creating Postgres SQL server using below Azure CLI
    az postgres server create [--admin-password]
                              [--admin-user]
                              [--assign-identity]
                              [--auto-grow {Disabled, Enabled}]
                              [--backup-retention]
                              [--geo-redundant-backup {Disabled, Enabled}]
                              [--infrastructure-encryption {Disabled, Enabled}]
                              [--location]
                              [--minimal-tls-version {TLS1_0, TLS1_1, TLS1_2, TLSEnforcementDisabled}]
                              [--name]
                              [--public]
                              [--resource-group]
                              [--sku-name]
                              [--ssl-enforcement {Disabled, Enabled}]
                              [--storage-size]
                              [--tags]
                              [--version]
    

    If the issue persists, please don't hesitate to reach out, we're here to help and will assist you further.


0 additional answers

Sort by: Most helpful

Your answer

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