Additional sign-in or account-related issues within Microsoft Teams for business
The error indicates that the desktop apps are trying to sign in against a tenant where the account no longer exists (for example, the former client’s tenant), even though the account still works in the correct tenant via the browser. Local identity/tenant information cached on the device is causing the apps to use the wrong context.
To fix this, clear the old work/school association and cached credentials, then reinstall and sign in only with the correct account/tenant:
- Remove old work/school account from Windows
- Open Windows Settings → Accounts → Access work or school (briefcase icon).
- If any old organization or client account is listed, select it and choose Disconnect.
- Remove cached credentials and identity tokens
- Open Control Panel → Credential Manager → Windows Credentials.
- Remove any entries that reference the old organization/client account or its tenant.
- In File Explorer, open each of these paths (Windows + R → paste path → Enter) and delete the contents of the folder (if a subfolder cannot be deleted, open it and delete inside):
-
%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe -
%LocalAppData%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy -
%LocalAppData%\Microsoft\OneAuth -
%LocalAppData%\Microsoft\TokenBroker -
%LocalAppData%\Microsoft\IdentityCache
-
- Restart the computer.
- Reinstall and sign in to Microsoft 365 apps
- Uninstall Microsoft 365 from Settings → Apps → Installed apps.
- Go to https://www.office.com in a browser and sign in with the correct work account (the one that works in the browser and belongs to the current tenant, not the old client tenant).
- From there, use Install apps to download and install the desktop apps.
- When prompted in Teams/Outlook, sign in only with the correct work account. If a sign-in screen shows the old client account, choose Use another account or Sign in with a different account and enter the correct one.
- If the error persists
- Because the message explicitly mentions that the account does not exist in the tenant and suggests signing in with a different Azure AD account, contact the current organization’s IT admin to confirm:
- The account is active in the correct tenant.
- There are no conditional access or compliance policies blocking the device.
- Because the message explicitly mentions that the account does not exist in the tenant and suggests signing in with a different Azure AD account, contact the current organization’s IT admin to confirm:
These steps remove the old tenant association and corrupted identity caches so Teams and Outlook can authenticate only against the correct Microsoft 365 tenant, matching the behavior that already works in the browser.
References: