What causes DF-PGSQL-InvalidCredential?

The PostgreSQL user password was changed but the ADF linked service was not updated. The linked service references a user that doesn't exist in the target database or has been dropped. The pg_hba.conf authentication method for the user or host is set to 'reject' or 'md5' when a different method is expected. The password is stored in Azure Key Vault and the Key Vault secret was rotated or the reference is incorrect

How do I fix DF-PGSQL-InvalidCredential?

In ADF Studio, open the PostgreSQL linked service and update the username and password to the current values.. If the password is stored in Azure Key Vault, verify the secret name and version match the current active secret.. Test the credentials directly: connect with psql or pg_admin using the same hostname, port, database, username, and password from the linked service.. On the PostgreSQL server, check pg_hba.conf to confirm the host/user/database combination is allowed and uses 'md5' or 'scram-sha-256' authentication.. Test connection the linked service and re-publish the ADF pipeline before triggering a new run.

Medium severitydata source

Power BI Refresh Error:
DF-PGSQL-InvalidCredential

What does this error mean?

The PostgreSQL username or password in the ADF linked service is wrong, the pg_hba.conf on the server doesn't allow the connection method, or the database user doesn't exist. ADF uses standard PostgreSQL authentication — any mismatch between the stored credentials and the server's actual user configuration will cause this error.

Common causes

1The PostgreSQL user password was changed but the ADF linked service was not updated
2The linked service references a user that doesn't exist in the target database or has been dropped
3The pg_hba.conf authentication method for the user or host is set to 'reject' or 'md5' when a different method is expected
4The password is stored in Azure Key Vault and the Key Vault secret was rotated or the reference is incorrect

How to fix it

1In ADF Studio, open the PostgreSQL linked service and update the username and password to the current values.
2If the password is stored in Azure Key Vault, verify the secret name and version match the current active secret.
3Test the credentials directly: connect with psql or pg_admin using the same hostname, port, database, username, and password from the linked service.
4On the PostgreSQL server, check pg_hba.conf to confirm the host/user/database combination is allowed and uses 'md5' or 'scram-sha-256' authentication.
5Test connection the linked service and re-publish the ADF pipeline before triggering a new run.

Frequently asked questions

Does this error affect all pipeline runs or just the current one?

Depends on the root cause. A persistent misconfiguration fails every run; a transient issue may resolve on retry. Check the run history.

Can this error appear in Azure Data Factory and Microsoft Fabric pipelines?

Yes — the same connector errors appear in both ADF and Fabric Data Factory pipelines.

How do I see the full error detail for an ADF pipeline failure?

In ADF Monitor, click the failed run, then the failed activity. The detail pane shows the error code, message, and sub-error codes.

Will downstream Power BI datasets be affected when an ADF pipeline fails?

Yes — a dataset refreshing after the pipeline will use stale data or fail if the target table was cleared. The Power BI refresh may succeed while serving wrong data.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide