Pages: the answer that became a document
Chat produces an answer; 'Edit in Pages' turns it into a Loop-backed canvas — persistent, shareable, co-editable, with Copilot still attached. Governance translation: a Page is a .loop component in the creator's OneDrive (Loop storage under your OneDrive/SharePoint estate — the Teams curriculum's chat-files logic applies): sharing rides normal file sharing; retention/eDiscovery ride file mechanics (plus the originating INTERACTION is separately recorded — two artifacts from one session, both governable).
The lifecycle consequence you already know from chat files: creator leaves → OneDrive offboarding schedule → shared Pages die with it. Team-critical Pages belong in shared spaces, not personal stores — put it in the adoption guidance now, not after the first loss.
Notebooks: curated grounding
A Copilot Notebook is a working set — you gather specific docs/pages/notes, and Copilot answers WITHIN that pile. Why it matters beyond convenience:
- Scoped grounding beats tenant-wide retrieval for deep work — no drift into the wrong project's files, better answers from less noise.
- It's the self-service version of what agents do with knowledge scopes (agents module) — a taste of scoping discipline with zero admin cost.
- The notebook references content the user can access (permissions model unchanged) — curation is a lens, not an access grant.
What to watch (proofs)
- Where Pages really live: create one, find the .loop in the creator's OneDrive — the storage claim proven; now eDiscovery/retention mapping is just file mapping.
- The leaver drill: a shared test Page through an offboarding simulation — the link-death timeline for YOUR tenant's policy, documented before it's a real loss.
- Discoverability check: one eDiscovery search hitting BOTH the Page content (file-side) and the originating interaction (record-side) — the two-artifact model demonstrated to legal.
- Sprawl signal: Pages/Loop growth in storage reports — the new content class arriving; fold into normal lifecycle governance before it's a migration project.