Microsoft Teams: Auto-create Microsoft Loop workspaces to share meeting content
From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".
Schedule dates changed in the text
Date phrases in schedule sentences differ between the versions this installation saw- Seen 21 Jun 2024
early June 2024→ late June 2024
Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.
What the notice says
Microsoft’s text, safely structuredUpdated June 21, 2024: We have updated the rollout timeline below. Thank you for your patience.
Coming soon: Microsoft Teams meeting organizers of recurring meetings will be prompted in the chat to create a Microsoft Loop workspace after their meetings end. The Loop workspace helps gather shared meeting content into a central, durable Loop workspace to enable ongoing collaboration over time. As a recurring meeting series continues, additional content shared in the meeting chat will be added automatically to the initial Loop workspace.
When this will happen
Targeted Release: We will begin rolling out mid-May 2024 and expect to complete by mid-May 2024.
General Availability (Worldwide): We will begin rolling out mid-May 2024 and complete by late June 2024 (previously early June).
How this will affect your organization
After rollout, it will be easy for meeting organizers to create Loop workspaces for their meeting members and pull in shared content in the chat such as meeting recordings, Microsoft 365 content (Word, Excel, PowerPoint, Whiteboards, and so on), Loop meeting notes, Loop pages, and other shared content. We will support additional content types over time.
After the meeting ends, organizers will be shown a prompt to create a Loop workspace, will be able to review and confirm workspace members as well as the shared content. After confirmation, a Loop workspace will be created, invites will be sent to the meeting members, and the shared content will be linked in a Loop workspace. As the group shares more content in a meeting series Teams chat over weeks or months, the new content will be added automatically to the workspace. Workspace members can also add other content to the workspace and can reconfigure the order of content in the left navigation pane of the Loop app.
For this initial rollout, this feature will be enabled for meeting series with 3-50 invitees. Later, we will release support for greater than 50 invitees and for Modern Groups.
After a meeting, the meeting organizer can select the prompt in the meeting chat to create a Microsoft Loop workspace:
Naming and sharing the Loop workspace:
The meeting organizer can review a list of files shared in the meeting series and add the desired files to the workspace:
What you need to do to prepare
This rollout will happen automatically by the specified date 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.
We will update this comm before rollout with revised documentation.
What changed
Between archive captures, newest first- Tags
New feature, User impact→ Updated message, New feature, User impact
Updated June 21, 2024: We have updated the rollout timeline below. Thank you for your patience. Coming soon: Microsoft Teams meeting organizers of recurring meetings will be prompted … Availability (Worldwide): We will begin rolling out mid-May 2024 and complete by
earlylate June2024.2024 (previously early June). How this will affect your organization: After rollout, it will be easy …- Tags
- · first version seen
Learn more
Links from the notice and their documentation checksRelated public changes
No related announcements were found in the saved public history. Check the source for newer announcements.
Not confirmed here
What this page cannot tell you- Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.