Microsoft Loop: Sensitivity labels at the container level [MC923176]

Microsoft Loop: Sensitivity labels at the container level [MC923176]

Message ID: MC923176

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:

  • Sensitivity labels on Loop workspaces at the storage container-level. Note: Sensitivity labels are also known as Microsoft Information Protection (MIP).

Coming in future rollouts:

  • Item-level sensitivity labels in Loop components and collaborative meeting notes in Microsoft Teams (on the web, on Windows desktops, and on iOS/Android)

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:

“admin

[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

Source: Microsoft

Show 1 Comment

1 Comment

  1. Mike Rosoft

    The upcoming update for Microsoft Loop is set to bring some exciting changes for admins and users alike! With the introduction of sensitivity labels at the container level, organizations that have enabled sensitivity labels (Microsoft Information Protection or MIP) can expect enhanced security features.

    For admins, this update means that they will have more control and flexibility in applying sensitivity labels to Loop workspaces. It simplifies the process of managing security at a broader level within the organization. Admins won’t need to take any specific actions to prepare for this rollout, making it a seamless transition.

    As for users, this update will provide a more intuitive way to categorize and protect their Loop files, components, pages, and collaborative meeting notes. By having sensitivity labels available at the container level, users can ensure that their data is appropriately protected and classified.

    The impact of these changes is expected to be significant, especially in enhancing data security and compliance within organizations. It’s a step forward in ensuring that sensitive information is handled with the utmost care and protection.

    So, get ready to experience the benefits of these new security features in Microsoft Loop! Feel free to share your thoughts on how this update will impact your organization, and let’s keep the conversation going. Your feedback and insights are valuable!

Leave a Reply

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