Share via

"Unknown Users" appear on Teams

Anonymous
2023-09-05T16:02:56+00:00

I am having an issue where several user accounts when re-enabled via AD appear as "Unknown User" on Teams.

I conducted a few tests on users who were recently terminated to see if they show as "Unknown User" and did the following:

-Re-enabled their account

-Moved their AD account to an active OU

-Granted them an M365 license

-Synced the directory

When I attempted to search for those users on Teams, two of them did not appear and one did.

I, then disabled and then re-enabled their account whilst not removing their licenses. Synced the users and then attempted to search those accounts via Teams and still received the same error.

The issue is when I re-enable accounts for users who are returning to the company, they should not appear as "Unknown User."

I also made sure to sync those users via Azure Active Directory.

Please assist.

Microsoft Teams | Microsoft Teams for business | Other

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 No comments

5 answers

Sort by: Most helpful
  1. Anonymous
    2023-09-11T14:30:06+00:00

    Hello Anna,

    Thank you for your response. I am relatively new to PS scripting. Where would I enter this script?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-09-07T10:26:16+00:00

    Yes, the “UsersPermissionToReadOtherUserEnabled” setting can only be changed via PowerShell. There is no option to change this setting in the Microsoft Teams Admin Center or any other GUI. You can use the Set-CsTeamsClientConfiguration cmdlet in PowerShell to change this setting for your tenant.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-09-06T20:27:10+00:00

    Hi Luis I'm AnnaThomas and I'd happily help you with your question. In this Forum, we are Microsoft consumers just like yourself. One possible solution that has worked for some users in the thread below is to check the setting “UsersPermissionToReadOtherUserEnabled” in your tenant settings and make sure it is activated. This can be done via PowerShell Reference by Tim Hölger https://learn.microsoft.com/answers/questions/551448/active-users-in-microsoft-teams-appear-as-unkown-u I hope this helps ;-), let me know if this is contrary to what you need, I would still be helpful to answer more of your questions. Best Regards, AnnaThomas Give back to the community. Help the next person with this problem by indicating whether this answer solved your problem. Click Yes or No at the bottom.

    Can this only be done via PowerShell? Is there not a setting in the GUI?

    Was this answer helpful?

    0 comments No comments
  4. EmilyS_726 17,720 Reputation points Volunteer Moderator
    2023-09-05T21:33:57+00:00

    Hello, this is Emily.

    For changes made to the Azure AD, some can take up to 24 hours to reflect. Just want to point that out in case that's the case, that 24 hours have not passed yet.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-09-05T20:12:10+00:00

    Hi Luis

    I'm AnnaThomas and I'd happily help you with your question. In this Forum, we are Microsoft consumers just like yourself.

    One possible solution that has worked for some users in the thread below is to check the setting “UsersPermissionToReadOtherUserEnabled” in your tenant settings and make sure it is activated. This can be done via PowerShell

    Reference by Tim Hölger https://learn.microsoft.com/answers/questions/551448/active-users-in-microsoft-teams-appear-as-unkown-u

    I hope this helps ;-), let me know if this is contrary to what you need, I would still be helpful to answer more of your questions.

    Best Regards,

    AnnaThomas

    Give back to the community. Help the next person with this problem by indicating whether this answer solved your problem. Click Yes or No at the bottom.

    Was this answer helpful?

    0 comments No comments