One-line summary
Similar updates
More like thisDetails
Body (from Message Center)
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 422725 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": [],
"ai_master_tags": [
"User",
"Admin"
],
"ai_model": "gpt-4.1",
"ai_summary": "Admins can require new Loop workspaces to be linked to an existing Microsoft 365 Group, aligning with SharePoint Team site governance, starting rollout in early April 2026.",
"ai_topics": [
"Microsoft 365 Apps",
"Loop",
"Microsoft 365 Groups",
"SharePoint"
],
"category": "planForChange",
"details_map": {
"Platforms": "Web",
"RoadmapIds": "422725",
"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."
},
"id": "MC929022",
"importance": 5,
"is_major_change": false,
"last_modified": "2026-03-26T16:36:11Z",
"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"
}
}