Microsoft Loop – Microsoft 365 Groups for Managing New Loop workspaces
Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.Rollout
- Roadmap
- 422728
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 22 Aug 2025 April 2025
- Seen 8 Jul 2025
late June 2025, late July 2025→ late September 2025, late October 2025 - Seen 3 Apr 2025
late March 2025, late April 2025→ late June 2025, late July 2025 - Seen 7 Mar 2025
late February 2025→ late April 2025 - Seen 24 Jan 2025
late January 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 removedWhat changed
Between archive captures, newest firstUpdated
July 8,August 22, 2025:We have updatedThe ability to create shared Loop workspaces that are managed by Microsoft 365 Groups launched in April 2025 with Roadmap ID 472022. As a result, thetimeline below. Thank youwork described below was canceled. For your reference, the ability foryour patience.IT admins to enforce that an existing Microsoft 365 Group be used to govern all new Loop workspaces is still tracked by Roadmap ID 422725. Work below has been canceled. See above. --- When creating a new Loop workspace, users will be able to choose …… manage the workspace's lifetime, governance, and compliance, similar to SharePoint Team sites.
This message is associated with Microsoft 365 Roadmap ID 422728When this will happen: General Availability (Worldwide): We will begin rolling out …Updated
April 3,July 8, 2025: We have updated therollouttimeline below. Thank you for your patience. When creating a new Loop … this will happen: General Availability (Worldwide): We will begin rolling out lateJuneSeptember 2025 (previously lateMarch)June) and expect to complete by lateJulyOctober 2025 (previously lateApril).July). How this will affect your organization: Once available, when creating a new …Updated
March 7,April 3, 2025: We have updated the rollout timeline below. Thank you for your … this will happen: General Availability (Worldwide): We will begin rolling out lateMarchJune 2025 (previously lateFebruary)March) and expect to complete by lateAprilJuly 2025 (previously lateMarch).April). How this will affect your organization: Once available, when creating a new …- Tags
New feature, User impact→ Updated message, New feature, User impact
Updated
January 24,March 7, 2025: We have updated thecontent.rollout timeline below. Thank you for your patience. When creating a new Loop workspace, users … this will happen: General Availability (Worldwide): We will begin rolling out lateFebruaryMarch 2025 (previously lateJanuary)February) and expect to complete by lateMarchApril 2025 (previously lateFebruary).March). How this will affect your organization: Once available, when creating a new …- Tags
Updated January 24, 2025: We have updated the content. Thank you for your patience. When creating a new Loop workspace, users will be able to choose … this will happen: General Availability (Worldwide): We will begin rolling out late
JanuaryFebruary 2025 (previously late January) and expect to complete by lateFebruary 2025.March 2025 (previously late February). How this will affect your organization: Once available, when creating a new …- · first version seen
Linked documentation
Microsoft pages the notice links toThe notice links to no Microsoft Learn or Support page that this installation reads.
Related public evidence
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.