Teams error 0xCAA82EE2: the request has timed out (how to fix it)

What 0xCAA82EE2 means

Microsoft’s Teams sign-in help page describes 0xCAA82EE2 as “The request has timed out.” Its advice is to make sure you’re connected to the internet and then work with IT to check that other apps or a firewall aren’t blocking access. The Microsoft Learn version for admins adds that the network between you and Microsoft must allow the Microsoft 365 addresses and ports Teams needs.

Nearby codes on the same pages can help you narrow it down:

Code	What Microsoft says it means
0xCAA82EE2	The request timed out
0xCAA82EE7	The server name couldn’t be resolved, which points to DNS
0xCAA70004	The server or proxy wasn’t found, often a misconfigured proxy (see Teams error caa70004)
0xCAA70007	The connection was interrupted during a download

So the sign-in window couldn’t get an answer from Microsoft in time. The question is what’s slowing or stopping that request.

Quick checks

1. Make sure other websites load. If the connection dropped after the PC woke from sleep, restart it; Microsoft notes that brief Wi-Fi loss or the network starting up after hibernation can cause these errors.
2. Open Microsoft Edge, press Ctrl + Shift + N for an InPrivate window, and go to https://login.microsoftonline.com. Microsoft uses this as a test: if the page doesn’t load, the cause is the network, a local firewall or antivirus software, not Teams.
3. Disconnect from any VPN and try again. If you’re on a work network, try once on another network, such as a phone hotspot. If Teams signs in there, the original network is blocking or slowing the request.
4. Check Settings > Network & internet > Proxy. If a manual proxy is set and you didn’t set it up, ask IT whether it should be there before turning it off.
5. If the web works but name lookups seem slow or fail, see DNS_PROBE_FINISHED_BAD_CONFIG for ways to reset DNS on Windows.

If the InPrivate test fails on one network but works on another, skip to the admin section and pass it to IT along with the error code.

Fix 1: Update or reset new Teams

If the browser test works but the Teams app still times out, the app itself may be stuck.

1. If Teams opens far enough, select Settings and more (the three dots next to your profile picture) and choose Check for updates.
2. Quit Teams fully, including from the system tray.
3. Open Settings > Apps > Installed apps, search for Microsoft Teams, select the three dots and choose Advanced options.
4. Under Reset, select Reset. Microsoft notes this clears your Teams personalization settings.
5. Open Teams and sign in again.

If you’d rather clear only the cache, Microsoft’s cache guide says to quit Teams and delete the contents of this folder:

%userprofile%\appdata\local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams

Older guides point to %appdata%\Microsoft\Teams. That’s the folder for classic Teams, which has been retired; see Teams classic: why it’s gone. On a Mac, the same Microsoft page lists the new Teams folders under ~/Library/Group Containers/UBF8T346G9.com.microsoft.teams and ~/Library/Containers/com.microsoft.teams2.

If Teams signs in but then can’t load chats or calls, that’s a different problem; see Microsoft Teams not connecting.

Fix 2: If other Microsoft 365 apps can’t sign in either

When Outlook, Word or OneDrive also fail to sign in, the problem is usually Windows’ shared sign-in component (the Web Account Manager, or WAM) rather than Teams. Microsoft’s Office sign-in connection guide covers this.

1. Open Event Viewer and go to Applications and Services Logs > Microsoft > Windows > AAD > Operational. Errors around the time of the failed sign-in that mention XMLHTTPWebRequest confirm a network problem during sign-in.
2. Make sure your firewall and antivirus allow C:\Windows\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Microsoft.AAD.BrokerPlugin.exe, C:\Windows\System32\backgroundTaskHost.exe and https://login.microsoftonline.com. If you’re not sure how rules are set up, how to block a program in Windows Firewall shows where they live, so you can check none of them is blocked.
3. If the sign-in window doesn’t appear at all, Microsoft’s desktop app sign-in guide gives PowerShell commands to check and re-register the sign-in plug-in. Run Windows PowerShell as administrator and enter:

Add-AppxPackage -Register "$env:windir\SystemApps\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy\Appxmanifest.xml" -DisableDevelopmentMode -ForceApplicationShutdown

Microsoft also suggests antivirus exclusions for the %localappdata%\Microsoft\TokenBroker, OneAuth and IdentityCache folders when security software interferes with sign-in. These steps are general sign-in fixes; Microsoft doesn’t tie them to 0xCAA82EE2 specifically, so try them only if the quick checks point to the PC rather than the network.

For IT admins

• Confirm the user’s network can reach the endpoints in Microsoft 365 URLs and IP address ranges, which Microsoft links from the 0xCAA82EE2 entry.
• Check firewalls, proxies and TLS inspection between the user and Microsoft. A proxy that slows or holds HTTPS sign-in traffic can produce a timeout rather than a clear refusal.
• If one site or VPN profile is affected and others aren’t, compare the network path for that location.
• If you open a support case, Microsoft asks for Teams debug logs and the exact error code shown on the sign-in screen.

Advice to skip

• Don’t leave the firewall or antivirus switched off. Turning one off briefly can confirm it’s the cause, but the fix is an allowance for the sign-in components above.
• Don’t disable ADAL or WAM with registry changes from old forum posts. Microsoft says that isn’t recommended for fixing Office sign-in problems.
• Credential Manager entries named msteams_adalsso belong to classic Teams. Deleting them doesn’t help new Teams sign in.

Related guides

• Teams error caa70004: what it means and how to fix it
• Microsoft Teams not connecting: how to fix it
• Teams classic: why it’s gone and how to switch to new Teams
• DNS_PROBE_FINISHED_BAD_CONFIG: 7 ways to fix it on Windows

Official sources

• Why am I having trouble signing in to Microsoft Teams? (Microsoft Support)
• Resolve sign-in errors in Teams (Microsoft Learn)
• Clear the Teams client cache (Microsoft Learn)