Forum Discussion
New teams: call queues not showing in search
- Feb 26, 2026
Update form Microsoft Internal:
Issue Summary:
Customer is unable find auto attendants or call queues in Teams client.
Root Cause:
Root Cause 1 - PG is migrating the API used by PowerBar search from SearchV2 to Substrate service, this change has a consequence that AA and CQ will not be returned in the Teams PowerBar when searched by display name.
Root Cause 2 -. If the end user is search in the Calls App and has only entered 5 or less characters.Investigation Guidance:
This is by design and part of a product design change that occurred recently.
For root cause 1 - please educate the user to one of the following options:
- Search in the power bar by the resource account UPN of the AA or CQ;
- Or search by resources account display name in the Calls APP.
For root cause 2 - Please educate the end user to search for voice apps by entering at least 6 characters of the resources account display name.
Strange that it is fixed for Tom and I but not for you.
My 365 tenant's users are all on E5 licenses fwiw.
- RobKobMay 31, 2024Copper ContributorWe ended up licensing all of our auto attendants and call queues, this way we could hide the CQs from the GAL and because the auto attendants were licensed they'd show up in the GAL. We're education so we had CALs to spare, but this sure isn't a solution for all.
- Tom_MuirheadMay 31, 2024Copper Contributor
This seemed to stop working again today. Switching to Classic works and a work around for our concierge position (and it worked for me) is to save the resource that goes into the queue you need as a speed dial and then switch back to NEW Teams. The resources still won't show up but the speed dial will get you there.