Microsoft 365 app: Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces

🚨 The Signal: Admins can now enforce that new Microsoft Loop workspaces must link to an existing Microsoft 365 Group. This improves governance and data lifecycle management for collaborative content, reducing unmanaged sprawl.

The Impact

Admins gain control over Loop workspace creation, reducing unmanaged data sprawl and improving data governance.

• Security Teams: Reduced risk of unmanaged data exposure in new Loop workspaces.
• Admins: New policy option to enforce M365 Group linkage for Loop workspaces.
• End Users: May need to request or use existing M365 Groups for Loop collaboration.

The Action

1. Review existing Microsoft 365 Group creation and lifecycle policies.
2. Determine if new Loop workspaces should be restricted to existing M365 Groups.
3. Configure the optional IT admin policy for Microsoft Loop workspaces (specific path TBD upon GA, likely M365 Admin Center or PowerShell).
4. Communicate policy changes to end-users regarding Loop workspace creation.

Domain: M365-Apps · Impact: medium · Workload: M365 Apps