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

43 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-10-21T13:33:30+00:00

    I found that this was related to Proxy config settings in the Internet Explorer control panel applet. If you are using a PAC file or redirecting your connections through a web processing filter like zscaler or websense, than they can interfere with the authentication process. If you find that this only happens with an active VPN connection, it's likely because the corporate web filter only becomes active when the user connects to corporate VPN. If you open the Internet Settings control panel applet and go to the connections tab, you can use the "automatically detect settings" checkbox to fix this. Likewise, if you have VPN connections listed in the connection list, you can double click on each of those and check the "automatically detect settings" check box within each connection.

    This might explain why doing a full "reset" of internet settings fixes this for some people - because it wipes out any proxy settings. However, you lose any other configuration settings by doing the full reset when all you may need to do is reset the proxy settings.

    Note that your corporate group policy settings may reset these settings back to their original settings. If that happens, then your IT department will need to fix the problem in their web filtering software.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-07-16T19:40:45+00:00

    Hi JDJankowski,

    There seems to be a conflict issue between MS teams and the Windows or Internet Security system recently. 

    I have faced with the same issue for about a month's time as the App was working before perfectly.

    If you use Zscaler, you may Turn it OFF and run MS teams App to see if it works.

    I hope this could also solve your problem as it did for mine. However, our admin is working to find the main conflict as Zscaler is required to be ON per our organization policy.

    Cheers,

    Adam

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-06-22T02:52:44+00:00

    This works perfectly to me! Thank you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-06-12T10:24:01+00:00

    Our users are having similar problems. When they are on the LAN they can't sign in.  But when off the LAN there are no problems and they can login to Teams fine.

    We receive several errors

    0xCAA80000, CAA70004 and caa30194

    Our AD is not synced with O365 as we are using the free version of Teams

    Users were logging in fine until earlier this week

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. 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