Share via

Cannot delete database due to Private endpoint in Failed state; reprovision fails

Dajo Hofman 20 Reputation points
2026-03-11T11:11:15.61+00:00

Hi,

We are running into an issue with deletion of some resources, specifically an Azure Database for PostgreSQL flexible server and the connected private endpoint.

The database had previously been inaccessible due to CMK inaccesibility (deleted resources in the wrong order). This has been restored, but we still cannot delete the database as it will fail with the message that a private endpoint is connected. We have tried deleting the private endpoint, but it has a provisioning state: "Failed" and fails to delete.

We have tried restoring the provisioning state as instructed in the troubleshooting guide using Get-* and Set-AzPrivateEndpoint. This operation fails however with:

Set-AzPrivateEndpoint: Long running operation failed with status 'Failed'. Additional Info:'An error occurred.'
StatusCode: 200
ReasonPhrase: OK
Status: Failed
ErrorCode: InternalServerError
ErrorMessage: An error occurred.

The activity log for the private endpoint does not provide more details just a state update to "Failed", the activity log for the database shows another failed operation:
Operation name
Update Azure Database for PostgreSQL - Flexible Server Private Endpoint Connection Proxy Create

  • Time stamp
    Wed Mar 11 2026 11:54:35 GMT+0100 (Central European Standard Time)
  • Event initiated by
    Azure Traffic Manager and DNS
  • Error
    codeResourceOperationFailure
  • Message
    The resource operation completed with terminal provisioning state 'Failed'.

How can we resolve this?

Azure Database for PostgreSQL
0 comments No comments

Answer accepted by question author
  1. Manoj Kumar Boyini 11,685 Reputation points Microsoft External Staff Moderator
    2026-03-11T14:39:39.5733333+00:00

    Hi Dajo Hofman

    The PostgreSQL flexible server was stuck in an Updating state due to the earlier private endpoint failure. The internal PostgreSQL team restarted the underlying server container, after which the server returned to a Ready/Healthy state. Once the server was healthy, the private endpoint could be recovered successfully, and you were then able to delete both the private endpoint and the server without issues.

    Glad to hear everything is cleaned up now. Please let us know if you need any further assistance.

    0 comments No comments

0 additional answers

Sort by: Most 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.