The feature is limited to the Teams desktop and Mac clients in Microsoft’s Worldwide standard multi-tenant cloud, according to the roadmap. It is aimed at a familiar problem in high-volume Teams deployments: unread-only mode is useful for triage, but it previously made it awkward to check a conversation that had already been read without abandoning the focused view.
The eye icon replaces a more disruptive detour
When a user applies the unread-only filter to a chat or channel section, hovering over that section’s name should reveal an eye icon. Selecting it opens a list of read chats or channels associated with that section; choosing an item opens it while the surrounding list remains filtered to unread content.
The practical distinction is that a read thread becomes available as a temporary reference point rather than a reason to reset the user’s working view. A user can check an earlier reply, confirm a decision in a channel, or retrieve context from a read chat, then return directly to the remaining unread queue.
Modern Workspace Pro, which archives Microsoft 365 Message Center posts, reports that the eye control replaces a prior “see read” button in the chat list. That is a modest interface change, but it removes a control that was separate from the section header and makes the escape hatch available where users are already scanning their chat and channel groups.
A launched roadmap item does not mean a new tenant switch
There is no Teams admin policy, PowerShell setting, or tenant-side configuration attached to this update. Microsoft’s Message Center guidance, as reproduced by Modern Workspace Pro, says the feature is enabled by default and requires no administrative preparation.
For IT teams, that means this is a change-management issue rather than a deployment project. Help desk staff should know that the eye icon appears only after a user has placed the relevant chat or channel section in unread-only mode. Users looking at an ordinary all-conversations list will not see the control simply because the feature has shipped.
The feature also should not be confused with Teams’ broader chat-and-channels redesign. Microsoft introduced unread filtering as part of that evolving experience, alongside filters for chats, channels, meetings, and muted conversations. Roadmap item 559608 does not create a new unread filter; it changes how users can momentarily reach read content while that existing filter is active.
That difference matters in organizations where Teams training materials describe unread-only mode as an all-or-nothing view. Those instructions are now incomplete for the affected desktop clients. A user no longer needs to switch back to an all-items view simply to inspect a conversation that has dropped out of the unread list.
The rollout dates tell a more useful story than the May label
Microsoft’s roadmap entry gives May 2026 as the general-availability date, while the Message Center notice associated with the feature, MC1274550, said rollout would begin in early May and complete in early July. Modern Workspace Pro reported on June 23 that Microsoft had revised the completion estimate from mid-May to early July.
That means “GA: May” should be read as the start of availability, not proof that every eligible desktop and Mac client received the UI at that point. The September 2 roadmap update changed the entry’s status to Launched, providing Microsoft’s later confirmation that the release is no longer in its rollout phase.
Microsoft has not published a minimum Teams client version for the eye icon in the roadmap item or the available Message Center text. Administrators troubleshooting a report that the option is absent should therefore start with the basic checks: confirm the employee is using Teams on Windows or macOS, ensure the chat or channel section is actually in unread-only mode, and have the user update or restart the Teams client before treating the behavior as a tenant configuration problem.
What Microsoft did not promise
The roadmap specifically names Desktop and Mac. It does not list Teams on the web, iOS, Android, government cloud environments, or on-premises variants. Administrators should not tell users that the icon is available everywhere based on this announcement alone.
Microsoft also did not identify license prerequisites, controls to disable the feature, telemetry, audit implications, or compliance changes. That absence is unsurprising for a client-side navigation refinement, but it is still useful operationally: the update changes what users can see in a filtered list, not what chats or channels they are authorized to access. Opening an item from the read list remains subject to the user’s existing Teams permissions.
For organizations with tightly scripted support procedures, the only documentation update needed is straightforward: in an unread-only chat or channel section, hover over the section name and select the eye icon to access read items without clearing the filter. The feature’s value is not a new collaboration capability; it is a quicker route through a view that users already rely on to keep Teams from becoming an endless unread backlog.