Microsoft Teams Error Code caa70004

Anonymous
2020-05-06T21:22:12+00:00

Good day,

We seem to be having some trouble with Microsoft Teams authentication for some users on new computers that have been added to our internal domain. Currently this is only happening to users that are logging into the computer for the first time. We have now confirmed that it is happening on all versions of Windows 10 that we can test from 1809 to 1903. The O365 accounts and licensing are fine, each user can login to Teams web app and use the service just fine. This is unexpectedly only the Microsoft Teams software not working.

***Very importantly, we are never prompted for a password.***We enter the proper email address for the Office 365 user and click sign-in. After doing so we are greeted with the below screen, there is no attempt or request to authenticate. There are no credentials in the credential manager and we have cleared all others to be sure it is unrelated.

We were also able to find that when the computers are removed from the domain they can login but not when added to the domain. When the computer is added to the domain and even if put in an OU blocking all policies from AD it still gives the same error whether it is a domain or local user account. Additionally, it doesn't matter which user is attempting to authenticate. You get the same error message when you attempt a fake address as well as a valid address. This makes me believe that the authentication process doesn't even get to the point of actually authenticating the user before it fails inexplicably.

It is clear this is an issue with the forms based authentication and it appears to be bypassing that step for some reason that I can't understand that just started but only when the PC is attached to the domain. If I remove the device from the domain it immediately starts working and as I mentioned. All existing PCs we have running on the domain are working without issue but when we log a new user into the computer it doesn't work, whether that be a local or domain user.

The error is as follows and is in the screen capture below. The first portion changes every time an attempt is made but I included it for reference since it is shown in the capture.

desktop-029172fb-76ac-4134-a8b8-c7df6ca648a8 <this part of the message changes with every attempt>

Error code - caa70004

There's a more permanent way to sign in to Microsoft Teams. If you're having trouble completing the process, talk to your IT admin.

I can provide the logs but wasn't able to include them because of the character limit.

I am at a total loss, the only things I can seem to hint at with the errors but not with the error code is a potential issue with AD FS but we do not use AD FS internally and it isn't configured on the domain. All other Office applications such as Outlook will connect and are completely content with being on our domain but Teams will not work.

Your assistance with this matter is greatly appreciated.

Microsoft Teams | Microsoft Teams 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

43 answers

Sort by: Newest
  1. Anonymous
    2020-06-12T01:47:24+00:00

    Post resetting my office password teams started showing the issue was receiving the same page 

    "run into a issue" with error code caa70004.

    Tried the following and it worked flawlessly, the inital mistake i was doing was that i was on VPN & company sign in page already.

    >>> ensure you are not on any vPN or company related production connection, keep it on simple internet connectivity.

    >>> clear the cache in all cache folders only

    %AppData%\Microsoft\teams\application cache\cache

    during the above ensure teams is not running, post clearing the cache start the teams on plain internet connectivity and then it shows the organisation sign in page post that it should work unless you have other underlying symptoms.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-06-08T09:40:39+00:00

    Dear all

         I face the same problem for 3 days now, first  i notice that  the code erreur is 4c7, but today i found a different one erreur caa70004 . 

    Could you please advise if you know how ti fix it ? 

    Thanks in advance

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-05-09T08:39:43+00:00

    Hi J.D. Jankowski,

    From the fiddler log screenshots, you can see they connected to different hosts. The failed one connected to odc.officeapps.live.com. From my research, this URL is dedicated for Microsoft personal accounts. While the successful one was redirected to the right Microsoft 365 login host login.microsoftonline.com. 

    From my perspective, this issue could be related with the DNS records of the domain. Because the root cause is that the user credential is sent to the wrong host for authentication after Teams resolves the domain of the user account. To protect your privacy, I'd like to discuss this in private message.

    Regards,

    Marvin

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-05-08T17:24:52+00:00

    Hello Marvin,

    I did it again to confirm but I have tested on the devices in question with no AV installed and there is no blocking on the system firewall as I turned it off for testing as well. Additionally, I have created a bypass rule in the site firewall for the devices being tested on to make sure it was not firewall related. Lastly, I completed the steps requested for the AAD WAM package and after that process was successfully completed I received the same caa70004 error when attempting to login to Teams.

    J.D. Jankowski

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-05-08T07:54:34+00:00

    Hi JDJankowski,

    Thank you for the log files. From the log, I found the error is related with WAM (Web Account Manager).

    In this scenario, please make sure the firewall, antivirus software, and Windows Defender don't block the following AAD WAM plug-in processes that engaged in token acquisition:

    • C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Microsoft.AAD.BrokerPlugin.exe
    • C:\Windows\System32\backgroundTaskHost.exe

    Besides, you can try to reinstall the AAD WAM package to check if it helps. For your reference, see Fix authentication issues in Office applications when you try to connect to an Office 365 service.

    Regards,

    Marvin

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments No comments