Share via

How can I access my accounts using the MS teams and outlook apps as I keep getting an error message.

Niki Roach 0 Reputation points
2026-05-15T20:24:31.14+00:00

I'm able to access my Teams and outlook via a browser but when I try and login via the apps I'm not able to access my 365 account. I keep getting an error message shown below. This relates to a time when I used my work email (the one my account is linked to) to access a clients sharepoint. I no longer have access and the client has advised I've been removed from their organizational lists and am not visible. I can't remove the account details from the login screen and when I try and login I get the following error message.

Please help!

Error message:

Request Id: [Moderator note: Personally Identifiable Information removed]

Correlation Id: [Moderator note: Personally Identifiable Information removed]

Timestamp: 2026-05-15T20:16:21Z

Message: AADSTS90072: User account 'hidden for security' from identity provider '[Moderator note: Personally Identifiable Information removed]' does not exist in tenant 'hidden for security' and cannot access the application '[Moderator note: Personally Identifiable Information removed]'(Microsoft Office) in that tenant. The account needs to be added as an external user in the tenant first. Sign out and sign in again with a different Azure Active Directory user account

Microsoft Teams | Microsoft Teams for business | Sign up and Sign in | Other

1 answer

Sort by: Most helpful
  1. Q&A Assist
    2026-05-15T20:24:49.97+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    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:

    1. Remove old work/school account from Windows
      • Open Windows SettingsAccountsAccess work or school (briefcase icon).
      • If any old organization or client account is listed, select it and choose Disconnect.
    2. Remove cached credentials and identity tokens
      • Open Control PanelCredential ManagerWindows 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.
    3. Reinstall and sign in to Microsoft 365 apps
      • Uninstall Microsoft 365 from SettingsAppsInstalled 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.
    4. 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.

    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:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.