Microsoft Loop will soon introduce container-level sensitivity labels, enhancing security features for organizations using Microsoft Information Protection. This update, part of Microsoft 365 Roadmap ID 111225, will roll out between late October and early December 2024, requiring no admin action prior to rollout.
Coming soon: New security features for Microsoft Loop for organizations that have enabled sensitivity labels (also known as Microsoft Information Protection or MIP).
Before this rollout, Microsoft Loop supports users or admins adding item-level sensitivity labels on all .loop files (including Loop components, Loop pages, and Copilot pages) in the Microsoft Loop app (on the web and for iOS/Android) and new Microsoft Outlook for Windows and Outlook for the web, classic Outlook for Windows, Outlook for Mac, Outlook on Android and iOS.
With this rollout, we will support:
Coming in future rollouts:
This message is associated with Microsoft 365 Roadmap ID 111225.
When this will happen:
Container-level Sensitivity Labels for Loop workspaces: General Availability (Worldwide): We began rolling out late October 2024 and expect to complete by early November 2024 (Loop app for the web)
Container-level Sensitivity Labels for Loop workspaces: General Availability (Worldwide): We will begin rolling out in November 2024 and expect to complete by early December 2024 (Loop apps for iOS/Android)
How this will affect your organization:
After this rollout, container-level sensitivity labels on Loop workspaces will be available by default.
Admins do not need to do anything to prepare for this rollout. If your tenant has sensitivity labels configured at the item-level for Files, you or your users will be able to apply these labels to all Loop files (including Loop components, Loop pages, and Copilot pages). If your tenant has sensitivity labels enabled for Groups & sites, then you or your users will be able to apply these labels and policies to your Loop workspaces.
Applying a sensitivity label to a Loop workspace:
What you need to do to prepare:
This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your users about this change and update any relevant documentation.
Learn more