Copilot Pages and Loop components

Microsoft 365 Copilot's output is interesting in isolation but most useful when you can keep iterating on it — adding context, sharing with colleagues, editing collaboratively. That's what Copilot Pages and Microsoft Loop components are for: persistent, multi-user, multi-app surfaces for AI-generated content.

Loop components

A Loop component is a portable, live, collaborative block of content. It lives in Microsoft Loop but can be pasted into Teams chats, Outlook emails, Word documents, OneNote, and Whiteboard. Wherever it appears, it's the same component — edit it in one place and the change propagates everywhere.

Component types include:

• Lists — bulleted, numbered, task, voting.
• Tables.
• Paragraphs of rich text.
• Task lists that integrate with Planner and To Do.
• Code blocks.
• Person lists with status fields.
• Q&A components.

Loop components are best for lightweight ongoing collaboration — a kickoff agenda, a punch list, a status update — where multiple people contribute and the content should stay live, not get scattered across a dozen email replies.

Microsoft Loop (the app)

Beyond components, there's a full Loop app (loop.cloud.microsoft) where you create workspaces containing pages. Each page is a Notion-like document made up of components. Workspaces are shared, pages can be public to the workspace or scoped, and the whole thing syncs in real time.

Loop is Microsoft's answer to Notion, Coda, and similar modern collaborative document tools. It's still maturing but increasingly the default for in-progress collaborative content.

Copilot Pages

Copilot Pages is the AI-assisted authoring surface inside Loop. When you ask Microsoft 365 Copilot something in the standalone Copilot Chat experience, you can promote the response to a page. The response becomes an editable Loop page that you can:

• Refine with further Copilot prompts.
• Edit collaboratively with colleagues.
• Share into a Teams chat, channel, or workspace.
• Anchor in a Loop workspace alongside related content.

This turns Copilot from a one-shot answer machine into a starting point for an iterative document.

A typical use case

A product manager asks Copilot Chat: "Summarise the customer feedback from last week's interviews and propose three feature ideas."

Copilot pulls from notes, transcripts, and Teams chats; produces a summary; PM clicks "Edit in Pages"; the page opens with the response. PM:

1. Refines specific bullets with /copilot inline prompts.
2. @-mentions a colleague to add their perspective.
3. Embeds the page as a Loop component in a Teams channel.
4. Iterates over the next several days as the team adds detail.

The same workflow used to require: 1 prompt, 1 doc, 1 share, several emails, several iterations.

Governance considerations

Loop components and pages are stored in OneDrive (for personal-owned content) or in SharePoint (for organisation-owned, via Loop workspaces backed by Microsoft 365 Groups). They inherit:

• Microsoft 365 retention policies.
• Sensitivity labels.
• DLP policies.
• eDiscovery searchability.

Admins enable / disable Loop and Copilot Pages via Microsoft 365 admin center tenant settings. Roll-out follows the same pattern as other modern Microsoft 365 collaboration surfaces.

Copilot Pages and Loop together are the "what's next" surface for collaborative work in Microsoft 365 — the part most worth piloting for teams already comfortable with the basics.