Fix Teams Desktop App Uses the Wrong Tenant After a Windows Update

After a Windows update, the Teams desktop app sometimes signs into the wrong Microsoft 365 tenant. You see your personal account or a different organization’s account instead of your work account. This happens when the Windows Credential Manager stores stale tokens from an old session. This article explains why the update resets the sign-in state and gives you the exact steps to clear the cache, remove old credentials, and force a fresh sign-in to the correct tenant.

You will also learn how to prevent this from happening again by adjusting the Teams sign-in settings and verifying the tenant ID after you sign in.

Why the Teams Desktop App Signs Into the Wrong Tenant After a Windows Update

Windows updates, especially feature updates like Windows 11 23H2, can reset the Teams app’s sign-in state. The update may invalidate the cached tokens that Teams uses to keep you signed in. When Teams restarts after the update, it tries to refresh the token using the Windows Credential Manager. If the credential manager holds a token from a previous session, Teams may pick up that token instead of the one for your current work account.

Another reason is that the Teams desktop app stores multiple account profiles. When the update clears the app’s local state, Teams may default to the first profile it finds. That profile might belong to a personal account or a different organization. The app does not automatically know which tenant you want to use.

The fix is to clear the Teams cache, remove the stale credentials from Windows Credential Manager, and then sign in again with your work account. This forces Teams to create a fresh token for the correct tenant.

What Causes the Credential Mismatch

The Windows Credential Manager stores web credentials and Windows credentials. Teams uses the web credentials for single sign-on. After a Windows update, the update process may modify the credential store. If you have multiple accounts, the update may cause Teams to read the wrong one. The result is that you see the wrong tenant name in the Teams title bar or in the account menu.

Steps to Clear Teams Cache and Remove Stale Credentials

Follow these steps in order. Do not skip any step. Each step removes a layer of stale data that causes the wrong tenant sign-in.

1. Sign out of Teams completely
   Open Teams. Click your profile picture at the top right. Select Sign out. Close the Teams window completely. Right-click the Teams icon in the system tray and select Quit.
2. Clear the Teams cache folder
   Press Win + R to open the Run dialog. Type %appdata%\Microsoft\Teams and press Enter. Delete the contents of this folder. Do not delete the folder itself. You can also delete the blob_storage and Cache subfolders if they exist.
3. Remove stale credentials from Windows Credential Manager
   Press Win + R, type control keymgr.dll, and press Enter. In the Credential Manager window, click Windows Credentials. Look for entries that start with MicrosoftTeams or Teams. Also look for entries that contain login.microsoftonline.com. Select each entry and click Remove. Confirm the removal.
4. Clear the web credentials for Teams
   Still in Credential Manager, click Web Credentials. Look for entries that contain login.microsoftonline.com or teams.microsoft.com. Remove those entries as well. This clears the single sign-on tokens.
5. Restart Teams and sign in with the correct account
   Open Teams. On the sign-in screen, click Use another account. Enter your work email address. Enter your password and complete multi-factor authentication if required. Teams will now create a fresh token for the correct tenant.
6. Verify the tenant name
   After signing in, click your profile picture. The tenant name appears next to your email address. Confirm that it matches your organization’s name. If it does not, repeat the steps and make sure you removed all Teams-related credentials.

Alternative Method: Use the Teams Sign-In Diagnostic Tool

If the manual steps do not work, use the Teams sign-in diagnostic tool. Sign in to the Microsoft 365 admin center. Go to Health > Diagnostics. Select Teams Sign-In. Run the diagnostic and follow the prompts. This tool checks your tenant configuration and can detect issues that cause wrong tenant sign-in.

If Teams Still Shows the Wrong Tenant After Clearing the Cache

Teams Desktop App Shows a Personal Account After Windows Update

This happens when the Teams app picks up a cached profile from a personal Microsoft account. After clearing the cache, make sure you sign in with the work account and not the personal one. You can also check the Windows Credential Manager for entries that contain live.com or outlook.com. Remove those entries as well.

Teams Desktop App Shows a Different Organization’s Tenant

If you work with multiple organizations, Teams may have stored a token for another tenant. After clearing the cache, use the Use another account option and enter the exact work email for the correct tenant. If the issue persists, check if the Teams policy in the admin center restricts sign-in to a specific tenant.

Teams Desktop App Keeps Signing Out After the Fix

This can happen if the Teams app cannot refresh the token because the credential store is corrupted. Run sfc /scannow in an elevated Command Prompt to repair system files. Then repeat the cache clearing steps. If the problem continues, reinstall Teams by uninstalling it from Settings > Apps and then reinstalling from the Microsoft 365 portal.

New Teams Desktop vs Teams on the Web: Key Differences

Item	New Teams Desktop	Teams on the Web
Credential storage	Uses Windows Credential Manager	Uses browser cookies
Cache location	Local folder in %appdata%	Browser cache
Impact of Windows update	Can reset sign-in state	Unaffected by Windows update
Sign-in method	Native sign-in window	Browser-based sign-in
Recommended for	Full desktop experience	Quick access without install

If you frequently encounter wrong tenant issues, consider using Teams on the web as a temporary workaround. It does not use the Windows Credential Manager, so it avoids the credential mismatch after updates.

Conclusion

You can now fix the Teams desktop app when it uses the wrong tenant after a Windows update. Clear the cache folder and remove stale credentials from Windows Credential Manager to force a fresh sign-in. Verify the tenant name after signing in to confirm the fix. To prevent future issues, use the Teams sign-in diagnostic tool after major Windows updates. You can also pin the correct tenant URL in your browser for quick access.