One-line summary
Similar updates
More like thisDetails
Body (from Message Center)
Updated May 11, 2026: We have updated the content. Thank you for your patience.
[Introduction]
A new organization-level Cloud Policy setting (OCPS) is available, allowing admins to block creation of tenant-owned Loop workspaces. When this setting is on, the "New workspace" ability in the Loop app will be unavailable. The only valid option for creating workspaces will be through standard channels in Teams, as these are connected to and managed by existing Microsoft 365 Groups. For more information about creating workspaces in Teams standard channels, visit Loop Workspaces in Teams Channels - Microsoft Support.
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 April 2026 (previously early April) and expect to complete by early May 2026 (previously late April).
[How this will affect your organization:]
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. Workspace creation must be initiated from the Loop app within standard Teams channels.
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 need to block Loop workspace creation",
"Update governance strategy for Loop workspaces if needed"
],
"ai_master_tags": [
"Admin"
],
"ai_model": "gpt-4.1",
"ai_summary": "A new policy lets admins block tenant-owned Loop workspace creation, limiting new workspaces to Teams standard channels managed by Microsoft 365 Groups.",
"ai_topics": [
"Microsoft 365 Apps",
"Loop",
"Teams",
"Microsoft 365 Groups"
],
"category": "planForChange",
"details_map": {
"Platforms": "Web",
"RoadmapIds": "422725",
"Summary": "A new Microsoft 365 Cloud Policy will block tenant-owned Loop workspace creation, requiring workspaces to be created only through existing Microsoft 365 Groups in Teams channels. This rollout begins late April 2026, aiming to align workspace management with existing governance but may limit some user scenarios."
},
"id": "MC929022",
"importance": 5,
"is_major_change": false,
"last_modified": "2026-05-11T16:27:32Z",
"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"
}
}