Edit

Share via

Overview of Loop storage

  • Applies to: Microsoft Teams

Storage

Note

The Copilot Pages and Copilot Notebooks content moved to a dedicated article.

Loop content is stored in SharePoint, OneDrive, and SharePoint Embedded, allowing familiar management within existing file management workflows. Where the content was originally created determines its storage location:

Content content originally created in Content stored in SharePoint Embedded Content stored in SharePoint Site Content stored in User's OneDrive Lifetime Management
Loop app, My workspace * ✔️in user-owned container user account
Loop app, shared workspace ✔️in shared container workspace owners
Teams channel workspace ✔️in shared container Microsoft 365 Group
Teams channel meeting ✔️in 📁Meetings Microsoft 365 Group
Teams channel ✔️in Channel folder Microsoft 365 Group
Teams private chat ✔️in 📁Microsoft Teams Chat files user account
Teams private meeting ✔️in 📁Meetings user account
OneNote for Windows or for the web ✔️in 📁OneNote Loop files user account
Whiteboard ✔️in 📁Whiteboard\Components user account

* The My workspace SharePoint Embedded container also contains Copilot Pages and Copilot Notebooks.

My workspace container name

Copilot Pages and Copilot Notebooks all use the Loop My workspace container. This user-owned container is named 'Pages' if the person visits the Microsoft 365 Copilot app first. It is named 'My workspace' if the person visits the Loop app first. Refer to listing all user-owned containers to get a list, regardless of the container name.

Storage quota

All Loop workspaces count against your organization's SharePoint storage quota.

SharePoint Embedded also offers a platform for developers to build their own applications. This alternate usage pattern which bills per use is different from Loop and Copilot Pages storage quota management.

Storage limits

Loop workspaces have a maximum size of 25 TB. This limit can't be increased or decreased. Learn more about SharePoint Embedded container limits.

Storage management after user departure

Types of Loop workspaces

Storage behaviors after user departure depends on the type of Loop workspace. There's one personal workspace per user in your organization, created on demand by the person when accessed. All other created Loop workspaces are shared workspaces. For more information, see workspace membership and Microsoft 365 Groups on the two shared workspace types.

Shared Workspaces

Tenant-owned

  • A roster permissions tenant-owned shared Loop workspaces. If all owners leave the company, the workspace becomes ownerless, remains in the tenant, and isn't automatically deleted.
  • You must be an owner to delete a workspace. If all the owners left the company, members can't delete the workspace until an IT administrator adds new owners.

Microsoft 365 Group-owned

  • The Microsoft 365 Group permissions and manages the lifetime of group-owned shared Loop workspaces, similar to the management of SharePoint Team sites.

Personal Workspaces

  • Copilot Pages, Copilot Notebooks, and My workspace store content within the same user-owned SharePoint Embedded container.
  • This personal content is private by default, allowing users to work without forced sharing or coauthoring, similar to OneDrive.

My workspace

  • My workspace is stored in a user-owned SharePoint Embedded container, created by Loop. The container is lifecycle managed with the user account, deleted when the user account is deleted from the organization.
  • My workspace can't be permanently reassigned to a new owner. It follows the same cleanup schedule as OneDrive: 30 days active, then soft deleted, and permanently purged 93 days after soft deletion.
  • Admins can recover content during the soft delete period using the SharePoint Admin Center or PowerShell.

Note

A feature for IT admins to assign temporary custodians during the cleanup period of user-owned workspaces isn't yet available. This capability for Copilot Pages, Copilot Notebooks, and My workspace is planned (Microsoft Roadmap ID 421612).

Ideas

  • The Ideas workspace is deprecated, no longer created by default, and replaced with the My workspace personal workspace.
  • Ideas were the first default workspace, was tenant-owned, permissioned with a single-person roster.
  • The Loop app doesn't delete the deprecated Ideas workspace; a user or an admin must delete it if needed.
  • If a user doesn't have multiple owners on their Ideas workspace, the workspace becomes ownerless when they leave the company. It remains in the tenant and isn't automatically deleted.

Loop components created in Microsoft 365 outside of the Loop app or Copilot Pages

See Storage. When content is stored in OneDrive, if that user leaves the organization, the standard OneDrive IT policy is applied. When content is stored in SharePoint, the standard SharePoint IT policy is applied. Learn more about OneDrive and SharePoint Retention and Deletion.