Error code CAA90049 - Any M365 App

Anonymous
2024-04-08T18:25:48+00:00

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.

  • User enters login credentials and Microsoft authenticator code then this error pops up for any m365 app / teams / OneDrive.
  • User is in another state so can't come into office.

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 and Office | Subscription, account, billing | For business | Other

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.

0 comments No comments

67 answers

Sort by: Newest
  1. Anonymous
    2024-09-11T21:23:54+00:00

    Any information on this reg key?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2024-09-04T16:30:52+00:00

    Once we disabled workplace join via the regkey it stopped immediately.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2024-09-04T16:23:52+00:00

    I'm not sure your environment, but for us it was only in VMware Horizon and I created a new pool where neither the golden image nor the instant clones used TPM chip and the issue went away for us.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2024-09-04T16:12:53+00:00

    Has anybody heard further on this issue yet? We just started having this happen to a few users.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2024-08-21T09:46:19+00:00

    Yes sorry, its worked for 24 hours then stopped again.

    Has anyone had anything back from MS on the cases they have logge about this. I'm about to log one myself.

    Was this answer helpful?

    0 comments No comments