When you switch between work or school accounts in the Teams desktop app, the app can get stuck on the loading screen with a spinning circle. This happens most often after a tenant change, a password update, or a cached profile conflict. The root cause is usually a stale cache, corrupted credentials, or a Teams policy that blocks the new tenant. This article explains why the loading screen persists and gives you step-by-step fixes to get Teams working again.
Key Takeaways: Fixing the Teams Loading Loop After a Tenant Switch
- Teams cache folder: Clearing %appdata%\Microsoft\Teams removes corrupted files that cause the loading loop.
- Credential Manager: Removing saved Teams credentials forces a fresh sign-in and resolves authentication conflicts.
- Teams admin center > Users > Sign-in status: Check if the account is blocked or if multi-tenant access is disabled.
- Ctrl + Shift + Escape: Use Task Manager to end all Teams processes before restarting the app.
Why Teams Gets Stuck on Loading After a Tenant Switch
The Teams desktop app stores your sign-in data, chat history, and meeting settings in a local cache. When you switch tenants, Teams must clear this cache and reload everything for the new account. If the cache contains data from the old tenant, the app can fail to initialize and stay on the loading screen indefinitely.
Another common cause is the Windows Credential Manager. Teams saves your login tokens there. If the token for the old tenant is still present, the app tries to use it for the new tenant, which fails silently. The app then keeps retrying, showing the loading spinner.
A third cause is a policy setting in Teams admin center. Your organization may have set a policy that restricts which tenants you can sign into. If the new tenant is not allowed, Teams will not load past the splash screen.
How the Loading Screen Behaves
The loading screen shows the Teams logo and a spinning circle. It can last from a few seconds to several minutes. If it lasts longer than two minutes, the app is likely stuck. You may also see a blank white window or an error message about sign-in.
Steps to Clear the Teams Cache and Fix the Loading Screen
Follow these steps in order. Each step addresses a different cause. Test Teams after each step to see if the problem is resolved.
- Close Teams completely
Right-click the Teams icon in the system tray and select Quit. Then open Task Manager with Ctrl + Shift + Escape. Look for any Teams process under Processes or Details. Select each one and click End Task. This ensures no background process is locking the cache files. - Clear the Teams cache folder
Press Windows + R, type %appdata%\Microsoft\Teams, and press Enter. Delete all files and folders inside this directory. Do not delete the Teams folder itself. This removes corrupted cache files that cause the loading loop. - Remove saved credentials from Credential Manager
Open Control Panel and go to User Accounts > Credential Manager > Windows Credentials. Scroll to the Generic Credentials section. Look for entries that start with Teams or Microsoft Teams. Click the arrow next to each entry and select Remove. Confirm the removal for each one. - Restart Teams and sign in to the correct tenant
Launch Teams from the Start menu. The app will open a sign-in window. Enter the email address for the tenant you want to use. If you have multiple accounts, select Use another account and enter the correct one. Do not use the account switcher until the app loads completely. - Check the sign-in status in Teams admin center
If the loading screen persists, ask your IT admin to open Teams admin center and go to Users > Manage users. Search for your account and check the Sign-in status. If it says Blocked, the admin must unblock it. Also check the Authentication methods section to ensure your login method is allowed. - Verify the tenant is allowed in your policy
In Teams admin center, go to Teams > Teams policies. Look for a policy that mentions external access or multi-tenant. If a policy restricts tenants, the admin must add the new tenant to the allowed list. This is especially common in organizations that use Azure AD conditional access. - Reinstall Teams as a last resort
If none of the above works, uninstall Teams from Settings > Apps > Apps & features. Then reinstall the latest version from the official Microsoft website. This resets all local settings and usually fixes persistent loading issues.
If Teams Still Has Issues After the Main Fix
Teams Shows a Blank White Window After Sign-In
A blank window usually means the cache was cleared but the app cannot fetch the new tenant data. Restart Teams and wait for at least two minutes. If the window remains blank, close Teams and run the cache clear again, then restart your computer before opening Teams.
Teams Keeps Asking for the Same Password
This happens when the Credential Manager still holds an old token. Go back to Credential Manager and remove all entries that contain Teams or Microsoft Teams. Then sign in again with your password. If your organization uses multi-factor authentication, complete the verification prompt.
Teams Stays on Loading Only for the New Tenant
If the old tenant loads fine but the new one does not, the issue is likely a policy or license problem. Confirm that the new tenant has a valid Teams license assigned to your account. Also verify that the tenant is not in a restricted region or under a data residency policy that blocks your location.
Teams Fails to Switch Accounts at All
If the account switcher does not appear or the app does not respond, use the profile icon in the top right corner. Click it and select Sign out. Then sign in again with the new account. This forces a fresh authentication session and clears the tenant switch loop.
New Teams Desktop vs Teams on the Web: Key Differences
| Item | Teams Desktop App | Teams on the Web |
|---|---|---|
| Cache storage | Local folder in %appdata% | Browser cache and cookies |
| Tenant switching | Uses account switcher and cached tokens | Relies on browser session and cookies |
| Common loading fix | Clear local cache and Credential Manager | Clear browser cache and sign out of all accounts |
| Policy enforcement | Applies machine-level policies | Applies browser-level policies |
If the desktop app continues to fail, use Teams on the web as a temporary workaround. Go to teams.microsoft.com and sign in with the new tenant. This avoids the local cache issue entirely. Once you confirm the web version works, you can retry the desktop app after clearing the cache.
You can now fix the Teams loading screen by clearing the cache, removing old credentials, and verifying your tenant policy. Start with the cache clear because it resolves most cases. If the problem returns, check the sign-in status in Teams admin center and confirm your account is not blocked. For a quick workaround, use Teams on the web. Remember to always sign out before switching tenants to avoid the loading loop.