Fix Teams Meeting Link Opens the Wrong Account After a Meeting Policy Change

When you click a Teams meeting link, Teams may sign you into the wrong account, especially after an admin changes meeting policies. This usually happens because the Teams desktop app caches your previous sign-in state and does not re-evaluate which account should handle the meeting. The fix involves clearing the cached credentials and setting the correct default account in Teams. This article explains why the wrong account appears and provides step-by-step instructions to resolve it.

Why a Meeting Policy Change Causes the Wrong Account to Open

Teams uses a single default account for joining meetings. When you click a meeting link, the desktop app checks its local cache to find which account is currently signed in. If an admin changes a meeting policy that affects meeting join behavior, Teams may not refresh this cache immediately. Instead, it uses the last signed-in account, which may be different from the account that received the meeting invitation.

The root cause is that Teams stores authentication tokens in Windows Credential Manager and in its own local profile. These tokens are tied to a specific user. When a policy change triggers a re-evaluation of meeting permissions, Teams might not clear these tokens, so it keeps using the old account. Additionally, if you have multiple accounts in Teams, the app may pick the first one in its list rather than the one associated with the meeting organizer.

How Teams Decides Which Account to Use

When you open a meeting link, Teams checks the meeting invitation for the organizer’s tenant. If the signed-in account belongs to a different tenant, Teams attempts to switch to an account that matches. If no match exists, it may prompt you to choose. However, if the cached token belongs to a personal account, Teams may open that account without prompting, even if the meeting is from a work account.

Steps to Clear Cached Credentials and Set the Correct Default Account

Follow these steps in order. Each step addresses a different layer of the problem.

1. Sign out of all accounts in Teams
   Open Teams, click your profile picture at the top right, then select Sign out. If you have multiple accounts, sign out of each one individually. This clears the active session but not the cached tokens.
2. Clear cached credentials from Windows Credential Manager
   Press Win + R, type control /name Microsoft.CredentialManager, and press Enter. Under Windows Credentials, find entries that start with Teams or Microsoft Teams. Click the arrow next to each entry, then select Remove. Confirm the removal.
3. Clear Teams local cache files
   Close Teams completely. Press Win + R, type %appdata%\Microsoft\Teams, and press Enter. Delete the contents of the Cache, Code Cache, and GPUCache folders. Do not delete the entire Teams folder, as this may break your installation.
4. Sign back into Teams with the correct account
   Reopen Teams. On the sign-in screen, enter the email address that is associated with the meeting invitation. After signing in, go to Settings > Accounts and verify that the correct account is listed as the primary account.
5. Test the meeting link
   Open the meeting link from your calendar or email. Teams should now open the correct account. If it still opens the wrong account, proceed to the next step.
6. Check meeting policy settings in the Teams admin center
   Go to Teams admin center > Meetings > Meeting policies. Select the policy assigned to the affected user. Under Meeting join, ensure that Meeting join notification is set to Enabled. This forces Teams to ask which account to use when multiple accounts are available.

If Teams Still Opens the Wrong Account After the Main Fix

Teams Opens a Personal Account Instead of a Work Account

This happens when the personal account is the default in Teams. After signing out, go to Settings > Accounts and select Add account to add your work account. Then, right-click your work account and choose Set as default. If the option is not available, sign out of the personal account first.

Meeting Link Opens the Teams Web App Instead of the Desktop App

If the meeting link opens in a browser, Teams may not be set as the default handler for meeting links. In the Teams desktop app, go to Settings > General and check the box for Register Teams as the default app for joining meetings. Then close and reopen Teams.

Policy Change Did Not Take Effect for All Users

Meeting policy changes can take up to 24 hours to propagate. If the issue persists, wait a few hours and try again. Also, verify that the correct policy is assigned to the user in Teams admin center > Users > Manage users > Policies.

Teams Desktop App vs Teams on the Web: Key Differences

Item	Teams Desktop App	Teams on the Web
Account cache	Stores tokens locally in Credential Manager	Uses browser cookies and session storage
Default account handling	Uses the last signed-in account unless changed	Uses the account active in the browser profile
Policy enforcement	Applies immediately after sign-in	Applies on each page load
Meeting join notification	Controlled by policy and may be ignored if cached	Always prompts when multiple accounts are signed in

After following these steps, you can click meeting links and land in the correct account every time. For recurring issues, set a reminder to check your default account in Teams settings once a week. If you manage policies, use the Meeting join notification setting to reduce confusion for users with multiple accounts.