Launching Microsoft Teams to attend a scheduled business meeting or communicate with colleagues, only to be halted by a persistent error screen reading “We’re sorry—we’ve run into an issue” (frequently accompanied by error codes such as caa70004, caa20003, or caa50024) is an immediate disruption. Clicking the “Try again” button simply spins the interface in an endless authentication loop before returning to the exact same failure screen.
This persistent login loop strikes both Classic Teams and the New Microsoft Teams app on Windows 11 and macOS. The failure is typically caused by stale single sign-on (SSO) authentication tokens, corrupted Edge WebView2 runtime caches, expired workplace account bindings in Windows Credential Manager, or Microsoft Entra ID (Azure AD) device registration desynchronisations. This tutorial walks you through comprehensive methods to break the login loop and restore your Teams workspace.
Method 1: Perform a Complete Microsoft Teams Cache Reset
Stale identity tokens and corrupted local storage databases inside the Teams client profile represent the single most common cause of authentication deadlocks. Purging the cache forces Teams to negotiate an uncompromised OAuth2 token exchange.
For the New Microsoft Teams (Windows 11):
- Right-click the Teams icon in the system tray and select Quit.
- Press Windows + R to open the Run dialogue.
- Type the following path and press Enter:
%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams - Select all files and folders inside this directory (press Ctrl + A) and press Delete.
- Alternatively, reset the app via Settings: open Settings > Apps > Installed apps, locate Microsoft Teams, click the three dots, select Advanced options, and click Reset.
For Classic Microsoft Teams:
- Exit Classic Teams completely.
- Press Windows + R, type
%appdata%\Microsoft\Teams, and press Enter. - Delete all files and folders located within this directory.
- Relaunch Teams.
Method 2: Clear Stale Teams Credentials from Windows Credential Manager
Windows Credential Manager stores saved passwords and Modern Authentication tokens. If an enterprise password was changed or a conditional access policy updated, cached tokens will cause authentication to fail repeatedly.
- Press the Windows key, type Credential Manager, and open the app.
- Click Windows Credentials on the right.
- Scroll down to the Generic Credentials section.
- Locate all credential entries beginning with:
msteams_authtokenMicrosoftAccount:user=TeamsorMicrosoftOffice16_Data
- Click the downward arrow next to each entry and click Remove.
- Restart your computer. When you open Teams, enter your email and password afresh.
Method 3: Disconnect and Reconnect Workplace Account in Windows Settings
Microsoft Teams leverages the Windows Web Account Manager (WAM) broker. If your work or school account profile in Windows becomes desynchronised with your organization’s Microsoft Entra ID tenant, Teams enters a permanent login loop.
- Press Windows + I to open Settings.
- Select Accounts in the left sidebar, then click Access work or school.
- Locate the business or educational account associated with your Teams login.
- Click on the account and click Disconnect. Confirm the disconnection.
- Restart your computer.
- Return to Settings > Accounts > Access work or school and click Connect.
- Sign in with your enterprise credentials to re-register your device identity with the tenant.
- Launch Microsoft Teams.
Method 4: Clear Microsoft Teams Cache on Mac (macOS)
If you are encountering the login loop on a Mac, Teams stores identity tokens inside your user library and the macOS Keychain.
- Quit Microsoft Teams (Command + Q).
- Open Finder, press Shift + Command + G, and enter:
~/Library/Application Support/Microsoft/Teams - Move all files inside this folder to the Trash.
- Open Spotlight, type Keychain Access, and press Enter.
- In Keychain Access, search for Teams.
- Delete entries labelled Microsoft Teams Identities Cache and com.microsoft.teams.
- Restart your Mac and sign into Teams.
Microsoft Teams Login Error Reference Table
Consult this reference guide to match error codes with targeted solutions:
| Error Code | Underlying Cause | Recommended Solution |
|---|---|---|
| Error caa70004 | Network timeout or hung TLS handshake | Reset network stack; check proxy or VPN configurations |
| Error caa20003 | Corrupted WAM authentication token | Disconnect and reconnect Work or School account in Settings |
| Error caa50024 | Device registration requirement failed in Entra ID | Run dsregcmd /status; re-join device to Azure AD |
| Endless redirect to login screen | Corrupted WebView2 runtime cache | Reset New Teams via Settings > Apps > Installed Apps > Reset |
| “We’ve run into an issue” immediately on boot | Stale Windows Credential Manager tokens | Delete msteams_authtoken entries in Credential Manager |
Verifying Service Availability via Teams Web Client
If app-level troubleshooting does not immediately resolve the login loop, verify whether the issue is isolated to the desktop client by visiting the Microsoft Teams web application at teams.microsoft.com inside an InPrivate or Incognito browser window. If you can authenticate successfully on the web, your account and tenant licensing are in good standing, confirming that a desktop client reset or complete reinstallation will resolve the issue.