The described behavior aligns with how Microsoft 365 Copilot Pages currently work: Pages are a distinct, persistent feature within Microsoft 365 Copilot Chat, stored and managed as their own artifacts, and are not just transient sidebar content.
From the available information:
- Copilot Pages are described as “an interactive canvas within Microsoft 365 Copilot Chat that lets you turn Copilot responses into editable, shareable pages” and are explicitly called out as:
- Persistent – “Save and edit AI-generated content, making it durable and reusable.”
- Shareable – “Easily share pages with your team through Teams, Outlook, or the Microsoft 365 app.”
- Multiplayer – “Work collaboratively with your teammates, seeing everyone’s contributions in real-time.”
- Additional documentation focuses on:
- Getting started with Microsoft 365 Copilot Pages.
- Drafting content with Copilot Chat and Copilot Pages.
- Sharing Copilot Pages and collaborating on them.
- FAQs about how Copilot Pages work.
The context provided does not document a separate, ephemeral “sidebar-only” Pages feature, nor any automatic connection between a sidebar “Summarize to page” action and a separate OneDrive-based Pages product. It only documents the persistent Copilot Pages experience and how to use it (create, save, share, and collaborate).
Given the available documentation, the appropriate guidance is:
- Treat Copilot Pages as the persistent, Microsoft 365-integrated feature described in the docs, using the documented entry points (Microsoft 365 Copilot Chat, Microsoft 365 app, Teams, Outlook) rather than assuming that any sidebar action automatically creates a OneDrive-based artifact.
- Use the documented workflows to:
- Create and refine content in Copilot Pages.
- Explicitly share and collaborate on those Pages.
- For product feedback about naming conflicts or UX confusion (for example, if a specific Edge sidebar “Summarize to page” flow does not behave as expected or appears disconnected from Microsoft 365 Copilot Pages), submit feedback through the in-product feedback mechanisms (e.g., “Send feedback” or “Help & feedback”) so it can be routed to the product team.
The current documentation does not describe or guarantee that a “Summarize to page” action in a browser sidebar will automatically create a persistent Microsoft 365 Copilot Page stored in OneDrive, nor does it describe any automatic linkage between such a sidebar artifact and the Microsoft 365 Copilot Pages home.
References: