In this post we explore the different types of Loop components and how they get stored in Microsoft 365.
I’ve been using Loop quite a bit recently, but I personally have found it quite confusing to understand where each Loop component gets stored and how. So I’ve decided to breakdown the different types of components and where they get stored in this post!
What are Loop components?
Microsoft say Loop components are sharable elements that stay in sync across Microsoft 365. These components, such as tables or task lists allow collaborators to work together in real time on content in a single place. There are multiple types of Loop components available for use. Different components get presented depending on where you are creating your component (for example: In a Teams chat). There are, however a shortlist of templates to choose from, including:
- Task list: A detailed task tracking table, with the ability to assign tasks to people and set due dates.
- Voting table: Let your collaborators decide, best idea wins!
- Progress tracker: Big and small – track it all.
- Calendar: Calendar functionality within Loop.
- Kanban board: Plan and track your teams’ work items in a Kanban board.
- Team retrospective: Reflect on the project, celebrate wins and brainstorm improvements.
- Q&A session: List questions as they come up, and everyone can collaborate live on answers.
As well as the above component templates, there are also page templates which can be seen below and also accessible via the template gallery:
Understanding Loop Pages and Workspaces
While a Loop component is a single piece of content, a Loop page is a container for multiple components. A Loop page can be used to pull several components together, such as a project plan, a meeting summary, or a collaborative document. These pages are organized within Loop workspaces, which serve as shared digital spaces for teams to manage all their projects in one centralized location. This structure allows a team to have a single, dedicated area to track all their work without having to search through multiple chat threads.
How Loop content is stored
The storage location for Loop content is determined by where it was originally created. Every Loop component and page is saved as a file that counts toward your organization’s storage quota. Here is a clear overview of where your Loop content is stored:
| Creation location | Storage location |
|---|---|
| Teams 1:1 or group chats | Chat creator’s OneDrive |
| Outlook email | User’s OneDrive |
| Loop app workspace (my workspace) | User-owned SharePoint Embedded container |
| Loop app workspace (shared) | Shared SharePoint Embedded container |
| Teams channel workspace | Shared SharePoint Embedded container, managed via Microsoft 365 group |
| Teams channel meeting | Stored in SharePoint (Meetings folder), managed via Microsoft 365 group |
| OneNote | User’s OneDrive |
| Whiteboard | User’s OneDrive |
A note on SharePoint Embedded
While individual Loop components are stored in users’ OneDrive, the storage for Loop pages and workspaces is a bit different. They are stored in SharePoint Embedded, which is an API-only solution, meaning it doesn’t have a user interface like a standard SharePoint site. Loop workspaces use this service to store their content in a dedicated container within your organization’s tenant. Content stored in SharePoint Embedded is isolated within a dedicated container for the Loop app, meaning it’s only accessible through the app itself. Since it’s built on the Microsoft 365 platform, content stored in SharePoint Embedded is subject to the same compliance and security policies that apply to your other Microsoft 365 data.
IT admin controls
IT admins can control who can create and use Loop content across Microsoft 365. This can be done through a set of policies that govern different Loop experiences. The main controls for managing Loop are:
- Policy-Based Configuration: Admins can use the M365 admin center or cloud policy to manage the creation of Loop content. These policies can be applied to the entire organization or to specific user groups.
- Compliance and Security: Admins can use eDiscovery and Data Loss Prevention (DLP) in Purview to manage Loop content, just as they would with any other file.
- Storage Management: All Loop workspaces/ pages created within the Loop app are stored in SharePoint Embedded and count towards the organization’s SharePoint storage quota and can be managed via the SharePoint admin center.
Leave a Reply