What causes AADSTS50126?

User typed the wrong password or username at the sign-in prompt. Password was recently changed in Entra ID but the cached/stored credential on a Power BI dataset, gateway, or ADF linked service was not updated. Account password expired and must be reset before sign-in succeeds. Service account used by an unattended Power BI refresh or ADF pipeline has a rotated password that the data source still references. User is signing in with an on-premises AD password that has not yet synced to Entra ID via Azure AD Connect

How do I fix AADSTS50126?

Sign in to https://myaccount.microsoft.com with the same account to confirm the password actually works — this isolates 'wrong password' from 'wrong configuration'. If the credential is stored (Power BI dataset, on-prem data gateway, ADF linked service, Fabric connection): open the data source settings and re-enter the current password under 'Edit credentials'. If the password was recently changed, force a password sync: in Azure AD Connect run 'Start-ADSyncSyncCycle -PolicyType Delta' and retry. For service accounts driving unattended refreshes, replace the password-based credential with a service principal or managed identity so password rotation no longer breaks the pipeline. If the account is locked or the password is expired, reset it via the Entra admin center (Users → Reset password) and update every downstream stored credential

High severityauthentication

Power BI Error:
AADSTS50126

What does this error mean?

Microsoft Entra ID (Azure AD) rejected the sign-in because the supplied username or password did not match.

Common causes

1User typed the wrong password or username at the sign-in prompt
2Password was recently changed in Entra ID but the cached/stored credential on a Power BI dataset, gateway, or ADF linked service was not updated
3Account password expired and must be reset before sign-in succeeds
4Service account used by an unattended Power BI refresh or ADF pipeline has a rotated password that the data source still references
5User is signing in with an on-premises AD password that has not yet synced to Entra ID via Azure AD Connect

How to fix it

1Sign in to https://myaccount.microsoft.com with the same account to confirm the password actually works — this isolates 'wrong password' from 'wrong configuration'
2If the credential is stored (Power BI dataset, on-prem data gateway, ADF linked service, Fabric connection): open the data source settings and re-enter the current password under 'Edit credentials'
3If the password was recently changed, force a password sync: in Azure AD Connect run 'Start-ADSyncSyncCycle -PolicyType Delta' and retry
4For service accounts driving unattended refreshes, replace the password-based credential with a service principal or managed identity so password rotation no longer breaks the pipeline
5If the account is locked or the password is expired, reset it via the Entra admin center (Users → Reset password) and update every downstream stored credential

Frequently asked questions

What does AADSTS50126 mean?

Error validating credentials due to invalid username or password. The user didn't enter the right credentials. Expect to see some number of these errors in your logs due to users making mistakes.

How do I fix this error?

Check your application registration, token configuration, and user permissions in the Azure portal. Review Conditional Access policies if the error is policy-related.

Source · learn.microsoft.com/en-us/entra/identity-platform/reference-error-codes#aadsts-error-codes