User not available in Teams Search

Question

User not available in Teams Search

Damian Lisak 0

Hey,

I have problem with Teams user - hybrid AD + E5 license.

After I changed Last Name, user is not available in Teams Search.

I tried to rewrite all user details, like Name, Lasn Name, mail, Userproxy, etc.

I tried sync again, I checked different option (from tutorials), nothing helped. Problem has a few days.

If I start new conversation, it's working, but not if I search. The same when other users try to Search this user.

0 comments

2 answers

Your answer

Answer 1

Steven-N 25,315 Microsoft External Staff Moderator

Hi Damian Lisak

Thank you for reaching out to Microsoft Q&A forum

From my research, the root cause of this behavior is that Teams Search relies on the Exchange Online Address Book index, and changing the Last Name in hybrid AD sometimes fails to trigger a re-index.

That said, you need to force it by following below approach:

On your On-Premises AD server:

# 1. Hide the user from the Address Book
Set-ADUser -Identity "username" -Replace @{msExchHideFromAddressLists=$true}
# 2. Sync to Azure AD
Start-ADSyncSyncCycle -PolicyType Delta
# 3. WAIT 1-2 HOURS for Exchange Online to fully process the removal
# 4. Unhide the user
Set-ADUser -Identity "username" -Replace @{msExchHideFromAddressLists=$false}
# 5. Sync again
Start-ADSyncSyncCycle -PolicyType Delta

Then have the users who are searching for this person clear their local Teams cache (Close Teams --> Win+R --> %localappdata%\packages\msteams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams --> delete contents --> reopen Teams).

Hope my answer will help you and kindly let me know if the problem still persists.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

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

Steven-N 25,315 Reputation points Microsoft External Staff Moderator

2026-03-25T07:40:36.4166667+00:00

Hi Damian Lisak

It has been a while and I am writing to see how things are going with this issue.

Have you had a chance to check the replies provided?

Any update would be appreciated.
Damian Lisak 0 Reputation points

2026-03-25T14:02:10.4766667+00:00

Hey,

Unfortunately, it didn't help. Do you have any other idea? :/

Sorry for delay with update, I needed some time to check it.
Steven-N 25,315 Reputation points Microsoft External Staff Moderator

2026-03-26T07:00:40.1633333+00:00
Hi Damian Lisak

Thank you for the update and your patience!

Since the previous steps to force an Address Book sync didn't clear the issue, it’s likely that the user profile is either "stuck" in the Microsoft 365 Substrate indexing or there's a stubborn client-side caching issue we haven't bypassed.

Please try the following steps to thoroughly isolate and force a backend re-index:

Step 1: Isolate Client vs. Backend (The Web App Test)

Before we make any more backend changes, please have one of the affected users open an InPrivate/Incognito browsing window and log into the Teams Web App

If the user IS searchable in the Web App: The issue is 100% a local caching problem on the desktop clients. In modern Teams, you may need to reset the app entirely (Settings > Apps > Installed apps > Microsoft Teams > Advanced options > Reset) or completely reinstall it.

If the user is NOT searchable in the Web App: This confirms the issue is still on the backend/indexing. Proceed to Step 2.

Step 2: Force an Offline Address Book (OAB) Generation

Even if Azure AD is updated, Exchange Online's Offline Address Book might be lagging, which Teams relies on.

Connect to Exchange Online PowerShell: Connect-ExchangeOnline

Run the following command to force the OAB to update: Get-OfflineAddressBook | Update-OfflineAddressBook (Note: It can still take up to 24 hours for the new OAB to fully generate and propagate to all services, but this manually triggers the job).

Step 3: The License Toggle (Re-provisioning)

This is often the most definitive fix for a "stuck" profile in Teams. Removing and re-assigning the Teams license forces the backend services to completely re-provision the user and re-add them to the Teams directory.

Go to the Microsoft 365 Admin Center > Users > Active users.

