What the error means
0xCAA82EE2 (shown in Teams as caa82ee2) means the sign-in request timed out. Microsoft's support article for Teams users describes it in one line, "The request has timed out," and tells users to check their Internet connection and then work with their IT admin to make sure other apps or a firewall configuration are not preventing access.
Microsoft's admin article for Teams sign-in pairs it with 0xCAA82EE7 and goes further: after confirming the user has Internet access, admins should verify that the network and the network elements between the user's location and the Microsoft network are configured correctly, using Microsoft's network assessment tooling and the published Microsoft 365 URLs and IP address ranges.
Common causes
- No working Internet connection at the moment Teams tried to sign in, for example right after the PC wakes from sleep or while Wi-Fi reconnects.
- A firewall, VPN client or security app delaying or dropping the connection to Microsoft's sign-in service.
- A corporate proxy or network device that does not allow the endpoints Microsoft 365 needs.
- A slow or congested link where the request does not finish in time.
How to fix it
1. Confirm the connection and try again
Open any website to confirm the PC is online, then quit Teams fully and start it again. If the error appeared just after the PC woke from sleep, give the network a minute first. Microsoft's Office connection article tells admins to rule out errors caused by a lost Wi-Fi connection or by the system waking from hibernation before treating them as a real fault.
2. Check for apps or firewalls that block access
This is the step Microsoft gives users. As a general step, disconnect a VPN briefly if your company allows it, and check whether a recently installed security or firewall app coincides with the error. On a work PC, report the code to IT instead of disabling protection yourself.
3. Test the sign-in page in a browser
Microsoft's Office connection troubleshooting, which the Teams article uses for related codes, tests sign-in in Edge: open https://login.microsoftonline.com in a normal window and in an InPrivate window. If the page does not load or sign-in does not complete, the network, firewall or antivirus is the cause, not Teams.
4. Admins: check the network path to Microsoft 365
Microsoft's admin article tells admins to use its Network assessment tool to confirm the network between the user and Microsoft is configured correctly, and to compare firewall and proxy rules with the Microsoft 365 URLs and IP address ranges for the cloud the tenant uses. The Teams Sign in test in the Microsoft Remote Connectivity Analyzer at testconnectivity.microsoft.com checks the account from outside your network.
5. Update and then reset Teams
Select Settings and more, then Check for updates, in the Teams app. If the code persists on one PC only, reset new Teams under Settings, Apps, Installed apps, Microsoft Teams, Advanced options, Reset, as documented in Microsoft's cache article. The reset removes app data and personal settings.
If nothing works
Note the code from the lower-left of the Teams sign-in window, the time and the network you were on, and give them to your IT admin. Microsoft's support article says that when the status code cannot be solved by the user, the IT admin should receive it.
What we checked
Two official pages were read on 2026-11-19. The Microsoft Support article for Teams users lists 0xCAA82EE2 as a timeout with the connection and firewall guidance. The Microsoft Learn article Fix Teams sign-in errors lists 0xCAA82EE7 and 0xCAA82EE2 with the Internet access check, the network assessment step and the Microsoft 365 endpoints reference. The Office connection article and the Teams cache article on Microsoft Learn were read for the browser test and the reset steps. The error was not reproduced for this page.
Last checked: 2026-11-19.