Additional features, settings, or issues not covered by specific Microsoft Teams categories
This is perfect. It fixed the issue for me immediately. Thanks!
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Additional features, settings, or issues not covered by specific Microsoft Teams categories
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.
This is perfect. It fixed the issue for me immediately. Thanks!
This worked for me
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.
This Method help me to get this issue resolved, please follow below steps after uninstallting application through Add or Remove Program:
Done!!
Thanks !
Ashish Chaurasia
This worked for me after trying everything else