Microsoft Teams: Add a Loop workspace tab to standard channels [MC973493]

Coming soon to Microsoft Teams: Add a Loop workspace tab to standard channels enabling your team to brainstorm, co-create, collect, and organize content—together in real time. Everyone in the Team will have access to the Loop workspace, even as Team membership changes, and the workspace will adhere to the governance, lifecycle, and compliance standards set by the Microsoft 365 group backing the team. This message applies to Teams on Windows desktop, Teams on Mac desktop, and Teams on the web.

This message is associated with Microsoft 365 Roadmap ID 472022.

[When this will happen:]

Targeted Release: We will begin rolling out late January 2025 and expect to complete in late January 2025.

General Availability (Worldwide): We will begin rolling out February 2025 and expect to complete in late February 2025.

[How this will affect your organization:]

After this rollout, all users with the Loop app enabled on Teams will receive this experience by default.

To get started, users can select the plus sign (+) at the top of the Teams channel and select Loop from the list.

With this rollout, we will support these features:

• Creating a new workspace for a standard Teams channel where the workspace membership is the Channel group membership.
• Adding pages, files, and links to the workspace, collaborating with others, and sharing pages as components in Teams chats and channels. Users will be able to complete all their Loop workspace workflows in Teams.
• Recreating the Loop workspace tab in the channel, in case someone removes it by mistake.
• Deleting the Team will delete the attached Loop workspace. The workspace will be restored if the Microsoft 365 group is restored.
• If the user adding the Loop app to a channel does not have the appropriate license or permission to create a workspace, the user will be blocked from adding the app.
• The Loop workspace created in a Teams channel will automatically receive the sensitivity label of the Microsoft 365 group at creation time. With this rollout, when the label of a Microsoft 365 group changes after workspace creation, the label will not be automatically propagated to the workspace’s Microsoft SharePoint Embedded (SPE) container. Admins can update labels for these workspaces in the SharePoint admin center.
  • Coming soon in late February: When the label of the Microsoft 365 group changes, that update will automatically propagate to the SPE container for the workspace within 24 hours. We will update this message when this feature is available.

[What you need to do to prepare:]

This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.

If you want to block the Loop app in Teams, this will remove the Loop tab applications in channels and the Loop personal app in Teams. To learn more: Overview of Loop workspaces storage and permissions | Microsoft Learn

If you want to keep the Loop application in Teams but disable to ability for users to create Loop workspaces, follow these instructions:

1. Sign in to the Microsoft 365 Apps admin center at https://config.office.com/ with your Microsoft 365 admin credentials.
2. Select Customization from the left pane.
3. Select Policy management.
   
4. Create a new policy configuration or edit an existing one.
5. From the Choose the scope dropdown menu, choose either All users or select the group for which you want to apply the policy. Learn more: Microsoft 365 Groups for Cloud Policy in Manage Loop components in your organization | Microsoft Learn.
6. In Configure settings, choose your desired setting for Create Loop workspaces in Loop:
   • Disabled: Users cannot create Loop workspaces in Teams. (When disabled, the Loop app will open Loop components in Teams.)
   • Enabled or not configured: Users can create Loop workspaces in Teams.
   • Not configured = Enabled
7. Save the policy configuration.
8. Reassign priority for any security group, if required. (If two or more policy configurations are applicable to the same set of users, the one with the higher priority is applied.)

Learn more

• Overview of Loop workspaces storage and permissions | Microsoft Learn
• Related message center post: MC929022 Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces (published November 2024)