Share via

Summary of governance, lifecycle, and compliance capabilities for Loop

Note

The Copilot Pages and Copilot Notebooks content can now be found in a dedicated article.

As a Compliance Manager or IT administrator, it's crucial to stay up-to-date on the latest governance, data lifecycle, and compliance posture for the software solutions being used in your organization. This article details the capabilities available and not available yet for Microsoft Loop.

At a glance

Capability Status
Admin policies ✅ Available - Cloud Policy + SharePoint PowerShell
GDPR / EUDB ✅ Supported
Conditional Access ✅ Supported
Information Barriers ◐ OneDrive/SharePoint only (not SharePoint Embedded)
Customer Lockbox ✅ Supported
eDiscovery ✅ Supported (full-text search in review sets not available)
Legal Hold ◐ SharePoint Embedded content is Manual - My workspace container must be added per user
Retention policies ✅ Supported
Retention labels ◐ Limited manual application
Sensitivity labels ✅ Pages, components, and workspaces
DLP ✅ Supported with policy tips
Recycle bin ✅ Components and pages; ❌ Workspaces

SharePoint Embedded

Loop content storage varies based on creation method. For detailed information about storage locations, see storage. Content stored in SharePoint Embedded containers follows the SharePoint Embedded security and compliance documentation.

The sections below outline governance, lifecycle, and compliance capabilities applicable to all Loop storage types. Where capabilities vary by storage location—OneDrive, SharePoint sites, or SharePoint Embedded containers—specific details are provided.

Foundations

Data Security, Devices

Important

Information Barriers are not supported for content stored in SharePoint Embedded containers (Loop workspaces and My workspace). If your organization requires Information Barriers, consider using admin policies to restrict Loop workspace creation.

  • Customer Lockbox: Supported.
  • Guest app access: Available for Loop workspace containers. Enables third-party export/eDiscovery tools, migration tools, and developer APIs. Use PowerShell to Get and Set guest app permissions.

Data Lifecycle

  • Loop's My workspace, Copilot Pages, and Copilot Notebooks are stored together in a single, user-owned SharePoint Embedded container, identified and owned by Loop. Shared Loop workspaces create one SharePoint Embedded container per workspace. These containers don't have individual storage limits; instead, their storage usage counts toward your organization's overall SharePoint storage quota. Currently, there's no admin control to set storage limits for individual SharePoint Embedded containers. Loop files in their OneDrive and SharePoint locations follow the quotas of these storage locations.

  • See Managing SharePoint Embedded containers for information and workflows within SharePoint Admin center or PowerShell.

    Important

    Unlike OneDrive, for the Loop My workspace, there's no user workflow for content stored in the user-owned SharePoint Embedded container after user departure. The container is deleted on the same schedule as the default OneDrive settings. See Storage management after user departure for detailed information.

  • Multi-Geo capabilities for My workspace are supported.

    • My workspace is a user-owned SharePoint Embedded container and is created in the geo that matches the user's preferred data location.
    • Loop content created in OneDrive and SharePoint follow the multi-geo capabilities of OneDrive and SharePoint.
    • Multi-Geo support for shared Loop workspaces use the same mechanism as SharePoint Communication sites, including rehome and creation in the tenant's default geo. Manage shared Loop workspace locations like other collaborative artifacts such as SharePoint Communication sites.

    Important

    Certain operations in Loop workspaces may not function correctly after moving containers across geos, such as sharing or creating new pages. Microsoft is aware of the issue and is working on a fix.

  • End-user Recycle bin for deleted Loop components and pages is available within the Loop workspace, OneDrive, or SharePoint site.

    Important

    There's no end user recycle bin for Loop workspaces. Furthermore, restoring the Loop workspace using admin tooling doesn't update in the Loop app user experience. The user would need to visit a saved page link for a restored workspace in order to see it again. Microsoft Roadmap ID 421615 addresses this.

  • Version History export in Purview or via Graph API is available. Loop workspace content stored in SharePoint Embedded (See storage for more information), version history is configured to save 50 versions and no admin setting is available to change this configuration. Loop files in OneDrive or SharePoint follow the same file versioning settings as other files.

  • Audit logs exist for all events. They're retained, can be exported, and can be streamed to third party tools. For more information, see Purview.

eDiscovery

  • Purview eDiscovery: Supported for search/collection, review (Premium license required), and export as HTML (Premium license required) or original format. Download and reupload files to OneDrive to view in native format.
    • Limitation: Full-text search within .loop files in Purview review sets isn't available.
  • Graph API export: Supported for third-party tools. Use PowerShell to Get and Set guest application permissions.
  • Legal Hold: Supported. Content is stored in the Preservation Hold Library.
    • Known Issue: Unlike OneDrive, Loop's My workspace isn't automatically included when a user is placed on Litigation Hold. You must manually add the My workspace container for each user when placing the user on Litigation Hold.

Microsoft 365 retention and deletion

  • Retention policies from Microsoft Purview Data Lifecycle Management configured for all SharePoint sites are enforced for all .loop files or alternatively can be configured per Loop workspace.

  • Retention labels from Microsoft Purview Data Lifecycle Management and Microsoft Purview Records Management are supported for Loop components by applying published labels in OneDrive or SharePoint, or automatically applying the labels. There's limited support for manually applying retention labels.

    • Retention labels can't be viewed or applied directly from a Loop component. Instead, the user must navigate to the Loop file within the Loop app to view or apply a retention label on a Loop component.
    • Retention labels that mark the content as a record or regulatory record can't be manually applied in either the Loop component or when the content is opened in the Loop app. If content is automatically labeled as a record, locking and unlocking this record isn't yet available.
    • For clarification only, not a limitation: retention labels don't apply to containers like SharePoint sites or Loop workspaces; instead, use retention policies for these containers. To learn more, see retention.

Information Protection

  • Sensitivity labels: Available for Loop pages and components. Workspace sensitivity labels are configurable per workspace (at container level) via SharePoint Admin Center and PowerShell. See configuring sensitivity labels.
    • Note: There's no admin setting to configure guest sharing of specific Loop workspaces. Use container sensitivity labeling for per-workspace external sharing configuration.
  • Data Loss Prevention (DLP): Rules enforced with end-user policy tip support.
  • Last updated on