MC752516: Meeting Chat shown by default in Gallery View with Teams Room

Announcement IDMC752516Published Date03-22-2024
ServicemicrosoftteamsLast Updated05-24-2024
CategoryStay informedExpiration Date07-01-2024
Roadmap ID332424Action Required by Date
TagsAdmin impact, Feature update, User impact


Summary
                Microsoft Teams will show Meeting Chat by default in Gallery View with Teams Room. This will enable users to see incoming chat messages on the front-of-room display during a meeting. The default chat experience can be configured via Teams Admin Center or XML setting. No action is needed to prepare for this change.


More Information

Meeting Chat is shown by default in Teams Room on Windows in Gallery view, making it easier to see incoming chat messages on the front-of-room display. IT admins can configure the default chat experience for a room, and users can make in-meeting changes to show or hide the chat using the touch console.

When this will happen:

GeneralAvailability (Worldwide, GCC, GCC High): We will begin rolling out late April 2024 (previously mid-April) and expected to complete by late May 2024 (previously mid-May).

How this will affect your organization:

This update enables users to have visibility of a meeting chat on the right panel in Gallery view during a meeting. In addition to the layout change, the chat icon button to show/hide the chat panel is moved from the view switcher to the uBar.

Chat panel in Gallery view

Chat panel in Gallery view


Chat button on uBar

Chat button on uBar

The default chat experience in Gallery view can be configured via Teams Admin Center or XML setting <OpenMeetingChatByDefault>. The default value is 'true.' Please note that the existing <ShowMeetingChat> setting hides the meeting chat completely from all in-meeting layouts as well as the chat button in-meeting. Therefore, <ShowMeetingChat> overrides <OpenMeetingChatByDefault>.

What you need to do to prepare:

There is no action needed to prepare for this change. You may want to notify your users about this change and update any relevant documentation as appropriate.

Previous Post Next Post