Select the affected user and go to the Licenses and apps tab.

Uncheck/remove the Microsoft Teams license (or the entire E5 license if easier, though removing just Teams is safer).

Click Save changes.

Wait 15-30 minutes to ensure the backend processes the removal.

Go back and reassign the Teams/E5 license, then save changes again.

Wait another 1-2 hours and test the search functionality again.

Step 4: Check Scoped Directory Search

If you have Scoped Directory Search enabled in your environment, verify the user's routing or address book policies.

Go to the Teams Admin Center > Teams settings.

Under Search by name, check if "Scope directory search using an Exchange address book policy" is turned on. If it is, verify that the user was not accidentally dropped from their Address Book Policy during the Last Name change.

Please give the License Toggle (Step 3) a try in particular, and let me know the results of the Web App test (Step 1).
Damian Lisak 0 Reputation points

2026-03-26T09:25:59.46+00:00
Hey,

Thank you for quick response.

It didn't work before and after previous steps - can't find user via Web App.

Command (cmdlet) Udpdate(...) doesnt't work (cmdlet not recognized).

I removed the Teams license (removing E5 license is too aggressive :) ) and now I'm waiting ~30min. I will let you know after all.

Scope (...) is turned off as default. Should I turn it on? (after step 3. finish, if that doesn't help).
Steven-N 25,315 Reputation points Microsoft External Staff Moderator

2026-03-26T11:00:09.9333333+00:00

Hi Damian Lisak

Given the complexity of the require, I’d like to take some time to review the details thoroughly and conduct further testing to ensure I can offer you the most effective solution.

I’ll follow up with you as soon as I have an update. I truly appreciate your patience and apologize for the delay.

Best regards,
Damian Lisak 0 Reputation points

2026-03-26T13:33:02.8766667+00:00

Hey @Steven-N ,

It didn't help.

So, steps 1, 2 and 3 didn't help. I can't do a step 4 (it's disabled as default), because we have few tenants and I don't want to do 'global' while the problem is only with 1 user :)
Any other ideas?
Steven-N 25,315 Reputation points Microsoft External Staff Moderator

2026-03-27T10:23:48.4433333+00:00
Hi Damian Lisak

Since the standard attribute toggles and license re-provisioning didn't trigger a re-index for this specific user, here are the remaining advanced steps to force a Substrate update, along with the final escalation path:

Sometimes, changing a completely unrelated, indexed attribute forces the Exchange Online Substrate to reconstruct the user's profile card from scratch, which Teams uses for its internal search.

On your On-Premises AD server, add a temporary, fake SMTP address to the user's proxyAddresses attribute (e.g., smtp:******@yourdomain.com). Alternatively, change the Department or Job Title to a dummy value.

Run a Delta Sync: Start-ADSyncSyncCycle -PolicyType Delta.

Wait 1-2 hours for Exchange Online and Teams to process the change. Check if the user becomes searchable in the Web App.

If it works, revert the change (remove the dummy alias/title) and sync again.

If the issue still persists, I highly recommend you reach out directly to Microsoft Support team via Service Hub

to escalate this and get the definitive supportation.

Thank you for your understanding

Best regards
Damian Lisak 0 Reputation points

2026-03-31T12:59:16.58+00:00

Hey @Steven-N

Still nothing. I will follow your suggestion.

Thank you for your help and trying :)
Steven-N 25,315 Reputation points Microsoft External Staff Moderator

2026-04-01T08:02:35.94+00:00

Hi Damian Lisak

You can follow my suggestion as a workaround of this concern, maybe that is not the definitive solution but as I am forum moderator, I cannot suggest you further.

Thank you for your understanding and wish your problem will be solved soon

Regards

Answer 2

Damian Lisak 0

Hey,

I checked step 3 and didn't help :/ Step 4. didn't check, it looks a little risky with 1 user case :p We have a few tenants and I don't have permission to do changes like this.

Any other ideas how to solve problem?

0 comments