Troubleshooting SSO and login
This guide is used by Fin and the support team to diagnose SSO (Single Sign-On) issues with Microsoft Entra ID.
The SSO flow
Welcome uses OIDC (OpenID Connect) with Microsoft Entra ID. For SSO to work for a company:
A Global Administrator in the company's Azure tenant must grant admin consent for the Welcome Workdays app
The SSO domain (e.g. company.com) must be added in the Welcome Workdays admin under SSO settings
Information to collect
Company name and email domain
Who performed the setup (IT admin, building manager)
Exact error message or screenshot
Browser used (and whether incognito mode was active)
Error: "Unable to process request due to missing initial state"
This error appears after admin consent has actually been granted. It occurs because the consent URL redirects back to the Welcome login, but there is no active login flow to resume.
The error is cosmetic. The consent most likely went through.
Ask the customer to:
Verify in Microsoft Entra ID → Enterprise Applications → Welcome Workdays that the permissions are registered
Try logging in normally to confirm it works
If the error occurs BEFORE the consent dialog appears: try a regular browser window (not incognito), disable strict tracking protection, or try Chrome/Edge.
Error: AADSTS65004 or consent blocked
The Azure tenant has strict consent policies that block third-party apps.
Ask the customer's IT admin to:
Check Entra ID → Enterprise Applications → Consent and Permissions
Ensure that admin consent is allowed, or add an exception for Welcome Workdays
The person granting consent must have the role of Global Administrator or Privileged Role Administrator.
User cannot log in after SSO is enabled
Check:
The domain in the Welcome SSO settings matches the user's email domain exactly
The user exists in Welcome Workdays (the user must be created first — SSO does not create users automatically)
The user is selecting the correct Microsoft account (some users have multiple)
Admin consent URL (for reference)
Format: https://login.microsoftonline.com/DOMENE/adminconsent?client_id=7f37f2d6-f31d-491a-83a8-ff2f42cc600b
Replace DOMAIN with the company's email domain (e.g. company.com). Both company.com and company.onmicrosoft.com work.
Known edge cases
Admin consent succeeds despite the error page. The "Missing initial state" error does not mean the consent failed
SSO must be enabled on both sides. Admin consent in Azure is not enough — the domain must also be added in Welcome
The user must exist in Welcome first. SSO authenticates but does not create users automatically
Both domain formats work: company.com and company.onmicrosoft.com
Do you need help?
Chat with us via the AI chatbot at the bottom right of the screen, or send an email to support@welcomeworkdays.com.
