Microsoft Loop explained

Microsoft Loop is Microsoft's modern collaborative document platform — pages built from reusable, real-time components that can be embedded across Teams, Outlook, Word, and more. It's Microsoft's answer to Notion, Coda, and the broader category of "blocks-based" collaborative documents.

Go deeper with Loop component patterns, Loop workspaces, Loop external sharing and governance, and Copilot Pages and Loop components. The neighbouring canvas tools are Whiteboard in meetings and Whiteboard for hybrid workshops.

What Loop is

Loop has two faces:

• The Loop app at loop.cloud.microsoft — a standalone web app where users create workspaces containing pages, each built from blocks of content.
• Loop components — portable blocks that can be embedded in Teams chats, Outlook emails, Word documents, OneNote, Whiteboard. The same component is the same live content everywhere.

The key trick: edit a component in Teams chat, and the change appears in the same component embedded in Outlook, with no manual sync.

The block types

A Loop page or component can include:

• Paragraphs of rich text.
• Headings (multiple levels).
• Lists — bulleted, numbered, checklist, voting.
• Tables.
• Task lists that integrate with Planner and Microsoft To Do.
• Person mentions that resolve to Microsoft 365 identities.
• Code blocks with syntax highlighting.
• Images, videos, files.
• Q&A components.
• Embeds — pull in content from other apps (Figma, Adobe XD, YouTube, etc.).
• AI-assisted content generated via Copilot.

Loop workspaces

A workspace is a Loop home for a group of related pages. Workspaces are shared with specific people (not yet with whole tenant directories), with each member getting access to all pages. Backed by a hidden Microsoft 365 Group and SharePoint site for storage.

Pages within a workspace can be hierarchical (page contains sub-pages), search across the workspace works, and changes flow live.

Loop and Copilot

When Microsoft 365 Copilot generates content in the standalone Copilot Chat experience, you can export to Pages — the response becomes an editable Loop page that you can refine collaboratively. This is one of the most underrated Copilot patterns.

How Loop fits with Microsoft 365

• OneNote — Loop is for collaborative working documents; OneNote is for personal or team notebooks with section/page structure.
• Word — Word is for finished documents with rich formatting; Loop is for in-progress collaborative content.
• SharePoint pages — for published content with broader audiences; Loop for working content.
• Teams chat — Loop components are embedded inside Teams chat; Loop pages can replace shared docs for ongoing collaboration.

A practical pattern: working notes and brainstorms in Loop, polished output in Word or PowerPoint when needed.

Governance

Loop content is stored in OneDrive (personal) or SharePoint (shared via workspaces). It's:

• Subject to retention policies.
• Searchable in eDiscovery.
• Covered by sensitivity labels.
• Auditable via Purview.

Tenant admins enable / disable Loop via the Microsoft 365 admin center. New tenants increasingly have Loop on by default.

When to use Loop

• Cross-app collaboration where the same content needs to live in chat, email, and a doc.
• Working content that several people contribute to over days or weeks.
• Copilot output iteration.
• Lightweight knowledge management in a team.

For tasks where Word or SharePoint pages are the obvious answer (finished documents, published intranet), stay with them. Loop is for the messy middle.