Teams call link opens the wrong chat instead of the call

Symptom

You receive a meeting link by email or chat. Clicking opens Teams - but instead of the call you land:

• in a 1:1 chat in your home org
• in a channel chat of a completely different org
• on the home view of a tenant where you did not expect to be

The actual call happens without you.

Cause

The Teams desktop client has an active tenant. When you click a link that belongs to a different org, Teams attempts routing - sometimes it lands in a similarly named chat in the current tenant instead of the correct call.

Older versions of the classic client did this often. The new Teams client is better but not perfect.

Fix 1: incognito + browser

The reliable path:

1. Right-click the meeting link, “Open in private window”
2. The private browser window forces an explicit account login
3. Microsoft reads the tenant from the link, routes correctly
4. In the browser, click “Join in browser” or let it launch the Teams app

Private window benefit: no existing sessions, no stuck SSO.

Fix 2: switch tenant before clicking

If you know the link belongs to Org X:

1. Open the tenant switcher top right in Teams
2. Click Org X, wait for Teams to switch
3. Only then click the meeting link

That way you are already in the correct tenant when routing happens - no room for confusion.

Fix 3: when you already landed wrong

You ended up in the wrong chat, the call runs without you:

1. Do not click the link again in the desktop client (would route to the same tenant)
2. Instead copy the link from the original email into a browser
3. Open in private window - sign in cleanly and join

Prevention: browser profiles

If you constantly hop between orgs, set up a browser profile per identity (Chrome or Edge profiles). Always open meeting links in the matching profile - drag-and-drop or right-click “Open in profile X”.

Useful links

• Microsoft Support - Join a Teams meeting
• Chrome Profiles - separate identities cleanly
• Edge Profiles