background
← Back to all provider errors

Microsoft

AADSTS50058 — Single Sign-On failed; no session

Silent SSO (prompt=none) requested but no valid session.

Riposte solution

No Azure AD session exists for a silent sign-on attempt. This error often arises if trying an OAuth flow with prompt=none when the user isn't logged in. To fix, require an interactive login. Use Riposte to start a normal OAuth flow via /auth/sessions (which will prompt the user to sign in) instead of relying on an existing session.

Quick facts

Provider
Microsoft
Endpoint / surface
Azure AD OAuth 2.0
Status code
400

Why it happens

[User not signed in; Session expired]

How to fix it

[Use interactive login; Ensure user has active session]