Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces

Plan for Change

Message ID

MC929022
View in Message Center

Roadmap ID

422725
View in M365 Roadmap

Services

Microsoft 365 apps

Affected Platforms

Web

Summary

Starting late November to December 2025, admins can require new Microsoft Loop workspaces to be connected to existing Microsoft 365 Groups for management, similar to SharePoint Team sites. This policy may affect scenarios like Teams meeting content aggregation and short-term projects. No preparation is needed.

Details

Updated August 13, 2025: We have updated the timeline. Thank you for your patience.

Admins will be able to ensure that new Loop workspaces are connected to and managed by an existing Microsoft 365 Group, similar to SharePoint Team sites.

This message is associated with Microsoft 365 Roadmap ID 422725

When this will happen:

General Availability (Worldwide): We will begin rolling out late November 2025 (previously late September) and expect to complete by late December 2025 (previously late October). 

How this will affect your organization:

Once Microsoft 365 Roadmap ID 422728 is available, end-users will have the ability to choose existing Microsoft 365 Groups for managing new Loop workspaces. This means that new Loop workspaces can optionally be connected to and managed by an existing Microsoft 365 Group, similar to how SharePoint Team sites are managed.

Additionally, Microsoft 365 Roadmap ID 422725 covers the capability to ensure that new Loop workspaces are connected to and managed by an existing Microsoft 365 Group, similar to SharePoint Team sites (it will not be an option for users to skip selecting an existing Microsoft 365 group if this policy is configured).

While this setting may align with existing governance processes, it's important for admins to note that scenarios like automatic aggregation of Teams meeting content into a Loop workspace, or the creation of small, short-term project workspaces, will be more challenging for end-users unless they can skillfully select an existing M365 group during creation. Please consider this tradeoff in your adoption strategy.

If your organization has governance tools for SharePoint Communication sites that work effectively in a reactive manner (i.e., governance is applied after the site is created), Microsoft recommends extending this process to include Loop workspaces rather than using this policy.

What you need to do to prepare:

There is nothing you need to do to prepare. This capability will roll to your tenant automatically.

Timeline

Published
Nov 8, 2024
Updated
Aug 13, 2025
End Date
Feb 9, 2026

Tags

Updated messageNew featureUser impact

Category

Plan for Change