- Concept
- Version · 6.0.2
- Manage
Troubleshoot single sign-on
Last updated: November 17, 2026
These are the single sign-on problems people run into most often with Microsoft Entra. Each one starts from what the person signing in sees, then explains the cause and the fix.
Signing in
I signed in but I cannot see anything
Your sign-in worked. Your account is in the Pending group with no permissions, and the screen headed Your account is awaiting access is what that looks like.
Ask a workspace administrator to assign you to a group.
If you were invited, check that you signed in with the address the invitation was sent to. An expired invitation is not applied, so an administrator assigns your groups directly instead.
This happens even if you belong to groups in Microsoft Entra. Liquibase Secure does not use Entra groups, so your access comes only from the groups an administrator assigns you in Liquibase Secure.
I reached a Microsoft error page and never came back
On the OpenID Connect path, an account outside the configured tenant is refused by Microsoft at its own tenant-scoped endpoint. Entra reports AADSTS50020 and the user stays on Microsoft's error page rather than returning to Liquibase Secure.
Tenant restriction is working as intended here. Sign in with an account that belongs to the configured tenant.
My single sign-on was refused
A single sign-on attempt is refused when the email address already belongs to a password account. A user has exactly one identity, and the existing password account owns that address.
Sign in with the password for that account.
I cannot switch Microsoft accounts
Signing out of Liquibase Secure does not sign you out of Microsoft. The next sign-in attempt reuses the Microsoft session you still hold.
Sign out at Microsoft as well, or use a private browser window, then sign in with the account you want.
Problems that affect everyone
Sign-in suddenly fails for everyone
An expired credential on the provider reaches users as a failed sign-in even though nothing about their account changed.
Check the provider configuration. On OpenID Connect, the client secret expires. On SAML 2.0, the signing certificate expires, typically every one to three years. Both are replaced from the Single Sign-On page without downtime. See Configure single sign-on with Microsoft Entra.
Everyone was signed out at once
Disabling or removing a provider signs out every user who authenticated through it, on their next request. Password users are unaffected.