Critical: Cannot Authenticate to Azure PostgreSQL Flexible Server (recall-ai-prod-flex) After Password Reset

Question

I am unable to authenticate to my Azure Database for PostgreSQL Flexible Server instance (recall-ai-prod-flex) as the admin user, despite multiple password resets and following all documented troubleshooting steps.

Resources:

• Server: recall-ai-prod-flex.postgres.database.azure.com
• Admin user: recalladmin@recall-ai-prod-flex
• Location: Central US
• Database: postgres

Issue Details:

• Error:

FATAL: password authentication failed for user "recalladmin@recall-ai-prod-flex"

• Password was reset several times via Azure Portal (most recent attempt: OrunmilaP1!)
• Waited over 5–15 minutes after resets
• Firewall rules allow all relevant IPs
• Username format is correct (recalladmin@recall-ai-prod-flex)
• Connection fails via both psql (CLI) and Visual Studio Code (with PostgreSQL extension)
• All fields are precisely matching portal-provided values (server name, username, password, database, port, SSL)
• No application or admin connection is possible

Steps Taken:

• Reset password to simple and complex values
• Confirmed username format and correct server/database
• Verified IP/firewall settings in Azure Portal
• Tried connection from multiple clients/locations

Impact:

• Unable to access or administer the PostgreSQL server
• All app and migration workflows are blocked

Request: Please investigate and resolve possible backend provisioning or authentication issues. Ensure the admin password reset is successful and advise next steps if additional Azure actions are required.I am unable to authenticate to my Azure Database for PostgreSQL Flexible Server instance (recall-ai-prod-flex) as the admin user, despite multiple password resets and following all documented troubleshooting steps.

Answer 1

Hi @Kal Fizer ,

Thank you for providing the details.

Based on the error message, the PostgreSQL Flexible Server is reachable and responding to connection requests. The error**"FATAL: password authentication failed for user"** indicates an authentication issue rather than a firewall or network connectivity problem.

A few key points to verify:

• For Azure PostgreSQL Flexible Server, confirm that the server is in the Ready state and that the authentication method is configured as PostgreSQL authentication or PostgreSQL and Microsoft Entra authentication. Password resets are only applicable when password-based authentication is enabled.
• If you recently reset the administrator password, ensure the reset operation completed successfully in the Azure portal before attempting to reconnect.
• Review any Bicep/ARM deployments, CI/CD pipelines, or Azure Key Vault integrations that manage the administratorLoginPassword. We have seen scenarios where automated deployments overwrite a manually reset password with a stored secret value.
• Verify the administrator username exactly as shown in the server properties and test connectivity using a PostgreSQL client with SSL enabled. Microsoft documentation also recommends testing with an alternative client to rule out client-specific configuration issues.

Since you have already performed multiple password resets, I recommend checking the Azure Activity Log for any recent deployments or configuration changes that may have updated the administrator password after the reset.

If the issue persists after confirming the above, please share the requested details via private message so that further investigation can be performed.

Microsoft References:

• Password authentication failed for user - Azure Database for PostgreSQL [Password a...soft Learn | Learn.Microsoft.com]
• Reset administrator password in Azure Database for PostgreSQL Flexible Server [Reset Admi...soft Learn | Learn.Microsoft.com]

Please let us know the outcome after validating the authentication configuration and any deployment automation affecting the server credentials.
Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

Answer 2

First, reset the password again immediately and edit the question to remove the exposed credential. It should now be treated as compromised.

The username shown is likely the main issue. Azure Database for PostgreSQL Flexible Server uses the administrator login exactly as displayed on the server's Overview/Properties page—for example, recalladmin. The legacy user@servername format should not be used for Flexible Server.

Try this and enter the newly rotated password only when prompted:

psql "host=recall-ai-prod-flex.postgres.database.azure.com port=5432 dbname=postgres user=recalladmin sslmode=require"

Before retrying, confirm the server state is Ready and Authentication is set to PostgreSQL authentication or PostgreSQL and Microsoft Entra authentication. Reset the password once, then wait for the portal's successful-completion notification.

Also check the Activity Log and any Bicep/ARM pipeline. A deployment that supplies administratorLoginPassword can overwrite a portal reset with the secret held by the deployment, so update the pipeline/Key Vault value as well.

The current FATAL: password authentication failed shows the server was reached; this is not the usual firewall error. If it still fails with the short username, follow Microsoft's password-authentication troubleshooting and admin password reset guidance.