When you switch between work accounts in the Teams desktop app, it may sign you into the wrong tenant. This happens because Teams caches account and tenant data on your device, and the cache does not always refresh correctly. The result is that you see the wrong company’s channels, chats, or meetings. This article explains why the cache causes the problem and provides step-by-step fixes to force Teams to load the correct tenant.
Key Takeaways: Fixing Tenant Switching in Teams Desktop
- Teams app settings > Accounts: Sign out of all accounts to clear cached tenant data.
- Clear Teams cache folder %appdata%\Microsoft\Teams: Removes corrupted files that cause wrong tenant loading.
- Registry key HKEY_CURRENT_USER\Software\Microsoft\Office\Teams: Delete to reset tenant-specific settings.
Why Teams Desktop Loads the Wrong Tenant After Switching
Teams desktop stores a local cache of user profiles, tenant IDs, and authentication tokens. When you switch accounts, Teams reads this cache to speed up sign-in. If the cache contains stale or mixed data from the previous tenant, Teams may apply that data to the new account. This results in the desktop app showing the wrong tenant’s resources even though you signed in with the correct credentials.
Another cause is the authentication token cache. Teams uses the Web Account Manager on Windows and a separate token store. If tokens from two tenants share the same user principal name, the app can pick the wrong token. This is common when you have accounts with the same alias in different domains, for example john@contoso.com and john@fabrikam.com.
The issue is not a network problem or a permission problem. It is purely a local data problem. Clearing the cache and resetting the authentication state forces Teams to download fresh tenant information from Microsoft 365. This is why the fixes below focus on removing cached data rather than changing server settings.
How Teams Stores Tenant Data Locally
Teams stores tenant data in three main locations on Windows:
- The profile cache in %appdata%\Microsoft\Teams
- The Web Account Manager token store managed by Windows
- Registry keys under HKEY_CURRENT_USER\Software\Microsoft\Office\Teams
Each location holds different pieces of the sign-in state. The profile cache holds user interface data. The token store holds authentication tokens. The registry holds settings like the last logged-in tenant. When any of these get out of sync, Teams can show the wrong tenant.
Steps to Force Teams to Load the Correct Tenant
Use the following steps in order. Start with the simplest fix and move to the more thorough ones only if needed.
- Sign out of all accounts in Teams
Open Teams and click your profile picture at the top right. Select Manage account and sign out of every account listed. Then close Teams completely by right-clicking the Teams icon in the system tray and choosing Exit. This clears the active session but not the cache. - Clear the Teams cache folder
Press Ctrl+R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter. In File Explorer, select all files and folders inside the Teams folder and delete them. Do not delete the Teams folder itself. This removes cached profiles, logs, and temporary files. - Clear the Web Account Manager tokens
Open Windows Settings by pressing Windows+I. Go to Accounts > Email & accounts. Find the Microsoft account or work account that Teams uses and click Remove. This clears the token stored by Windows. You will need to sign in again after this step. - Delete the Teams registry key
Press Ctrl+R, type regedit, and press Enter. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\Teams. Right-click the Teams key and select Delete. Confirm the deletion. This resets tenant-specific settings such as the last used tenant ID. - Restart Teams and sign in to the correct tenant
Launch Teams again. You will see the sign-in screen. Enter the credentials for the tenant you want to use. After sign-in, verify that the correct company name appears in the top left corner of the app.
If the Wrong Tenant Still Appears
If the problem persists after clearing the cache and tokens, the issue may be with the Teams app installation itself. Uninstall Teams completely, then reinstall it. Use the following steps:
- Uninstall Teams
Go to Settings > Apps > Installed apps. Find Microsoft Teams and click Uninstall. Confirm the action. - Delete the remaining Teams folders
After uninstalling, delete the folders %appdata%\Microsoft\Teams and %localappdata%\Microsoft\Teams if they still exist. - Reinstall Teams
Download the latest Teams desktop client from the Microsoft 365 admin center or the Teams website. Install it and sign in with the correct account.
If Teams Still Has Issues After the Main Fix
Teams Shows a Blank Window After Switching Accounts
A blank window occurs when the cache is cleared but the app does not rebuild the UI. Close Teams, press Ctrl+Shift+Escape to open Task Manager, and end all processes named Teams. Then restart Teams. This forces a fresh UI load.
Teams Keeps Asking for Credentials After Clearing Cache
This is normal after clearing tokens. Teams needs to re-authenticate. If the prompt loops, check that your system time is correct and that your network allows access to login.microsoftonline.com. Also verify that you are not blocked by a conditional access policy.
Wrong Tenant Appears in the Web Version Too
If the web version also shows the wrong tenant, the issue is not local. Clear your browser cache and cookies for the Teams domain. Then sign in again. If the problem remains, contact your IT admin to check if you have multiple accounts with the same user principal name in different tenants.
Teams Desktop vs Teams on the Web: Key Differences
| Item | Teams Desktop | Teams on the Web |
|---|---|---|
| Cache location | Local appdata folder and registry | Browser cache and cookies |
| Token storage | Windows Web Account Manager | Browser session storage |
| Tenant switching behavior | Can cache multiple tenants and mix them | Usually isolated per browser profile |
| Fix for wrong tenant | Clear appdata and registry | Clear browser cache and cookies |
Teams desktop is more prone to the wrong tenant issue because it stores data in multiple locations. The web version is simpler but does not support all features like background blur in calls. For business users who switch tenants daily, the desktop app is still the recommended option, but you must maintain the cache properly.
Now you can clear the Teams cache, remove the registry key, and reset the Web Account Manager tokens to force the correct tenant. Start with the sign-out and cache clearing steps. If the issue returns, check if you have multiple accounts with the same alias. Use the keyboard shortcut Ctrl+Shift+Escape to close Teams processes when a blank window appears.