How To Fix Teams Sign-In Error Codes 0xCAA (2026)
A Teams sign-in error that starts with 0xCAA means the sign-in itself failed, not your meeting.
Microsoft documents several of these codes, and each one points to a different cause such as the clock, the network or your organization’s rules.
This guide covers the Teams desktop app on Windows, with the fix for each code taken from Microsoft’s own pages.
Quick answer
| Error code | What Microsoft says it means | First fix |
|---|---|---|
| 0xCAA20003 | Authorization problem | Correct the date and time |
| 0xCAA20004 | The request needs approval, or a Conditional Access policy affects sign-in | Contact your IT admin |
| 0xCAA82EE2 and 0xCAA82EE7 | Timed out, or the server name could not be resolved | Check internet and firewall |
| 0xCAA70004 and 0xCAA70007 | Server or proxy not found, or an interrupted download | Check proxy and network tools |
| 0xCAA90018 | Wrong credentials | Sign in with your Microsoft 365 account |
Find the error code first
Teams shows the status code in the bottom-left corner of its window when sign-in fails.
Write the code down exactly, because the fix depends on it and your IT admin will ask for it.
The order to try the fixes
- Read the code
- Fix date and time
- Check internet
- Update Teams
- Reinstall Teams
- Send code to IT
Most of these codes depend on your network or your organization, so expect to involve IT if the first steps do not work.
0xCAA20003: fix the date and time
Microsoft says 0xCAA20003 is an authorization problem and tells you to check that the date and time are correct.
Wrong clock settings also block secure https sites, which is why sign-in breaks.
- Open the Start menu, then open Settings.
- Go to Time and language, then Date and time.
- Turn on Set time automatically.
- Turn on Set time zone automatically.
With automatic time zone on, Windows also handles daylight saving time for you.
0xCAA20004: approval or a Conditional Access policy
Microsoft’s support page says this code means the request needs approval from a resource owner or an authorization server.
Its troubleshooting page says a Conditional Access policy is affecting the sign-in.
You cannot change those rules yourself, so ask your IT admin to confirm your account meets your organization’s Microsoft Entra ID policies.
0xCAA82EE2 and 0xCAA82EE7: network problems
0xCAA82EE2 means the request timed out, and 0xCAA82EE7 means the server name could not be resolved.
Microsoft’s troubleshooting page says the cause is no internet access or something between you and Microsoft’s network blocking the addresses and ports Teams needs.
- Confirm the PC is online by opening a normal website.
- Ask IT to run the Microsoft network assessment tool to check the network setup.
- Ask IT to confirm you can reach the endpoints listed in Microsoft 365 URLs and IP address ranges.
- Check whether other apps or a firewall are blocking access.
0xCAA70004 and 0xCAA70007
Microsoft’s support page describes 0xCAA70004 as a server or proxy that was not found.
It links this to a misconfigured proxy or a network inspection tool such as Fiddler that is not set up to decrypt https traffic.
The fix is to have IT stop that program and relaunch Teams, or configure the tool correctly and relaunch.
For 0xCAA70007, the same page says the download failed because the connection was interrupted, so check your internet and ask IT whether a firewall is blocking access.
Microsoft’s separate troubleshooting page also ties both codes, or the same sign-in trouble in other Office apps, to a known Office 2016 build issue.
0xCAA90018: wrong credentials
This code means your Windows credentials differ from your Microsoft 365 credentials.
Sign in again with the correct work or school email and password, and contact your IT admin if the code keeps coming back.
Who can fix each code
Some codes you can clear yourself, while others only your IT team can change.
| Error code | You can try | Needs IT |
|---|---|---|
| 0xCAA20003 | Set time and time zone automatically | Not listed by Microsoft |
| 0xCAA20004 | Nothing on your own | Review of Conditional Access and Entra ID policy |
| 0xCAA82EE2 and 0xCAA82EE7 | Confirm internet access | Firewall, ports and Microsoft 365 endpoints |
| 0xCAA70004 and 0xCAA70007 | Confirm internet access | Proxy settings and inspection tools |
| 0xCAA90018 | Sign in with the right email and password | If the code persists |
Update the Teams app
Microsoft says the desktop app normally updates itself, but a copy that missed an update can fail to sign in.
- Select Settings and more, the three dots next to your profile picture at the top right of Teams.
- Select Check for updates.
- Install any update and try to sign in again.
Reinstall Teams
Reinstall only if the error persists after the steps above.
- Uninstall Teams from Windows.
- Press Windows key and R, type %appdata%\Microsoft and press Enter.
- Delete the Teams folder.
- Download Teams again and, if you can, right-click the installer and choose Run as administrator.
What about CAA20002 and CAA2000B
Many people search for CAA20002 or CAA2000B, but Microsoft’s Teams sign-in pages do not list either code.
For any code that is not in its table, Microsoft says to note the code and send it to your IT admin.
The update and reinstall steps above are the general steps Microsoft gives for sign-in errors, so they are the safe ones to try.
Tools Microsoft points IT to
| Tool | What it does |
|---|---|
| Teams Sign-in diagnostic | Runs tests for one user and suggests a solution, and needs a Microsoft 365 admin account |
| Remote Connectivity Analyzer | Runs a Teams sign-in test for the user account you enter |
| Network assessment tool | Checks that the network is configured correctly for Teams |
| Teams debug logs | Go with a support request along with the error code |
Microsoft says the Sign-in diagnostic is not available in the GCC, GCC High, 21Vianet or Germany clouds, and the Remote Connectivity Analyzer test is not supported in GCC or GCC High.
When to contact IT or Microsoft
If nothing works, Microsoft says to open a support request and include the Teams debug logs and the error code shown on the sign-in screen.
IT admins can also run the Teams Sign-in diagnostic and the Remote Connectivity Analyzer sign-in test for the affected user.
If Teams opens but will not load, see Teams stuck on the loading screen.
Once you are in, Teams microphone and camera fixes and Teams screen sharing fixes cover the usual meeting problems.
If the problem is on a phone, read Teams mobile app login errors.