Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
Setting RoamIdentity to "Enable" does NOT resolve the issue for us.
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.
Setting RoamIdentity to "Enable" does NOT resolve the issue for us.
Not that I'm aware of. Using Win10 Enterprise pool but can check to see if that's an option I can disable on the pool creation.
Note: we currently have a production pool in use where O365 and Classic Teams and older version of FSLogix (not HF4) being used, no issues. Just on this new test pool. I will check that GPO. Thank you, Craig!
JQueen.24 - Are you using a vTPM? My golden image never had a vTPM and when I created a new pool and told horizon NOT to add the vTPM my issue went away. As such that became my fix.
Additionally on the 31st PhRust posted this and it seems to have helped others.
We had the same problem after an upgrade to Server 2022 with FSLogix HF4 (2.9.8884.27471), after we set the "RoamIdentity" to "1" via GPO it works fine.
I'm also seeing this in Horizon 8, instant clone desktop VDI using FSLogix HF4 for profile management. We are trying to get the New Teams and New Outlook working on Win10 Enterprise desktops. We use Okta 2fa and on a new profile we can get setup in all the apps New Teams, New Outlook, OneDrive, Edge, etc... However, once we logoff the session and get a new session, this is when we start to see the error as reported.
I have tested this fix and it does appear to resolve the issue.