TeamsFixer
de en

Tenant is selectable but sign-in still fails

You see the org in the tenant switcher, click it, nothing works. Account shown, icon appears, then error. Here is the workaround.

Last verified:

Affected systems

windows macos

Quick fixes

  • Find a 'we are trying to reach you' email and click the link - opens Teams in the browser
  • Clear browser cache and cookies for teams.microsoft.com
  • Reset the Teams cache fully

Symptom

In the Teams tenant switcher (top right next to your profile picture) you see the organization. You click it, the icon appears, maybe even the welcome animation - then everything disappears and Teams throws a vague error or hangs on the splash screen.

This is the scenario that hits consultants and multi-tenant users hard: everything looks like it works, then fails.

Workaround: via the reach-you email

This is the trick most people discover by accident: every Teams email notification (meeting invite, new message, “we are trying to reach you”) contains a link that targets the foreign tenant directly.

  1. Search your inbox for a recent Teams email from the problem organization
  2. Click the “Open in Microsoft Teams” link
  3. Teams Web opens, signs in cleanly to the correct tenant

This is not coincidence: the email link contains a tenant hint that bypasses the SSO conflict in the desktop client. In the web you get a clean browser session without the desktop client’s stuck cache.

Real fix: reset the cache

The email trick is a workaround, not a cure. For a permanent fix:

Windows

  1. Quit Teams completely (Task Manager, all processes)
  2. Delete both cache folders:
%appdata%\Microsoft\Teams
%localappdata%\Packages\MSTeams_8wekyb3d8bbwe\LocalCache
  1. Open Credential Manager, delete every Microsoft entry
  2. Clear browser cookies for login.microsoftonline.com and teams.microsoft.com
  3. Reboot, reopen Teams, sign in fresh

macOS

  1. Quit Teams (Cmd + Q in Teams, plus Activity Monitor for stragglers)
  2. Delete the cache:
~/Library/Application Support/Microsoft/Teams
~/Library/Group Containers/UBF8T346G9.com.microsoft.teams
  1. Open Keychain Access, delete every Microsoft and Office entry
  2. Clear Safari/Chrome cookies for login.microsoftonline.com
  3. Reboot, open Teams, sign in fresh

When that does not help

  • Conditional Access: A policy may block exactly this tenant-switch combination. Open in the web browser and capture the correlation ID - IT can use it.
  • Multiple MSA identities in the browser: If your browser is signed into multiple Microsoft accounts simultaneously, the login flow can get confused. Use a private window for testing.
  • Re-add as guest: If your guest invite is ancient, a re-invite from the foreign admin can break the deadlock.

Related errors