Forum Discussion
Microsoft Teams Error Code 0xcaa80000
- Aug 06, 2020
I found that deleting the token binding key had resolved the issues for a number of people in Google searches that I did. Only thing is when I deleted the token key I logged into the Teams app and it error'd again. Then as part of a fiddler trace I was doing I kept trying to connect a few times with Teams one after the other and finally the ADFS page popped up to enter the users username and password and it signed in! Unsure if deleting the binding key fixed the issue or not!
C:\Users\BobSled\AppData\Local\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\AC\Microsoft\Crypto\TokenBindingKeys\Keys
fb47a8d42be514593f982d4b0d7edd08_90cb05ef-cd90-4066-aafe-3397eb8039a5_4068bc0f75fd0f09b9c2c7507f15f982
blue_man
This may relate to the following articles:
- https://www.reddit.com/r/sysadmin/comments/190tvru/office_http_404_in_avd/
-https://www.reddit.com/r/VMwareHorizon/comments/1avofn9/authentication_issues_with_latest_version_of_365
- https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Anyone-having-issues-with-Outlook-or-Teams-after-latest-Windows/td-p/3009088/page/2
- https://kb.vmware.com/s/article/97111
https://www.reddit.com/r/sysadmin/comments/190tvru/office_http_404_in_avd/
- LordDelacroixMay 12, 2024Copper Contributor
stefanwey-umb can someone please explain to me why we, those of us in the community, are the ones responsible for continually fixing problems created by this crappy software from a crappy company called Microsoft?