User Not Appearing When Searching on Teams

Question

User Not Appearing When Searching on Teams

Habib Ullah Yusufzai 0

Hi ,

i have a user who is not visible in teams search,

the user account is enabled and have teams license

the user is not hidden from GAL

the user was able to be searched with out any troubles before but recently is not appearing in the search bar anymore,

its not my teams issue the user is not visible to the rest of the team too

the user however can continue conversation who they have started in the past but can't create new conversation

neither can someone new start a conversation with them

your help would be greatly appreciated

Ahmad Bataineh 0 Reputation points

2026-09-18T23:50:43.94+00:00
This issue points to an index sync delay, an information barrier block, or a stale directory cache on Microsoft's backend for that specific account.

Here are the step-by-step diagnostic and resolution actions to resolve this:

Check Active Directory / Entra ID Attributes 5 mins Verify that the user's MailNickname and UserPrincipalName (UPN) are not missing or corrupted in Microsoft Entra ID (Azure AD), as an empty MailNickname prevents the user object from being indexed by Teams search. Action: Run this PowerShell command to confirm: Get-MgUser -UserId "******@yourdomain.com" | Select-Object DisplayName, MailNickname, UserPrincipalName, AccountEnabled

Toggle GAL Visibility to Force Directory Sync Prerequisite for Index Sync Even though the user is currently not hidden from the Global Address List (GAL), toggling this setting forces Microsoft Exchange and Teams Substrate to re-index the object.

Open Exchange Online PowerShell and run:

Set-Mailbox -Identity "******@yourdomain.com" -HiddenFromAddressListsEnabled $true

Wait 10-15 minutes.
1. Re-enable visibility:

Set-Mailbox -Identity "******@yourdomain.com" -HiddenFromAddressListsEnabled $false

Inspect Information Barrier & Address Book Policies Admin Center Check Check if the user was recently assigned to a restricted Address Book Policy (ABP) or an Information Barrier (IB) policy that isolates them from other users.

Check Information Barriers in the Microsoft Purview Compliance Portal under Information barriers.

Verify Exchange Address Book Policy:

Get-Mailbox -Identity "******@yourdomain.com" | Select-Object AddressBookPolicy

Verify License Cycle 2 mins Unassign the Microsoft Teams license, wait 5 minutes, and reassign it. This re-triggers the provision workflow for Teams services (Chat, Calling, Search Substrate).

Test Direct Chat URL Workaround Immediate Workaround Have another user attempt to open a direct chat by pasting this link directly into a browser tab: https://teams.microsoft.com/l/chat/0/0?users=******@yourdomain.com Verification: If this opens a chat successfully, the user's account is functional and the issue is strictly isolated to the Teams Substrate Search Index, which usually resolves within 24â€“48 hours after toggling the GAL setting.

If the issue persists after 24 hours of toggling the GAL setting, run the Teams Search Diagnostic tool in the Microsoft 365 Admin Center (Help & Support -> Search for "Teams user search diagnostic"), or submit a ticket directly to Microsoft Support to request a manual Substrate Search re-index for the affected Object ID.

1 answer

Your answer

Answer 1

Hi @Habib Ullah Yusufzai,

Based on your description, since all users are unable to find this account in Teams search while existing conversations continue to work, one of the more likely possibilities is that the account has been excluded from the Teams directory due to Information Barriers, an Address Book Policy (ABP), or a service-side synchronization/indexing issue.

I would suggest checking the directory search scope and Information Barriers configuration:

In Microsoft Teams admin center, go to Teams > Teams settings > Search by name. Verify whether "Scope directory search using an Exchange address book policy" is enabled.

User's image

If it is enabled, review the Address Book Policy assigned to both the affected user and the users attempting to search for them.
In Microsoft Purview, check whether your organization is using Information Barriers, and whether the affected user was recently added to a new segment or policy.

User's image

Address Book Policies can restrict which users appear in Teams search results. Information Barriers can further prevent user lookup, discovery, and the creation of new conversations between certain groups of users.

You can also refer to the following official articles for a better understanding of these configurations:

If you have already reviewed these areas and everything appears correct, or if you need more effective troubleshooting, I would recommend opening a support request through Microsoft 365 Admin Center > Help & support.

User's image

At that point, the issue could be related to a backend synchronization or indexing problem, or another configuration that is not visible from the admin portals. A Microsoft support engineer can perform a deeper investigation, review backend settings, run any necessary synchronization processes, and, if required, escalate the case to a specialized engineering team for further analysis.

As this is a user-to-user community forum, I do not have access to Microsoft's internal diagnostic tools or backend resources, so my ability to investigate is limited. These are simply some thoughts based on similar cases I have seen, and I hope they help point you in the right direction or at least provide a path for further escalation if needed.

I hope this information is helpful. Thank you for taking the time to read my suggestions, and I wish you the best of luck in resolving the issue.

If the answer is helpful, please kindly click "Yes" button below. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Aetherin 1,730 Reputation points Independent Advisor

2026-09-18T23:48:40.2133333+00:00

Hi @Habib Ullah Yusufzai,

Have you had a chance to check the replies provided? Any update would be appreciated.