Fix Teams Cannot Switch Work Accounts When Switching Between Tenants

You try to switch between work accounts in Teams, but the account picker shows no option to sign out or add another tenant. This typically happens when Teams caches the previous account and cannot refresh the authentication token. The root cause is often a stale credential cache, an incorrect tenant allow list, or a blocked sign-in policy. This article explains why the switch fails and gives you step-by-step fixes to clear the cache, reset the account, and verify tenant policies.

Why Teams Cannot Switch Between Work Accounts

Teams stores authentication tokens in several places on your Windows device. When you sign in to one tenant, the token is cached in the Windows Credential Manager and in the Teams app data folder. When you try to switch to another tenant, Teams reads the cached token first. If the token is still valid, Teams skips the sign-in prompt and loads the old tenant. This behavior is by design to reduce repeated logins, but it becomes a problem when you need to work in two tenants on the same machine.

Another common cause is a tenant policy that blocks cross-tenant sign-in. The Teams admin center controls external access and guest access. If the target tenant has disabled external access or if the source tenant has not added the target tenant as an allowed domain, the switch will fail silently. The third cause is a corrupted Teams cache. Over time, the cache files in %appdata%\Microsoft\Teams can become stale or corrupt, which prevents the account picker from showing the correct options.

How the Account Switch Works in Teams

When you click your profile picture in Teams and select Switch account, Teams first checks the local token cache. If a token exists for the current tenant, Teams displays a list of accounts that are already signed in. To add a new account from a different tenant, you must sign out completely. If the sign-out button is missing or grayed out, the token cache is corrupted or the policy prevents sign-out. The fixes below address each of these layers.

Steps to Fix the Account Switch Problem in Teams

Perform these steps in order. Test the switch after each step to see if the problem is resolved. You will need local administrator rights on your Windows device for step 2 and step 3.

1. Sign out of Teams completely
   Click your profile picture in the top-right corner of Teams. Select Sign out. Wait for the sign-in window to appear. Do not sign in yet. If the sign-out option is not visible, continue to step 2.
2. Clear the Teams credential cache
   Open Windows Credential Manager by searching for it in the Start menu. Click Windows Credentials. Scroll to the section that lists MicrosoftAccount and MicrosoftOffice16_Data. Find any entry that contains Teams or AAD. Click the arrow to expand the entry, then click Remove. Repeat for all entries that contain Teams or Microsoft.AAD.
3. Delete the Teams app cache folder
   Press Windows + R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter. Close Teams completely first. Select all files and folders in this directory and delete them. Do not delete the Teams installation folder, only the cache folder. Restart Teams and sign in with the first tenant.
4. Sign in to the second tenant using a private window
   After clearing the cache, sign in to the first tenant. Then click your profile picture and select Sign out. In the sign-in window, click Use another account. Enter the email address for the second tenant. This forces a fresh authentication token for the second tenant.
5. Verify the tenant allow list in the Teams admin center
   Open the Teams admin center at admin.teams.microsoft.com. Go to Org-wide settings > External access. Under External access with Teams and Skype for Business, confirm that the domain of the second tenant is not blocked. If it is blocked, remove the domain from the blocked list or add it to the allowed list. Save the change and wait up to 24 hours for propagation.
6. Check the sign-in policy in Microsoft Entra ID
   Open the Microsoft Entra admin center at entra.microsoft.com. Go to Users > User settings. Under App registrations, verify that the Users can sign in to apps setting is set to Yes. If it is set to No, change it to Yes and save.

If Teams Still Has Issues After the Main Fix

Sometimes the problem persists even after clearing the cache and verifying policies. Here are the most common related failures and their fixes.

Teams Shows a Blank Window After Signing Out

A blank Teams window usually means the cache folder was not fully deleted. Close Teams from the system tray by right-clicking the Teams icon and selecting Quit. Then repeat step 3. If the window still appears blank, restart Windows and try again.

The Sign-out Option Is Missing or Grayed Out

This happens when the Teams client cannot reach the authentication server to invalidate the token. Check your internet connection and verify that you can open login.microsoftonline.com in a browser. If the site loads, clear the DNS cache by running ipconfig /flushdns in an elevated command prompt.

Teams Signs You Back Into the Old Tenant Automatically

If Teams automatically signs you into the previous tenant, the token is still present in the Windows Credential Manager. Open Credential Manager again and look for entries that contain Microsoft.AAD or MicrosoftOffice16_Data. Remove all of them, then restart Teams. Also check if the Stay signed in option was selected during the last sign-in. Sign out and sign in again without selecting that option.

New Teams Desktop vs Teams on the Web: Key Differences

Item	New Teams Desktop	Teams on the Web
Account switching	Uses Windows Credential Manager cache	Uses browser cookies and session storage
Cache clearing	Delete %appdata%\Microsoft\Teams	Clear browser history and cookies
Sign-out reliability	Sometimes fails due to token cache	Usually reliable with a fresh browser session
Best for multi-tenant work	Good after cache reset	Better for quick switches with private browsing

If you frequently switch between two tenants, consider using Teams on the web in a private browser window for the second tenant. This avoids the desktop cache entirely and gives you a separate session for each tenant. The desktop app is still the best choice for calls and screen sharing, but the web version is a reliable fallback for account switching.

After applying the fixes above, test the switch by signing out and signing in with the second tenant. If the problem persists, contact your tenant administrator to confirm that the external access policy allows the second domain. You can also try the Ctrl + Shift + Escape shortcut to open Task Manager and end any lingering Teams background processes before restarting the app.