New Teams - How do you remove users from the "Pick an account" / Login screen?

Anonymous
2023-12-01T12:57:48+00:00

While testing "New Teams" I have noticed that the "Pick an account" / Login screen shows the previous users that have logged in, even if they have clicked "sign out".

When clicking on those users, it also logs them in without asking for a password.

After reading other posts here, I have tried deleting the cache here: %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe

And also deleting the data in this folder: %LocalAppData%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy

Doing this has stopped the accounts from being logged in without a password, but the accounts still appear on the "Pick an account" / Login screen.

They do not show in classic teams or any other application and there are no additional accounts in the "Access Work and School" windows setting page.

I have also tried to fully remove and reinstall Teams but the accounts are still visible.

Does anyone have a solution for this?

Thanks

EDIT:

I have found a possible solution:

Delete:
%LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe
%LocalAppData%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
%LocalAppData%\Microsoft\OneAuth
%LocalAppData%\Microsoft\TokenBroker
%LocalAppData%\Microsoft\IdentityCache

Then restart the PC.

This will sign out all Microsoft products but does remove the users from the login list and removed their login details, meaning a password is required to login to Teams.

Microsoft Teams | Microsoft Teams for education | Sign up and Sign in | Switch between accounts

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

99 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-12-01T13:42:06+00:00

    Hi, there are no accounts listed in "Access work or school" but the previously logged in accounts are still visible in new teams.

    Was this answer helpful?

    60+ people found this answer helpful.
    0 comments
  2. Anonymous
    2023-12-08T13:02:45+00:00

    I have found a possible solution:

    Delete:
    %LocalAppData%\Packages\MSTeams_8wekyb3d8bbwe
    %LocalAppData%\Packages\Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
    %LocalAppData%\Microsoft\OneAuth
    %LocalAppData%\Microsoft\TokenBroker
    %LocalAppData%\Microsoft\IdentityCache

    Then restart the PC.

    This will sign out all Microsoft products, but does remove the users from the login list and removed their login details, meaning a password is required to login to Teams.

    Was this answer helpful?

    50+ people found this answer helpful.
    0 comments
  3. Anonymous
    2023-12-08T23:39:39+00:00

    Thanks to everyone who has put effort into fixing this. Deleting a bunch of system generated folders solves an issue temporarily for us, but it is hardly a solution.

    Microsoft should be tasking their entire Dev team toward resolving this (or asking Googles AI Engine how to fix it). This is an absolutely disgraceful wholescale security risk. EVERYONE who ever logged onto Teams on a Shared Access Computer leaves their environment open to any casual passer by and clicks on their logon ICON.

    Come on MSFT GET THIS FIXED...

    Was this answer helpful?

    40+ people found this answer helpful.
    0 comments
  4. Anonymous
    2023-12-04T15:50:15+00:00

    Hi, I have censored the emails/names, but this is the screen I am referring to.

    I have tested this on different computers, on Windows 10 and 11, and have not seen any way to remove the names from this list.

    Was this answer helpful?

    40+ people found this answer helpful.
    0 comments
  5. Anonymous
    2023-12-14T10:57:08+00:00

    Hi,

    No need to delete all the folders.

    1. Check if process ms-teams.exe is still running and kill it.
    2. Rename %LocalAppData%\Microsoft\OneAuth\accounts or remove the content.
    3. Start Teams, the primary account will automatically be recreated.

    Cheers,

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments