M365 Changelog: (Updated) Microsoft Teams: Meeting recap and meeting artifacts automatically shared in chat after meeting

Summary

Microsoft Teams will automatically share a recap message in the meeting chat after a meeting, including links to the meeting recap page and meeting artifacts such as the transcript, recording, files shared, and meeting notes. The rollout begins in early April 2024 and is expected to complete by mid-June 2024, with no action needed to prepare for the change. Users with access to intelligent recap will also receive meeting insights such as the list of speakers, name mentions of users in the meeting, and suggested tasks.

MC718761 – Updated May 31, 2024: Microsoft has updated the rollout timeline below for GCC organizations. Thank you for your patience.

In Microsoft Teams, Microsoft is rolling out a new recap message in the meeting chat. 

This message is associated with Microsoft 365 Roadmap ID 381121.

When this will happen:

Targeted Release: Microsoft will begin rolling out early April 2024 and expects to complete by early April 2024.

Worldwide: Microsoft will begin rolling out early April 2024 and expects to complete by late April 2024.

GCC: Microsoft will begin rolling out early May 2024 and expects to complete by mid-June 2024 (previously mid-May).

How this will affect your organization:

Shortly after a meeting ends, a recap message will appear in the meeting chat with links to the meeting recap page and meeting artifacts such as the transcript, the recording, any files shared in the meeting, and the meeting Collaborative notes and Whiteboard (if used).

For users with access to intelligent recap, the recap message also will include meeting insights such as the list of speakers, name mentions of users in the meeting, and suggested tasks.

Teams users: 

user controls
View image in new tab

Teams users with access to intelligent recap: 

user controls
View image in new tab

What you need to do to prepare:

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