Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Does anyone have a firm solution here? I have VDI users getting this error.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello, I have a remote end user that is receiving this error code when trying to sign into any M365 app. Once we close the error message the apps work perfectly fine but this happens daily when signing on and I would like to find a permanent fix. I would attach a screenshot but that doesn't seem to be working right now.
Something went wrong
We couldn't sign you in. If this error persists, contact your system administrators and provide the error code CAA90049.
Error code: CAA90049
Correlation ID: 9a55***1d07
Server message: Session key is empty
Any help is appreciated.
Thank you
[PII is removed by moderator]
Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Does anyone have a firm solution here? I have VDI users getting this error.
I have a user with the same issue after he updated and rebooted. Apps repeatedly ask for a sign in, even using the web apps. We also get a 1001 error when signing into Office desktop apps. I have updated Office, cleared credentials, removed / added registry keys, removed folders from their AppData, etc. None of the fixes online are working.
Couple of things. The client I'm having issues with is federated and using single sign on. And I found that I could log into a different Office 365 account in Office and it will accept the sign in. Could be something on the back end with Entra.
Office/Teams seem to work just fine after we click "Continue." Of course, our Help Desk is flooded with calls about this error prompt. So we would like a resolution - shouldn't receive this prompt at all. We are running Server 2022.
Same here, did yo manage to fix it?
Same here.