Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
We are encountering this issue as well in a VDI environment.
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.
We are encountering this issue as well in a VDI environment.
We do have a VDI environment for our users with office shared computer activation. After 9 April the uses have to login in Office applications and after activate the users will have to register device for MAM end get this error. Are there any solution for this issue?
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
Hello,
Any news from anybody about this. Today is the first time it happened to one of my users and can't get her through it. I cleared the activation status and license on her endpoint but still getting the same error. EntraID sees it as a successful sign in.
Have you found a solution for this, we have a user with this exact problem and would also like to remedy the issue.