| Announcement ID | MC775345 | Published Date | 04-11-2024 | |
| Service | microsoftteams | Last Updated | 04-11-2024 | |
| Category | Stay informed | Expiration Date | 12-20-2024 | |
| Roadmap ID | 109573 | Action Required by Date | ||
| Tags | New feature, User impact | |||
| Summary |
|---|
| In Microsoft Teams, presenters can enable annotations during screen sharing, allowing all participants to collaborate live. Meeting content with annotations can be saved as a Microsoft Whiteboard, accessible for continued collaboration post-meeting. Rollout begins late May 2024, with no admin action required. |
| More Information |
|---|
In Microsoft Teams, collaborative annotations enable meeting participants with the presenter role to enable annotations after sharing their screen. This allows everyone in the meeting to draw, add a note, react, highlight text, and more to share their thoughts right on the content, live with everyone else. Participants sharing their screen will have the ability to save content with collaborative annotations as a Microsoft Whiteboard, enabling all meeting participants to revisit this content and continue collaborating after the meeting. When this will happen:General Availability (Worldwide, GCC, GCC High, DoD): We will begin rolling out in late May 2024 and expect to complete by late June 2024. How this will affect your organization:Saving meeting content with collaborative annotations as a Whiteboard is available on desktop (Microsoft Windows and Mac). When users who share their screen in Teams meetings and select Start annotation in the presenter toolbar, they will see a new Save button in the Whiteboard toolbar that will allow users to capture all annotations from the meeting in one Whiteboard file. Capture your annotations and view them in the Whiteboard: View all your saved snapshots from the meeting in a Whiteboard: 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 as appropriate. |
