Loop governance, lifecycle, manageability for IT Admins – Nov 2024 [MC938646]

Loop governance, lifecycle, manageability for IT Admins – Nov 2024 [MC938646]

Message ID: MC938646

In response to your feedback, we’ve updated public documentation, published IT Admin items to the Microsoft 365 Public Roadmap, issued Message Center posts for roadmap features, and summarized everything in a comprehensive blog, linked below, on managing Loop in your organization.

Blog: Loop governance, lifecycle, manageability for IT Admins – Nov 2024

This message is associated with and summarizes multiple Microsoft 365 Roadmap IDs. See below.

[When this will happen:]

Each Microsoft 365 Roadmap ID has its own schedule and MC post. Refer to each Roadmap ID for details. This summary is a convenience. Recent IT Admin blog summary covers:

ID 111225, MC923176: Loop workspace Sensitivity Labels

Users can apply container-level sensitivity labels to Loop workspaces to prevent oversharing and manage access effectively.

ID 421614, MC923419: Loop guest sharing via Entra B2B configuration for organizations with sensitivity labels

Enable B2B guest sharing for Loop workspaces, pages, and components, subject to administrator policy. This allows sharing with people outside your tenant, and now includes organizations that utilize sensitivity labels.

ID 397755, MC929030: Retention Labels are available for Loop pages and components

Organizations that rely on Microsoft’s records management capabilities in Purview can now include Loop content in their workflows with Retention Labels on Loop pages and components. There’s an in-app experience when a label is applied.

ID 421613, MC929029: Common Admin Management Tasks Enabled for all Loop workspaces

Admins can manage membership, ownership, deletion, and restoration of Loop workspaces in the SharePoint Embedded admin center or PowerShell. These changes are visible within the Loop experience.

ID 422727, MC929028: New personal Loop workspace

The Loop app now provides a personal workspace to all users, which is shared with Copilot Pages. This personal workspace is a user-owned SharePoint Embedded container, one per user. All governance, lifecycle management and compliance processes apply the same way they would to a user’s OneDrive.

ID 422729, MC929028: Ideas Workspace Functions as a Shared Loop workspace.

Loop Ideas workspaces are tenant-managed like SharePoint Communication sites. They appear with existing Loop workspaces, with all features such as adding members and organizing pages.

ID 362124, MC929027: Promote Members to Owners in Loop workspaces

Loop workspaces support multiple owners, allowing end-users to promote members to owners.

ID 422728, MC929023: Microsoft 365 Groups for Managing New Loop workspaces

When creating a new Loop workspace, users can choose an existing Microsoft 365 Group to manage the workspace’s lifetime, governance, and compliance, similar to SharePoint Team sites.

ID 422725, MC929022: Require Existing Microsoft 365 Group for New Loop workspaces

Ensure new Loop workspaces are connected to and managed by an existing Microsoft 365 Group, similar to SharePoint Team sites.

ID 421616, MC929025: Multi-Geo Support for Shared Loop workspaces

Data storage for shared Loop workspaces in the correct geo. M365 group-owned workspaces are created in the group’s geo, while non-M365 group-owned workspaces are created in the creator’s preferred data location.

ID 421615, MC929021: User Accessible Recycle Bin for Loop workspaces

When users delete a Loop workspace, owners can restore it from a recycle bin in Loop. In development Published 9119872

ID 421611, MC929020: Admin Usage Reports

View and monitor Loop usage in the tenant through existing M365 admin usage dashboards.

ID 421612, MC929014: Departed User Content Workflows for User-Owned Loop workspaces

Manage retention and deletion workflows for user-owned Loop workspaces like Copilot Pages when users leave the organization. Notify and provide temporary access to other employees or administrators to save important data before deletion policies take effect.

General Availability (Worldwide): We will begin rolling out late November 2024 and expect to complete most of the work by late April 2025.

[How this will affect your organization:]

We’ve consolidated all the information in one place to build confidence for enabling and using Loop in your organization. The blog and companion video (linked in at the top of the blog) provide the full story. Leave your questions in the blog comments!

Blog: Loop governance, lifecycle, manageability for IT Admins – Nov 2024 

[What you need to do to prepare:]

No action needed. These capabilities will be available automatically with each feature rollout.

Source: Microsoft

Leave a Comment

Comments

No comments yet. Why don’t you start the discussion?

Leave a Reply

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