How to Fix AADSTS50058: Session information is not sufficient for single-sign-on
Error message
AADSTS50058: Session information is not sufficient for single-sign-on.
If you're seeing "AADSTS50058: Session information is not sufficient for single-sign-on", you're not alone. Here's what it means, why it happens, and the steps to resolve it.
What this error means
Entra tried to sign the user in silently (without prompting) but doesn't have enough session state to identify them. This is usually expected behavior — the app is supposed to fall back to interactive sign-in.
Why this happens
The user has no active session, third-party cookies are blocked, the browser is in private mode, or the app sent `prompt=none` when no session existed.
Step-by-step fix
If you're a developer: catch this error and trigger an interactive sign-in flow instead of treating it as fatal.
If you're an end user: enable third-party cookies for `login.microsoftonline.com`, or open the app in a regular (non-private) window.
Confirm the user actually has an active Microsoft session in the same browser.
Affected products
Entra ID
Still broken? Try these
- Check whether browser tracking-prevention or content-blocking extensions are stripping cookies.
- If using MSAL, make sure `loginHint` or `account` parameters are passed correctly on `ssoSilent`.
- On corporate devices, verify the SSO extension is installed and signed in.
Related errors
Frequently asked questions
What does "AADSTS50058: Session information is not sufficient for single-sign-on" mean?
Entra tried to sign the user in silently (without prompting) but doesn't have enough session state to identify them. This is usually expected behavior — the app is supposed to fall back to interactive sign-in.
What causes "AADSTS50058: Session information is not sufficient for single-sign-on"?
The user has no active session, third-party cookies are blocked, the browser is in private mode, or the app sent `prompt=none` when no session existed.
How do I fix "AADSTS50058: Session information is not sufficient for single-sign-on"?
1. If you're a developer: catch this error and trigger an interactive sign-in flow instead of treating it as fatal. 2. If you're an end user: enable third-party cookies for `login.microsoftonline.com`, or open the app in a regular (non-private) window. 3. Confirm the user actually has an active Microsoft session in the same browser. Always test changes in a non-production environment first.
Browse more errors in Entra ID: Fix Microsoft Entra ID (Azure AD) errors. AADSTS error codes, admin consent, app role assignment, Conditional Access, and user lookup problems. Or paste your own error into the error decoder tool to find a match. You can also go back to the homepage to browse common errors by topic.