ChangeIntelIT change radar
Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 11:37 UTC Customize Public modeDiscuss ChangeIntel on Discord
MC929022 Plan for changeUpdated messageNew featureUser impact

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

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.
Microsoft 365 apps
Microsoft 365 admin center

Rollout

Roadmap
422725

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 21 Apr 2026 early April 2026 → early May 2026
  • Seen 16 Mar 2026 early March 2026, late March 2026 → early April 2026, late April 2026
  • Seen 3 Dec 2025 early September 2026, late September 2026 → early March 2026, late March 2026
  • Seen 3 Dec 2025 late November 2025, late December 2025 → early September 2026, late September 2026
  • Seen 13 Aug 2025 late September 2025 → late November 2025, late December 2025
  • Seen 22 May 2025 late June 2025 → late September 2025
  • Seen 2 Apr 2025 late March 2025 → late June 2025
  • Seen 6 Feb 2025 late January 2025, late February 2025 → late March 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated May 11, 2026: We have updated the content. Thank you for your patience. IntroductionA 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.

What changed

Between archive captures, newest first

  1. Updated April 21,May 11, 2026: We have updated the timeline and content. Thank you for your patience. IntroductionA new organization-level Cloud Policy setting  … early May 2026 (previously late April).  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 notsites. Workspace creation must be an option for users to skip selecting an existing Microsoft 365 group if this policy is configured).initiated from the Loop app within standard Teams channels. While this setting may align with existing governance processes, it's important for …

  2. Updated March 16,April 21, 2026: We have updated the timeline.timeline and content. Thank you for your patience. IntroductionA 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 … When this will happen: General Availability (Worldwide): We will begin rolling out earlylate April 2026 (previously early March)April) and expect to complete by late Aprilearly May 2026 (previously late March).April).  How this will affect your organization: Once Microsoft 365 Roadmap ID 422725 …

  3. … March).  How this will affect your organization: Once Microsoft 365 Roadmap ID 422728 422725 is available, end-users will have the ability to choose existing Microsoft 365 …

  4. Updated December 3, 2025:March 16, 2026: We have updated the timeline. Thank you for your patience. Admins will … this will happen: General Availability (Worldwide): We will begin rolling out early MarchApril 2026 (previously late November 2025) early March) and expect to complete by late MarchApril 2026 (previously late December 2025).March).  How this will affect your organization: Once Microsoft 365 Roadmap ID 422728 …

  5. Updated December 2,3, 2025: We have updated the timeline. Thank you for your patience. Admins … this will happen: General Availability (Worldwide): We will begin rolling out early SeptemberMarch 2026 (previously late November 2025) and expect to complete by late SeptemberMarch 2026 (previously late December 2025).  How this will affect your organization: Once …

  6. Updated August 13,December 2, 2025: We have updated the timeline. Thank you for your patience. Admins … When this will happen: General Availability (Worldwide): We will begin rolling out late November 2025early September 2026 (previously late September)November 2025) and expect to complete by late December 2025September 2026 (previously late October).December 2025).  How this will affect your organization: Once Microsoft 365 Roadmap ID 422728 …

  7. Updated May 22,August 13, 2025: We have updated the rollout timeline below. timeline. Thank you for your patience. Admins will be able to ensure that … this will happen: General Availability (Worldwide): We will begin rolling out late SeptemberNovember 2025 (previously late June)September) and expect to complete by late OctoberDecember 2025 (previously late July).October).  How this will affect your organization: Once Microsoft 365 Roadmap ID 422728 …

  8. Updated April 2,May 22, 2025: We have updated the rollout timeline below. Thank you for your … this will happen: General Availability (Worldwide): We will begin rolling out late JuneSeptember 2025 (previously late March)June) and expect to complete by late JulyOctober (previously late April).July).  How this will affect your organization: Once Microsoft 365 Roadmap ID 422728 …

  9. Updated February 6,April 2, 2025: We have updated the rollout timeline below. Thank you for your … this will happen: General Availability (Worldwide): We will begin rolling out late MarchJune 2025 (previously late January)March) and expect to complete by late AprilJuly (previously late February).April).  How this will affect your organization: Once Microsoft 365 Roadmap ID 422728 …

    • Tags New feature, User impact → Updated message, New feature, User impact

    Updated February 6, 2025: We have updated the rollout timeline below. Thank you for your patience. Admins will be able to ensure that new Loop workspaces are connected … this will happen: General Availability (Worldwide): We will begin rolling out late JanuaryMarch 2025 (previously late January) and expect to complete by late February 2025. April (previously late February).  How this will affect your organization: Once Microsoft 365 Roadmap ID 422728 …

  11. · first version seen

Linked documentation

Microsoft pages the notice links to

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 11:37 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.