What causes DF-MSSQL-InvalidCredential?

The SQL login password was rotated in the database but the ADF linked service was not updated. The SQL login was disabled or deleted from the server. The password is stored in Azure Key Vault and the Key Vault secret version changed or expired. The linked service uses a different SQL login than the one that has access to the target database

How do I fix DF-MSSQL-InvalidCredential?

In ADF Studio, open the SQL linked service and update the password to the current value.. If the password is stored in Azure Key Vault, verify the Key Vault secret name and version in the linked service match the current active secret.. In SQL Server Management Studio or Azure portal Query Editor, test the login: `SELECT 1;` with the configured credentials to confirm they work outside ADF.. If the SQL login was deleted, recreate it with the appropriate database roles: `CREATE LOGIN [name] WITH PASSWORD='.'; USE [database]; CREATE USER [name] FOR LOGIN [name]; ALTER ROLE db_datareader ADD MEMBER [name];`.. Test connection the linked service and re-publish before triggering the pipeline again.

Medium severitydata source

Power BI Refresh Error:
DF-MSSQL-InvalidCredential

What does this error mean?

The SQL Server username or password in the ADF linked service is wrong or has changed — typically after a password rotation or user deletion. Unlike InvalidAuthConfiguration, the auth method is correct but the specific credentials are rejected.

Common causes

1The SQL login password was rotated in the database but the ADF linked service was not updated
2The SQL login was disabled or deleted from the server
3The password is stored in Azure Key Vault and the Key Vault secret version changed or expired
4The linked service uses a different SQL login than the one that has access to the target database

How to fix it

1In ADF Studio, open the SQL linked service and update the password to the current value.
2If the password is stored in Azure Key Vault, verify the Key Vault secret name and version in the linked service match the current active secret.
3In SQL Server Management Studio or Azure portal Query Editor, test the login: `SELECT 1;` with the configured credentials to confirm they work outside ADF.
4If the SQL login was deleted, recreate it with the appropriate database roles: `CREATE LOGIN [name] WITH PASSWORD='.'; USE [database]; CREATE USER [name] FOR LOGIN [name]; ALTER ROLE db_datareader ADD MEMBER [name];`.
5Test connection the linked service and re-publish before triggering the pipeline again.

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