Where do Copilot Pages and Notebooks live — and can we govern them?

You’re right to treat Pages and Notebooks as storage and compliance decisions, not just “nice chat artefacts.” They look ephemeral in the Copilot pane; they aren’t.

Here’s what’s going on. Copilot Pages (.page) and Copilot Notebooks (.pod) live in the same user-owned SharePoint Embedded container as Loop My workspace. In SharePoint admin centre, PowerShell, and Purview audit, that container’s application name is always Loop — there is no separate Pages/Notebooks filter. Storage counts against organisation SharePoint quota. Admins govern creation through Microsoft 365 Cloud Policy: Create and view Copilot Pages and Copilot Notebooks (default enabled) and, separately, Enable code previews for AI-generated content in Microsoft Copilot Chat and Copilot Pages. Pages/Notebooks can be enabled or disabled independently of Loop, but the container is still created if either the Pages/Notebooks policy or Loop’s “Create Loop workspaces in Loop” policy allows it for that user. Learn is blunt on Information Barriers: not supported for SharePoint Embedded — if IB is mandatory, disable Pages/Notebooks via Cloud Policy. When a user leaves, the container follows OneDrive-style deletion with a manual handoff for access/ownership; there is no end-user recycle bin for Notebooks.

This is First Law for AI artefacts: don’t let people put work into Pages/Notebooks unless you can see how it comes back out — Purview, eDiscovery, retention, and a leaver path. Steady before scale means Security and GRC know the Loop-named container exists before Adoption sprays “save that as a Page” training.

Options that actually work:

1. Allow for Wave 0 cohorts; document the Loop container. Cloud Policy scoped to a Microsoft 365 / security group for champions; retention via All SharePoint Sites; eDiscovery aware that the app label is Loop. Best Steady default for most tenants.
2. Block Pages/Notebooks, keep Loop (or the reverse). Disable only Create and view Copilot Pages and Copilot Notebooks, or only Loop workspace creation — Learn’s quick-reference scenarios. Use when IB or risk appetite differs by surface.
3. Block both policies for regulated cohorts. Stops new container creation for those users. Existing items aren’t auto-deleted; sharing links to Notebooks break when creation is disabled.
4. Ignore storage until quota or a leaver incident. Quiet until Compliance discovers “Loop” containers full of Copilot work. Don’t.

12 Panes action / comms: Tell Adoption: Pages and Notebooks are SharePoint Embedded under a Loop application name — train people like file owners, not chat tourists. Tell Compliance: IB isn’t supported here; use Cloud Policy if that’s a hard requirement. Leadership: we’re enabling creation for named cohorts with a leaver handoff, not tenant-wide by default.

Benefits / risks: Clear Cloud Policy stops surprise sprawl and IB conflicts; over-blocking frustrates useful Wave 0 work and drives paste-into-chat shadow habits; disabling creation hides Notebooks in the Copilot app but doesn’t erase existing content; Multi-Geo and legal-hold container picking still have rollout caveats — re-check Learn before promising the board.

I’d suggest this week: open config.office.com → Policy Management, decide Enabled vs Disabled for Create and view Copilot Pages and Copilot Notebooks per cohort, confirm Loop workspace policy doesn’t recreate the container for people you’ve blocked, and add one line to the AI register: Pages/Notebooks = Loop SPE container + Cloud Policy owner. You’ll have a calmer compliance conversation when the storage story matches the product UI.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer