Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces [MC929022]

Microsoft Loop – Require Existing Microsoft 365 Group for New Loop workspaces [MC929022]

Message ID: MC929022

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 January 2025 and expect to complete by late February 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.

Source: Microsoft

Show 1 Comment

1 Comment

  1. Mike Rosoft

    The upcoming update to Microsoft Loop, which requires new workspaces to be linked to existing Microsoft 365 Groups, is set to create a significant shift for both admins and users. For admins, this means a tighter grip on governance and management, akin to the familiar landscape of SharePoint Team sites. With this added layer of control, admins can ensure that all Loop workspaces adhere to organizational policies and standards, reducing the risk of rogue workspaces popping up like mushrooms after a rainstorm!

    For users, however, this change might feel like a double-edged sword. While the connection to existing Microsoft 365 Groups can streamline collaboration and project management, it may also complicate the creation of short-term or spontaneous workspaces. Imagine trying to whip up a quick workspace for a brainstorming session only to find yourself navigating through a maze of existing groups! It’s a bit like trying to find a parking spot at a busy mall during the holiday season—frustrating but ultimately rewarding when you finally settle on the right one.

    The impact of these changes will largely depend on how organizations adapt their adoption strategies. The ability to connect new workspaces to established groups should encourage better collaboration, but it’s essential for users to be trained on how to navigate this new requirement effectively.

    Overall, the rollout slated for late January 2025 promises to enhance organizational governance while presenting challenges for user flexibility. It’s a balancing act, and we’d love to hear your thoughts! How do you think this update will affect your workflow? Feel free to share your insights and experiences, and let’s get the conversation going! For deeper dives into similar topics, check out more posts at mwpro.co.uk.

Leave a Reply

Your email address will not be published. Required fields are marked *