What the error means
0xCAA70004 (shown in the Teams app as caa70004) is a connection failure during sign-in, not a password problem. Microsoft's support article for Teams users describes it as "The server or proxy wasn't found" and says the usual reason is a misconfigured proxy or a network sniffing program such as Fiddler that is running but has not been configured to decrypt HTTPS traffic.
Microsoft's admin troubleshooting article for Teams sign-in groups 0xCAA70004 with 0xCAA70007 and adds a second clue: if the sign-in problem also affects other Office applications, the cause is usually in the Windows sign-in layer that Teams and Office share, called Web Account Manager (WAM). That case is handled in Microsoft's article on connection issues in sign-in for Office.
Common causes
- A proxy server address that is wrong, unreachable, or requires authentication the sign-in broker cannot provide.
- A traffic-inspection or debugging tool, such as Fiddler, intercepting HTTPS without decryption set up.
- A local firewall, antivirus or endpoint tool blocking the processes that request sign-in tokens.
- A network that blocks or partially blocks
login.microsoftonline.com. Microsoft notes this address covers many IP addresses, so a partial block can make some devices fail while others work.
How to fix it
1. Close inspection tools and check the proxy
If a tool like Fiddler or another HTTPS proxy is running on the PC, close it and start Teams again. Microsoft's guidance is that the IT admin either stops the program and relaunches the app, or configures it properly and relaunches it. On a managed PC, ask IT whether a proxy is set for your network before changing it yourself.
2. Test the sign-in page in Microsoft Edge
Microsoft's Office connection article uses this test. Open Edge and go to https://login.microsoftonline.com, then repeat in an InPrivate window and sign in. You should land on office.com or your company's start page. If either attempt fails, the network, a local firewall or antivirus software is blocking sign-in, and Teams cannot work until that is fixed.
3. Update Teams
In the Teams desktop app, select Settings and more next to your profile picture and choose Check for updates. Microsoft's article says the app updates itself automatically, but an app that missed an update should be updated before further troubleshooting.
4. Admins: run the Teams sign-in diagnostics
A Microsoft 365 administrator can run the Teams Sign-in diagnostic from the Microsoft 365 admin center by entering the affected user's address. The Microsoft Remote Connectivity Analyzer also has a Teams Sign in test at testconnectivity.microsoft.com. Microsoft notes neither is available for every government or sovereign cloud.
5. IT: allow the sign-in broker through security software
When other Office apps fail too, Microsoft says to make sure the firewall, antivirus and Windows Defender do not block these processes, and that the network does not block login.microsoftonline.com:
C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Microsoft.AAD.BrokerPlugin.exe
C:\Windows\System32\backgroundTaskHost.exeTo confirm the pattern, the same article checks Event Viewer under Applications and Services Logs, Microsoft, Windows, AAD, Operational for XMLHTTPWebRequest entries with codes starting 0x?AA7.
6. Reset or reinstall Teams
If the error remains, Microsoft's Teams article ends with a reinstall. For new Teams on Windows, Microsoft's cache article documents a reset under Settings, Apps, Installed apps, Microsoft Teams, Advanced options, Reset. The reset deletes app data, including personal settings.
If nothing works
Collect Teams debug logs and note the exact error code shown on the sign-in screen, then open a support request through your Microsoft 365 administrator. Microsoft asks for both when the documented steps do not help.
What we checked
Two official pages were read on 2026-11-19. The Microsoft Learn article Fix Teams sign-in errors lists 0xCAA70004 with 0xCAA70007 and points to the Office connection troubleshooting article, which was also read for the Edge test, the blocked processes and the Event Viewer check. The Microsoft Support article for Teams users gives the description and the proxy and Fiddler explanation. The Teams cache article on Microsoft Learn was read for the reset steps. The error was not reproduced for this page.
Last checked: 2026-11-19.