What it does

Copilot Pages is a persistent, shareable canvas built on Loop. You take a good Copilot response and "edit in Pages", then keep working on it with others and with Copilot alongside.

Key facts

• Pages turns an ephemeral chat answer into durable, collaborative content — the thing chat responses normally lack.
• Built on Loop, so it syncs and coauthors like a Loop page.
• Available from Copilot Chat; you promote a response into a Page.
• Multiple people (and Copilot) can work the same Page at once.

When to use / skip

Use it the moment a Copilot answer is worth keeping and building on with a colleague. Skip it for one-off questions you'll never look at again — that's what plain chat is for.

Configuration decisions

• Whether Loop is enabled, since Pages depends on it.
• How Pages content is governed and retained, given it lives on the Loop platform.

Gotchas

• No Loop, no Pages. If Loop is switched off in the tenant, this feature simply isn't there.
• People treat it as a scratchpad and forget it's shareable, collaborative content with the governance that implies.
• Version history and retention behave like Loop, not like a classic Word doc — set expectations.

Consultant notes

• This is the answer to "great, but where did that Copilot answer go?" — position it as the bridge from chat to lasting work.
• Its dependency on Loop being enabled catches teams out constantly. Check the tenant state first.
• Governance for Pages rides on Loop's model, which security teams often haven't reviewed. Raise it early.

---

Worth revisiting after the next release wave.