What causes AADSTS50140?

Non-interactive authentication request (prompt=none) hitting the KMSI interrupt page, which requires user interaction. Power BI Gateway, ADF Linked Service or Databricks connector using a service principal flow that lands in an interactive KMSI screen instead of token endpoint. Embedded browser / WebView2 in a custom app blocking the KMSI redirect back to the application. Tenant policy forcing KMSI prompt while the client app sets prompt=none or login_hint without consent. User aborting or refreshing the browser at the KMSI screen, breaking the auth state

How do I fix AADSTS50140?

Retry the sign-in in a normal browser tab and click Yes/No on the "Stay signed in?" prompt — the flow should complete on its own. If this happens in a Power BI Gateway, ADF Linked Service or Databricks connection, switch from a user account to a Service Principal (client credentials) so KMSI is bypassed entirely. In your app registration, remove prompt=none from the auth request when the user has no existing session, or fall back to prompt=select_account on KmsiInterrupt. If using an embedded WebView, switch to the system browser (MSAL broker / WAM) so the KMSI redirect can complete. Tenant admins: disable the KMSI prompt for federated apps via Entra ID → Company branding → Sign-in page → "Show option to remain signed in" = No

Low severityauthentication

Power BI Error:
AADSTS50140

What does this error mean?

Sign-in was interrupted by the "Keep me signed in" (KMSI) prompt — an expected step, not a real failure.

Common causes

1Non-interactive authentication request (prompt=none) hitting the KMSI interrupt page, which requires user interaction
2Power BI Gateway, ADF Linked Service or Databricks connector using a service principal flow that lands in an interactive KMSI screen instead of token endpoint
3Embedded browser / WebView2 in a custom app blocking the KMSI redirect back to the application
4Tenant policy forcing KMSI prompt while the client app sets prompt=none or login_hint without consent
5User aborting or refreshing the browser at the KMSI screen, breaking the auth state

How to fix it

1Retry the sign-in in a normal browser tab and click Yes/No on the "Stay signed in?" prompt — the flow should complete on its own
2If this happens in a Power BI Gateway, ADF Linked Service or Databricks connection, switch from a user account to a Service Principal (client credentials) so KMSI is bypassed entirely
3In your app registration, remove prompt=none from the auth request when the user has no existing session, or fall back to prompt=select_account on KmsiInterrupt
4If using an embedded WebView, switch to the system browser (MSAL broker / WAM) so the KMSI redirect can complete
5Tenant admins: disable the KMSI prompt for federated apps via Entra ID → Company branding → Sign-in page → "Show option to remain signed in" = No

Frequently asked questions

What does AADSTS50140 mean?

This error occurred due to "Keep me signed in" interrupt when the user was signing-in. This is an expected part of the sign in flow, where a user is asked if they want to remai

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