Loop Workspaces will become a core Microsoft 365 service. The Microsoft Loop service plan requirement will be removed, extending access to more licenses. Admins should review their Office Cloud Policy.
Loop on the web still ignores regional language formats and falls back to English (en-US), even when a specific language is configured for users. This long-standing, frustrating limitation continues to affect users in regions where regional variants are used.
Microsoft has canceled the planned licensing enforcement for Loop Workspaces indefinitely. Users can continue to create and manage Loop Workspaces without an assigned Loop service plan, unless an admin policy restricts them.
Microsoft is retiring several Planner features by February 2026 while introducing new capabilities, including replacing the old user comments, new templates, and expanding the Project Manager Agent availability.
Microsoft is rolling out Loop Pages in Teams channels, supported in Standard, Private, and Shared channels. Stored in the channel’s SharePoint folder, these pages simplify collaboration and are accessible across Teams, Loop web, and Loop mobile apps.
Rendering of Loop components in Word for the web will be retired in September 2025, shifting to read-only placeholders.
Learn how to disable or enable Copilot Notebooks for users. Manage access by configuring the updated Cloud Policy to control who can use these features in OneNote and Microsoft 365 Copilot Chat.
I wrote a PowerShell script to get all SharePoint Embedded containers (like Loop Workspaces, Microsoft Designer, or both). The script handles paging automatically.
Users will soon be able to access Copilot Pages directly in the Copilot web app instead of Loop on the web, as they have in the past.
Teams owners cannot delete the new (Teams) channel-connected Loop Workspaces. I describe how an admin can delete such Loop containers.
Microsoft provides a new PowerShell property for Loop workspace containers to define the workspace type.
The SharePoint admin center can include new Designer containers. I can fully explain the cause of these crazy Designer containers.
Microsoft Loop in Teams and mobile apps allows users to apply file-level sensitivity labels to Loop files, enhancing data protection in the Teams apps.
Teams now supports Shared Group Workspaces. The new Loop container is connected to a Teams channel. All members of the team have access to the workspace by default.
It seems that SharePoint, OneDrive, or Teams has a misconfiguration related to permissions for Collaborative Meeting Notes when they are created in the new Teams calendar.
Loop Workspaces will allow multiple owners, enabling users to promote members to owners within shared workspaces.
Microsoft Loop now offers a personal workspace for users with a OneDrive. The existing Ideas workspace will transition to a shared Loop workspace.
For organizations with Sensitivity Labels, Microsoft has added support for guests in Loop Workspaces.
Microsoft Teams now allows users to forward Loop components in chats and channels. This update removes previous restrictions on forwarding messages with Loop components.
Microsoft has updated the licenses required for Microsoft Loop and Loop Workspaces in the Business and Enterprise licenses overview.