# Microsoft Loop

Shared pages and portable components within a Microsoft 365 tenant.

Revision: 2026-09-15.1 · Review: unreviewed

Commissioned by a Nimbalyst maintainer. Public-source synthesis; no independent review or product execution.

## Applicability

Living documentation accessed 2026-09-15; pin plan, client, deployment and tenant policies before use.. Work or school Microsoft 365 tenant; excludes personal-account and Copilot-specific capabilities..

## Claims

- **yes · documented**: Authors flexible pages containing notes and components. [Microsoft Loop overview](https://support.microsoft.com/en-us/loop/get-started-with-microsoft-loop) Scope: Loop pages in the work/school app.
- **yes · documented**: Provides real-time co-authoring in shared content. [Microsoft Loop collaboration model](https://support.microsoft.com/en-us/microsoft-365-copilot/compare-microsoft-loop-copilot-pages-and-copilot-notebooks) Scope: Supported Loop clients and Microsoft 365 context.
- **yes · documented**: Groups project content into shared workspaces. [Microsoft Loop overview](https://support.microsoft.com/en-us/loop/get-started-with-microsoft-loop) Scope: Workspace creation depends on tenant policy and entitlement.
- **yes · documented**: Can share pages or components with edit or read-only access. [Microsoft Loop permissions](https://learn.microsoft.com/en-us/microsoft-365/loop/loop-permission?view=o365-worldwide) Scope: Workspace members have edit access to every page in that workspace.
- **yes · documented**: Supports sharing an individual page or component. [Microsoft Loop permissions](https://learn.microsoft.com/en-us/microsoft-365/loop/loop-permission?view=o365-worldwide) Scope: Page links do not reduce access already granted by workspace membership.
- **partial · documented**: The permissions guide allows guest sharing under tenant conditions; the overview still says external sharing is unavailable. [Microsoft Loop permissions](https://learn.microsoft.com/en-us/microsoft-365/loop/loop-permission?view=o365-worldwide) [Microsoft Loop overview](https://support.microsoft.com/en-us/loop/get-started-with-microsoft-loop) Scope: Unresolved documentation conflict. Confirm tenant, guest identity, sensitivity labels and actual behavior before relying on it.

## Open questions

- Which client versions, plan and administrator policies apply to the team?
- What survives a representative export: links, attachments, comments, permissions and history?
- How do simultaneous edits, temporary disconnection and member departure behave on the chosen setup?
- Resolve the conflict between the overview and the dated guest-permissions guide on an authorized test tenant.

## Verification plan

1. Use the small-team-knowledge investigation to specify the required collaboration and access boundaries.
2. With explicit authorization, create an isolated synthetic workspace and named test accounts; do not invite real colleagues or upload private knowledge.
3. Test editing, viewer restrictions, recovery and export with pinned clients and plan; retain sanitized artifacts before drawing conclusions.

Last checked: 2026-09-15. Recheck by: 2026-10-15.

Content rights: Unlicensed prototype; redistribution decision pending.