One-line summary
Similar updates
More like thisDetails
Body (from Message Center)
Updated December 3, 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 early March 2026 (previously late November 2025) and expect to complete by late March 2026 (previously late December 2025).
[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.
Raw JSON (for debugging)
Show/hide raw
{
"snapshot_item": {
"action_required_by": null,
"ai_action_required_by": "2026-03-01T00:00:00Z",
"ai_actions": [
"Review governance strategy for Loop workspaces",
"Consider impact on workspace creation workflows"
],
"ai_master_tags": [],
"ai_model": "gpt-4.1",
"ai_summary": "Admins can require new Loop workspaces to be managed by existing Microsoft 365 Groups, with rollout starting early March 2026 and completing by late March 2026.",
"ai_topics": [
"Microsoft 365 Apps",
"Loop",
"Microsoft 365 Groups",
"SharePoint"
],
"category": "planForChange",
"details_map": {
"Platforms": "Web",
"RoadmapIds": "422725",
"Summary": "Starting March 2026, admins can require new Microsoft Loop workspaces to be connected to existing Microsoft 365 Groups for management, similar to SharePoint Team sites. This may affect scenarios like automatic Teams meeting content aggregation. No preparation is needed; the feature will roll out automatically."
},
"id": "MC929022",
"importance": 4,
"is_major_change": false,
"last_modified": "2025-12-03T21:19:13Z",
"ms_products": [
"Microsoft 365 Apps"
],
"platforms": "Web",
"roadmap_ids": [
"422725"
],
"services": [
"Microsoft 365 apps"
],
"severity": "normal",
"tags": [
"Updated message",
"New feature",
"User impact"
],
"title": "(Updated) Microsoft Loop \u2013 Require Existing Microsoft 365 Group for New Loop workspaces"
}
}