Skip to content
Browse all topics
Microsoft 365 Copilot

Copilot inside a Loop page

By Emil Björk · Microsoft ecosystem consultant, Gothenburg

Using Copilot to draft, summarise, and rewrite content on a Microsoft Loop page, and how that differs from Copilot Pages and Loop components in chat.

2 min read

Share as imagePNG

Loop pages are meant to be built collaboratively and to stay live wherever they're shared — a meeting note, a project plan, a running list that several people edit at once. Copilot's role inside that is the same as elsewhere in Microsoft 365: draft the first version, tidy what's there, and summarise when a page has grown long.

Where to find it

Open a Loop page (from the Loop app, a .loop file in OneDrive, or a Loop component shared in Teams or Outlook) and look for the Copilot icon on the page toolbar or in the component's own menu. It works at the level of the page or the specific component you're focused on.

What it does

Draft a page from a prompt. Start a blank page and ask Copilot to draft a project brief, a meeting agenda, or a status update structure. It writes directly into the Loop page as editable content — not a chat transcript, but the actual page.

Summarise a long page. A planning page that's accumulated weeks of edits, comments, and additions can be summarised so a new team member (or anyone who's been away) gets the current state without reading the whole edit history.

Rewrite and tidy. Select text on the page and ask for a cleaner version, a different tone, or a shorter one — the same rewrite behaviour familiar from Copilot in Word, applied to a Loop page instead.

Extract tasks. Ask Copilot to pull action items out of a planning page into a task list component, so a discussion turns into a tracked list without manual re-typing.

How this differs from nearby features

Copilot Pages are a specific kind of page created from a Copilot chat — you ask Copilot something, then turn the answer into a shareable, co-editable page. Working with Copilot inside a Loop workspace page is broader: it applies to any Loop page or component, whether or not it started as a chat. See Copilot Pages and Loop components for the Pages side of that distinction, and Loop components in a Teams chat for how a single component behaves when it's shared inline rather than as a full page.

What it needs

A Microsoft 365 Copilot licence for the AI features described here. Loop itself is included in Microsoft 365 for everyone and doesn't require Copilot to create or co-edit pages — only the drafting, summarising, and rewriting on top of it do. Loop content follows the same OneDrive/SharePoint storage and sharing permissions as other files, so who can see a page is governed the normal way.

Where it falls short

Very active pages with many simultaneous editors can be a moving target for a summary — what Copilot summarises is a snapshot, not a live feed. Deeply nested components (tables inside tables inside a task list) sometimes confuse a "summarise this page" prompt; asking about a specific component tends to work better than asking about the whole page at once.

Frequently asked questions

Is Copilot in Loop the same as Copilot Pages?
They're related but not identical. A Copilot Page is created from a Copilot chat and lives as its own shareable, co-editable canvas. Copilot inside a Loop workspace page works on content you and others are building directly as a Loop page or component, which may not have started life as a chat at all.
Do I need a Microsoft 365 Copilot licence to use Copilot in Loop?
Yes, for the Copilot drafting and summarising features described here. Loop itself — creating pages, components, and workspaces — doesn't require a Copilot licence; only the AI features on top of it do.
Can people without a Copilot licence still use a Loop page I've drafted with Copilot?
Yes. Once content is on the page it's ordinary Loop content — anyone with access to the page can read and co-edit it regardless of whether they have Copilot themselves.
Does Copilot in Loop read other pages in the same workspace?
By default it works on the page you're editing. Referencing other content explicitly (similar to @-referencing a file in Word) brings more context in, where that's supported.

Further reading

Microsoft Docs & product blog

Was this useful?

Spot something wrong or want a topic covered? Send it through the contact form.