When you switch between work and school accounts in Teams, the app sometimes freezes or fails to open entirely. This usually happens because cached credentials from the previous tenant conflict with the new sign-in. This article explains the technical root cause and gives you step-by-step fixes to clear the cache, reset the app, and switch tenants reliably.
You will also learn how to prevent the problem from recurring by using the correct sign-out workflow. Follow the instructions below to get Teams working again within minutes.
Key Takeaways: Fix Teams Tenant Switching Issues
- Teams admin center > Users > Sign-in status: Check if your account is blocked or requires reauthentication.
- Ctrl+Shift+M: Opens the Teams meeting window directly, bypassing the main app if it fails to launch.
- Clear cached credentials via Windows Credential Manager: Removes stale tenant tokens that cause the app to hang.
Why Teams Fails to Open After a Tenant Switch
Teams stores authentication tokens and cached user data in a local folder on your device. When you switch from one tenant to another, the app tries to reuse the existing cache. If the cache contains tokens from the previous tenant that are no longer valid, the sign-in process gets stuck. The result is a blank window, a freeze, or the app not opening at all.
Another common cause is the Teams background process continuing to run after you sign out. When you relaunch the app, it picks up the old process state instead of starting fresh. This is especially noticeable when you switch between a work account and a school account, because each tenant has its own identity provider and policy settings.
Windows Credential Manager also plays a role. Teams stores your sign-in credentials there, and if the credentials for the old tenant remain, the new sign-in request may conflict. Clearing these credentials is often the fastest way to resolve the issue.
What Happens During a Normal Tenant Switch
When you sign out of Teams, the app is supposed to clear the local cache and terminate all background processes. But if you close the window instead of using the sign-out option, the background process stays alive. The next time you open Teams, it attempts to restore the previous session, which includes the old tenant’s data. That restoration is where the app fails.
Steps to Clear Teams Cache and Reset the App
Follow these steps in order. They are safe and will not delete your chat history or files.
- End all Teams processes
Open Task Manager by pressing Ctrl+Shift+Escape. Look for any process named Microsoft Teams. Right-click each one and select End task. This ensures no background process is holding old tenant data. - Clear the Teams cache folder
Press Win+R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter. Delete all files and folders inside this directory. Do not delete the Teams folder itself. If a file is in use, skip it and continue after restarting. - Clear credentials from Windows Credential Manager
Open Control Panel and go to User Accounts > Credential Manager > Windows Credentials. Look for any entry that starts with microsoftteams or contains teams.microsoft.com. Click the arrow next to each entry and select Remove. Confirm the removal. - Restart Teams
Launch Teams from the Start menu. You will be prompted to sign in. Enter your credentials for the target tenant. The app should now open normally. - Sign out properly after switching
To avoid future issues, always sign out using the profile picture in the top right corner, then select Sign out. Do not just close the window. This clears the cache correctly and prevents the conflict.
Alternative: Use the Teams Web App
If the desktop app still fails, use Teams on the web at teams.microsoft.com. The web app does not rely on local cache and will not have the same switching problem. You can continue working while you fix the desktop app.
If Teams Still Has Issues After the Main Fix
Teams Opens but Shows a Blank White Screen
This usually means the cache was not fully cleared. Repeat the cache deletion steps and also clear the %appdata%\Microsoft\Teams\blob_storage folder. Then restart the app.
Teams Keeps Asking for Credentials
This indicates that the sign-in token has expired or the tenant policy requires reauthentication. Check if your account is blocked in the Teams admin center under Users > Sign-in status. If you are a user, contact your IT admin to verify that your account is active.
Teams Fails to Open After a Windows Update
Windows updates can sometimes corrupt the Teams installation. Repair the app by going to Settings > Apps > Installed apps, find Microsoft Teams, click the three dots, and select Advanced options. Then click Repair. If that does not work, uninstall and reinstall Teams.
New Teams Desktop vs Teams on the Web: Key Differences
| Item | New Teams Desktop | Teams on the Web |
|---|---|---|
| Cache location | Local app data folder | Browser cache only |
| Tenant switching | Can conflict with old tokens | No local token conflict |
| Offline support | Full offline access | Limited offline mode |
| Background processes | Run in Task Manager | None |
| Installation required | Yes | No |
Now you can clear the Teams cache, remove stale credentials, and restart the app to fix tenant switching problems. Always sign out properly to prevent future issues. For a quick workaround, use Teams on the web while the desktop app is being repaired. As an advanced tip, you can press Ctrl+Shift+M to open a meeting window directly, which sometimes bypasses the startup failure.