Many of us are continuously working to create and maintain a Microsoft 365 environment where you have good order and control over your information. With so many people having started using Microsoft 365 Copilot and with many still working hard to prepare their environment to start using Microsoft 365 Copilot and perhaps even starting to see the great opportunities that proper use of well-built agents offers, Good Governance is a must.

Order in Microsoft Teams is one thing, Order in SharePoint is one thing, and Order in OneDrive is another, but honestly, how many people have good control over Loop Workspaces?

Many of us have torn our hair out in frustration over numerous Loop Workspaces that are created without any clear guidelines for how they should be used, nor any clear overview of where they are actually stored, from where they are accessible (and thus how and where to secure them and their content). Now, from the end of April 2026 onwards it will be possible to create order in this “Loop chaos” (which many have already managed to achieve) when a much-anticipated functionality regarding Loop Governance will become a reality. Admins will be able to ensure/enforce that new Loop workspaces are connected to- and managed by an existing Microsoft 365 Group.

With this, Users will be able to (or must) choose an existing group (Roadmap Item 422728). Admins can optionally enforce that all new Loop workspaces must be tied to an existing Microsoft 365 Group (Roadmap 422725).

In my opinion, Loop Workspaces belong as “ingredients” in contextual team channels in Microsoft Teams. Because it is important that information is stored, retrieved, and secured in its logical context. Therefore, I strongly recommend that admins enforce this setting, otherwise there will be no order whatsoever if this is allowed to remain optional.

The capability is rolled out automatically. When/If admins enable enforcement, users will not be allowed to skip selecting an existing Microsoft 365 Group during Loop workspace creation. This will align Loop governance with existing lifecycle management for SharePoint Team sites and ensure more consistent ownership, security, and access control across workspace types.

Who the change affects

• End users who create Loop workspaces
• Admins responsible for governance of Teams, SharePoint, and Microsoft 365 Groups
• Teams users using automatic meeting-content aggregation into Loop workspaces, as this workflow depends on selecting the correct existing group

Which admin roles may need to configure or change settings

• Global Admin
• SharePoint Admin
• Teams Admin
  These roles may choose whether to enforce the “must use existing M365 Group” requirement as part of the organization’s governance strategy.

Increased efficiency and reduced costs

By linking Loop workspaces to existing Microsoft 365 Groups, organizations can:

• Reuse existing access models instead of creating new ones
• Reduce accidental over‑provisioning of sites and workspaces
• Lower administrative time spent cleaning up or correcting workspace settings
• Improve user productivity by keeping projects aligned with established governance structures

This can translate into reduced operational overhead and more predictable workspace lifecycle management.

Great Positive impact from a governance perspective

• Loop becomes aligned with the established governance model used for SharePoint Team sites
• Centralized control of ownership, retention, naming, sensitivity labels, and lifecycle
• Reduced fragmentation of workspaces and fewer “orphaned” collaboration spaces
• Easier to apply organization‑wide policies consistently

Potential security impacts

Positive security impact:

• Access control inherits from an existing Microsoft 365 Group, reducing misconfigurations
• More consistent visibility and ownership models across SharePoint/Teams/Loop
• Lower risk of unintentionally unrestricted Loop workspaces

Potential negative security impact:

• Users creating a workspace might choose an inappropriate group with wider access, potentially exposing content unintentionally
• Automated meeting-content aggregation into Loop may become more error‑prone if users select the wrong group

From a holistic perspective, we achieve major security benefits and unified governance. The minor potential negative consequences are relatively negligible and can be avoided through clear information to end users.

With this knowledge, I know what I will be looking forward to and doing at the end of April 2026. 😊