Microsoft Teams will soon default to landing on the last read message when selecting "Unread Chats." Users can choose to land on the newest message instead. Rollout begins in June 2025 and completes by July 2025. No admin action is required, but user notification is recommended.
Coming soon for Microsoft Teams: When users select Unread Chats, by default they will land on the last message they read in the chat. This rollout will allow users to quickly continue reading new messages and eliminates manual scrolling to find their last read message. Users will also be able to quickly jump to the newest message with a jump button. A new user-level setting will allow users to decide if they want to land on the last read message or continue landing on the newest message as they do before this rollout.
This message applies to Teams for Windows desktop, Teams for Mac desktop, and Teams for the web.
When this will happen:
Targeted Release: We will begin rolling out early June 2025 and expect to complete by mid-June 2025.
General Availability (Worldwide, GCC): We will begin rolling out mid-June 2025 and expect to complete by late June 2025.
General Availability (GCC High): We will begin rolling out early July 2025 and expect to complete by late July 2025.
General Availability (DoD): We will begin rolling out mid-July 2025 and expect to complete by late July 2025.
How this will affect your organization:
After this rollout, users will land by default on their last read message when they open Unread Chats. Users will get a button to jump to newest message:
The new user-level setting for users to choose if they want to land on the last read message or the newest message at Settings > Chats and channels > Chat > When I open a chat, take me to:
If the user chooses the non-default setting, users will land on the newest message after selecting Unread Chats. Users will see a button to jump to the last read message:
What you need to do to prepare:
This rollout will happen automatically by the specified dates with no admin action required before the rollout. You may want to notify your users about this change and update any relevant documentation.