Microsoft Teams signs you out repeatedly when you switch between work or school tenants. This happens because Teams stores cached credentials per tenant, and the sign-in cache becomes corrupted or conflicts with multiple accounts. You may also see a loop where you sign in, get signed out, and then sign in again. This article explains the root cause and provides step-by-step fixes, including clearing the Teams cache, resetting sign-in tokens, and configuring tenant switching settings.
You will learn how to fix the sign-out loop in the Teams desktop app on Windows 11 and Windows 10. We also cover the web client and mobile app. The fixes range from simple cache clears to policy changes in the Teams admin center.
Key Takeaways: Fix Teams Sign-Out Loops When Switching Tenants
- Teams cache folder (%appdata%\Microsoft\Teams): Clear this folder to remove corrupted sign-in tokens that cause repeated sign-outs.
- Windows Credential Manager: Delete the Teams and Microsoft Office credentials to reset the authentication state.
- Teams admin center > Users > User settings > Cross-tenant sync: Ensure that cross-tenant sync is not forcing sign-out during tenant switches.
- Sign-in options > Use another account: Use this option to switch tenants without triggering a full sign-out.
Why Teams Signs You Out When Switching Tenants
Teams uses the Microsoft Authentication Library to manage sign-in tokens. Each tenant has its own token cache. When you switch tenants, Teams must exchange the current token for a new one. If the token cache is corrupted, or if you have multiple accounts with overlapping email addresses, Teams may fail to refresh the token and sign you out.
Another cause is the presence of stale tokens from a previous version of Teams. The new Teams client on Windows 11 uses a different cache location than the classic client. If you upgraded, old tokens remain and conflict with new ones. This conflict often results in a sign-out loop.
How Tenant Switching Works in Teams
When you switch tenants, Teams clears the current session and loads the new tenant’s data. It does this by calling the sign-in endpoint with the tenant ID. If the token is invalid, Teams redirects you to the sign-in page. If the redirect fails because of a corrupted cache, Teams signs you out instead of showing the sign-in page.
Common Signs of the Sign-Out Loop
You may see a message like “We signed you out” or the app closes and reopens. Sometimes, Teams shows a blank window and then signs you out after a few seconds. You may also be asked to re-enter your password even though you just signed in.
Steps to Diagnose and Fix Repeated Sign-Outs in Teams
- Clear the Teams cache folder
Close Teams completely. Right-click the Teams icon in the system tray and select Quit. Press Win + R, type %appdata%\Microsoft\Teams, and press Enter. Delete all files and folders inside this directory. Do not delete the Teams folder itself. Restart Teams and sign in again. - Clear the Teams WebView2 cache
If the issue persists, clear the WebView2 cache. Press Win + R, type %localappdata%\Microsoft\TeamsWebView2, and press Enter. Delete the contents of this folder. This resets the embedded browser cache that stores tenant-specific cookies. - Remove saved credentials from Windows Credential Manager
Press Win + S, type Credential Manager, and open it. Select Windows Credentials. Look for entries that start with MicrosoftTeams or MicrosoftOffice. Click the arrow next to each entry and select Remove. Restart Teams. - Sign out and sign in using the correct tenant
In Teams, click your profile picture at the top right. Select Sign out. Then sign in again using the account that belongs to the tenant you want to use. Do not use the account switcher if it triggers the loop. - Use the “Use another account” option
When signing in, click Use another account instead of selecting a cached account. This forces Teams to create a fresh token for that tenant. - Switch tenants using the tenant picker
In Teams, click your profile picture, then select Switch tenant. If the picker is not available, use the web client to switch tenants and then sign back into the desktop app. - Check for multiple accounts with the same email
If you have the same email address in two tenants, Teams may not know which tenant to use. In the sign-in screen, select Options and then Sign in to an organization. Enter the tenant name or ID to force a specific tenant. - Reset Teams by reinstalling
If all else fails, uninstall Teams completely. Press Win + I to open Settings, go to Apps > Installed apps, find Microsoft Teams, and select Uninstall. After uninstalling, delete the %appdata%\Microsoft\Teams folder again. Then reinstall Teams from the Microsoft 365 portal.
If Teams Still Signs You Out After the Main Fix
Teams signs out when I switch tenants on the web
Clear the browser cookies for teams.microsoft.com and login.microsoftonline.com. In your browser settings, find the cookie section and delete cookies for these domains. Then sign in again. Also, disable browser extensions that block cookies or scripts.
Teams signs out on mobile when switching tenants
On the Teams mobile app, go to Settings > Account and sign out. Then clear the app cache. On Android, go to Settings > Apps > Teams > Storage > Clear Cache. On iOS, you may need to uninstall and reinstall the app.
Teams signs out after a policy change in the admin center
If an admin changed the tenant switching policy, Teams may sign you out to apply the new policy. Check with your admin. The policy is in Teams admin center > Users > User settings > Cross-tenant sync. If the policy blocks tenant switching, you cannot switch tenants without signing out.
New Teams Desktop vs Classic Teams vs Web Client: Sign-Out Behavior
| Item | New Teams Desktop | Classic Teams | Teams on the Web |
|---|---|---|---|
| Cache location | %appdata%\Microsoft\Teams | %appdata%\Microsoft\Teams | Browser cookies |
| Tenant switch method | Profile picture > Switch tenant | Profile picture > Switch tenant | Profile picture > Switch tenant |
| Sign-out trigger | Corrupted WebView2 cache | Corrupted token cache | Expired cookies |
| Fix complexity | Medium | Low | Low |
The new Teams desktop uses WebView2, which adds a separate cache layer. This makes the sign-out loop more likely after an upgrade. The classic Teams uses the same cache but without WebView2, so the fix is simpler. The web client is the easiest to troubleshoot because you only need to clear cookies.
For most users, clearing the Teams cache folder is the first and most effective fix. If that does not work, remove the Windows credentials. The web client is a good fallback when the desktop app is stuck in a loop.
After applying the fixes, test tenant switching by signing in to a different tenant and then switching back. Use the Switch tenant option in your profile menu. If the loop returns, repeat the cache clear and credential removal.
You can now switch between tenants without being signed out. Start by clearing the Teams cache and Windows credentials. If the problem persists, try the web client or reinstall Teams. For advanced control, use the Sign in to an organization option to specify the tenant ID directly.