Skip to main content
๐Ÿฆ‰
Message CenterMicrosoft 365 Updates
HomePermissionsTenant FinderPortfolio
๐Ÿฆ‰
M365 Message Centerby Cengiz YILMAZ

Track the latest updates, features, and announcements for Microsoft 365 services. Comprehensive archive of service updates and important changes.

Quick Links

HomePermissionsTenant FinderPortfolio

Connect

ยฉ 2026 M365 Message Center. Created with โค by Cengiz YILMAZ

Data sourced from Microsoft 365 Message Center โ€ข Not affiliated with Microsoft

  1. Home
  2. /
  3. MC929022

Microsoft Loop โ€“ Require Existing Microsoft 365 Group for New Loop workspaces

Plan for Change

Message ID

MC929022
View in Admin Center

Roadmap ID

422725
View in Roadmap

Services

Microsoft 365 apps

Affected Platforms

Web

Summary

Starting April 2026, new Microsoft Loop workspaces must be connected to existing Microsoft 365 Groups if the policy is enabled, ensuring governance similar to SharePoint Team sites. This may complicate some scenarios, so admins should consider adoption impacts. No preparation is needed; rollout is automatic.

Details

Updated March 16, 2026: 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 early April 2026 (previously early March) and expect to complete by late April 2026 (previously late March).ย 

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
Message published to Message Center
Updated
Mar 16, 2026
Message content updated
End Date
Jun 1, 2026
Message timeline ends

Tags

#Updated message#New feature#User impact

Category

Plan for Change

Related Messages

Similar updates

MC929014

Microsoft Loop โ€“ Departed User Content Workflows for User-Owned Loop workspaces

Nov 8, 2024
MC929025โ—

Microsoft Loop โ€“ Multi-Geo Support for Shared Loop workspaces

Nov 8, 2024
MC915492

New Microsoft Outlook for Windows: Add Microsoft accounts with non-Microsoft email addresses

Oct 21, 2024
MC929028

Microsoft 365 app: Microsoft Loop รขโ‚ฌโ€œ New personal Loop workspace

Nov 8, 2024
MC923176

Microsoft Loop: Sensitivity labels at the container level

Nov 1, 2024