What you need to know
- Microsoft Teams will soon show users search results within context by navigating to the thread containing a queeried item.
- The new option could arrive as soon as October 2022, but that is not a firm date.
- The new feature is on the way to Teams for Windows and Mac.
Microsoft Teams currently handles searches for messages in a way that can be awkward. When you search for text, Teams takes you to a view of your messages and any directly connected thread, but it's completely out of context. Clicking on the search result doesn't take you to where the chat was sent within a channel or conversation. That's about to change, thanks to a change that's on the way to Teams.
"When users search for a chat message in Teams and click on a message result, they are taken to a view that contains only the selected message, rather than the entire chat thread," reads an entry on the Microsoft 365 roadmap (opens in new tab). "This fix will now land the users on the full chat thread once the message search result is clicked, thereby providing full context of the conversation around the message result."
The change should make it easier to see the context surrounding messages. While threads are a convenient way to organize conversations, there are times when you need to see the comment that sparked a thread to understand what's been said.
Microsoft Teams on Windows and Mac should see the change at some point in the future. The Microsoft 365 roadmap currently lists a release date of October 2022, but that's just a guideline and is subject to change.
Sean Endicott brings nearly a decade of experience covering Microsoft and Windows news to Windows Central. He joined our team in 2017 as an app reviewer and now heads up our day-to-day news coverage. If you have a news tip or an app to review, hit him up at firstname.lastname@example.org (opens in new tab).
Get the best of Windows Central in in your inbox, every day!
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.