Microsoft Loop workspaces deep dive
By Emil Björk · Microsoft ecosystem consultant, Gothenburg
How Loop workspaces work — the hidden Microsoft 365 Group backing, sharing model, and governance.
4 min read
Share as imagePNG
A Loop workspace is the container in the Microsoft Loop app for a set of related pages. Workspaces are where teams use Loop most heavily — for ongoing collaborative content that doesn't fit a Word document or a Teams chat. The architecture behind workspaces matters for governance and lifecycle.
Workspaces are the container level of Microsoft Loop explained, built from Loop components, governed per Loop external sharing, and increasingly created through Copilot Pages and Copilot Notebooks.
What's in a workspace
A workspace contains:
- Pages — Notion-like documents built from Loop components and blocks.
- Sub-pages — pages nested under other pages, with arbitrary depth.
- Workspace settings — name, icon, member list.
- Activity — recent changes by members.
Pages can have rich content: text, headings, tables, task lists (integrating with Planner and To Do), Q&A, code blocks, embeds (Figma, YouTube, Power BI), images, and AI-generated content via Copilot.
What backs a workspace
Behind every workspace is a hidden Microsoft 365 Group with an associated SharePoint site. Workspace pages are stored as files in that site. This has practical implications:
- Permissions are managed through the workspace UI but ultimately map to Microsoft 365 Group membership.
- Retention policies for SharePoint apply to workspace content.
- Sensitivity labels can be applied.
- eDiscovery searches reach workspace pages.
- Audit logs in Purview cover workspace activity.
Sharing models
A workspace can be shared with:
- Specific people — explicit members.
- A team — extending the workspace to all team members (with the relevant Microsoft 365 Group).
External sharing of workspaces was rolled out progressively; check current capabilities in your tenant. Loop components (embedded in chats, emails) can travel to anyone with access to the host content, regardless of workspace membership.
When to use workspaces vs other surfaces
- Workspace — ongoing collaborative content for a specific team, multi-page knowledge base, in-progress project notes.
- Teams channel — synchronous chat plus loose files.
- SharePoint site — published intranet content, polished documents.
- OneDrive — personal working files.
- Loop components — small reusable blocks embedded in other apps.
The boundaries are blurry. Many teams use multiple: a Teams team for chat, a Loop workspace for collaborative knowledge, a SharePoint site for finished documents.
Governance controls admins actually have
Because every workspace is a Microsoft 365 Group underneath, the governance levers are the ones already familiar from Teams and SharePoint site governance, rather than a separate Loop-specific admin surface:
- App-level rollout control — the Loop app (like any first-party app) can be targeted to pilot groups or blocked tenant-wide through app policies in the Microsoft 365 admin center, letting a phased rollout happen without touching the underlying group infrastructure.
- Group creation restrictions — if your tenant restricts who can create Microsoft 365 Groups, that same restriction governs who can create a new Loop workspace, since workspace creation provisions a group.
- Group expiration policies — an inactive workspace's group is subject to the same expiration and renewal nudges as an inactive Team, which is the practical answer to workspace sprawl: let the platform's existing lifecycle policy do the cleanup rather than building a Loop-specific one.
- Sensitivity labels and container settings apply exactly as they do to Teams — labelling a workspace's underlying group can restrict external sharing and guest access even though the label is applied through the Loop UI rather than the Teams admin center.
- Naming and classification policies for Microsoft 365 Groups apply here too, so a tenant enforcing a naming convention on Teams will see the same prefix/suffix show up on the SharePoint site backing a Loop workspace.
The practical governance takeaway: don't look for a "Loop admin center." Loop workspace governance is Microsoft 365 Group governance, wearing a different front end — which is good news for tenants that already have that story straight, and a trap for anyone who assumed a new app needed a new set of controls.
Operational notes
- Workspace ownership — every workspace should have a clear owner; orphaned workspaces accumulate quickly.
- Page hierarchy — start with a flat structure and add depth only when needed. Deep nesting becomes hard to navigate.
- Templates — Loop ships templates for project plans, meeting notes, brainstorms, decisions. Use them as starting points.
- Copilot integration — Copilot can generate content directly into Loop pages, then iterate collaboratively.
For teams already using Microsoft 365 heavily and looking for a Notion-like surface, Loop workspaces are increasingly the right answer. The product has matured significantly since launch.
Frequently asked questions
- What happens to a Loop workspace if the owner leaves the organisation?
- Nothing automatically — the workspace persists because it's backed by a Microsoft 365 Group, and the group survives its owner's departure. It becomes ownerless unless someone reassigns ownership, which is exactly the orphan problem Microsoft 365 Groups have always had; the same group-expiration and ownerless-group cleanup policies that apply to Teams and SharePoint sites apply here too.
- Can admins turn off Loop workspaces tenant-wide?
- Yes — the Loop app can be disabled or scoped to specific security groups through app policies in the Microsoft 365 admin center, the same mechanism used to control other first-party app rollout. Existing workspace content isn't deleted by disabling the app; it just becomes inaccessible through the Loop app itself while the underlying SharePoint site remains intact.
Was this useful?
Spot something wrong or want a topic covered? Send it through the contact form.