Have you already tried one of the latest features to Microsoft 365 Copilot: Copilot Pages? These are dynamic, persistent canvases designed specifically for multiplayer AI collaboration ( = working together with others in the same Page in real time). This feature can be used to make spontaneous, AI-generated content durable, editable, and shareable. That’s what Copilot Pages offer and they matter because they turn fleeting Copilot responses into reusable and workable assets. Used via Copilot BizChat, these pages allow users to transform Copilot responses into something more permanent. You can then continue editing the result just like a Loop page. And as a matter of fact, Copilot Pages are Loop Pages.
Think of it as upgrading from a notepad (only you work on your text) to a collaborative workspace where everyone you choose can see and build on each other’s ideas in real-time. This is not just a new tool—it’s a new way of working, blending human and AI interactions into a seamless workflow, if you want to say it in a fancy way. If you have already been using Microsoft Loop, then this way of working is nothing new to you. But if you haven’t: welcome to the future of work happening today.
How to Use Copilot Pages Details for IT Admins Upcoming Features (Q4 CY2024):
How to Use Copilot Pages
Using Copilot Pages is simple and intuitive. Here’s a quick guide to get you started. Remember that you need to have Microsoft 365 Copilot license, to be able to use Copilot Pages today.
Use BizChat (Business Chat, Microsoft 365 Copilot Chat) via Microsoft 365 portal ( https://m365.cloud.microsoft/chat ) or using Copilot inside Microsoft Teams. Copilot Pages are only available at Work-side at the moment.
Interact with Copilot as you normally would. When you receive a response you’d like to keep, click ‘Edit in Pages.’
This will create a page and open it side-by-side with the chat, with the response already copied and formatted.
You can continue your conversation in chat, and each subsequent response can be added to the page by clicking ‘Edit in Pages’ again.
Remember, that these are Loop Pages! You can use a many of rich features what Loop has to offer. Copilot doesn’t seem to work when using Copilot Pages via BizChat, but when you open these pages in the Loop App, you can also use Copilot to summarize, rewrite etc the content on the page.
Note: the name of the page will be the beginning of the prompt you used for the response you chose to Edit in Pages. So.. I warmly recommend you to change the name of the page, so it makes sense to you and others later 😊
You can make it multiplayer, by sharing your page with others. This allows collaborators to view and edit the page, but they won’t have access to your Copilot session. This sharing can be done by clicking the share icon on top right are of your Page.
From there you can choose to share a Page link or Copy component. When pasting the Page to Teams chat (or Outlook, Whiteboard, etc) , use Copy component, but if you want receiver to open the page in Loop App, share a link to that page.
Tip: easy way to share Copilot Page to your colleague by using @-mention and giving permissions to that Page.
This way William will have a notification in his Loop app and can open that page right away.
At this point both Emma and William can edit the content simultaneously in real-time, just like in ordinary Loop pages and components.
You can return to your page by clicking Edit in Pages in the chat where you first created it.
There is also a small page-icon on the top right area of the Page. It indicates that this chat has a page attached to it, and you can open (or close ) the Page by clicking it.
In the near future you can find the Pages tab in Microsoft365.com, where all your previously created pages are stored.
As a best practice, I recommend that relevant Copilot Pages are added to Loop Workspaces ( for example this one would be in a ForestSilk Webpage workspace), so they can be discovered more easily later by you and the team.
I am also looking forward to rest of the features, that were visible in Microsoft’s Copilot Pages videos I have seen.
Details for IT Admins
Copilot Pages are Loop Pages, and thus they already have controls and compliance features:
Storage and Management: Copilot Pages are stored as .loop files in a user-owned SharePoint Embedded container, counting against the tenant’s SharePoint quota. They support all SharePoint file system features, including governance and compliance processes.
Configuration and Control: Admins can control Copilot Pages using Loop admin switches in Cloud Policies (https://config.office.com/ – Customization / Policy Management ). Notably, disabling Loop in the tenant does not disable Copilot Pages, but a specific switch has been added for Pages management which needs to be used. By default Copilot Pages are on.
Copilot Pages are Loop Pages and thus support the capabilities listed in the Summary of governance, lifecycle, and compliance capabilities for Loop. In summary, that includes admin toggles, GDPR and EUDB compliance, Intune device management, Conditional Access policies, Information Barriers, Customer Lockbox, individual file recycle bin, version history, audit logs, eDiscovery, export, legal hold, retention policies, sensitivity labels, and data loss prevention.
Read more admin details from Microsoft’s post. Note that at the time of writing this, they are still talking about Copilot Chat and not BizChat. Name changes do take time..
Upcoming Features (Q4 CY2024):
Retention labels at the file level.
Programmatic API access to content in SharePoint Embedded containers, enabling third-party governance, management, and compliance tools.
Guest/external access via Entra B2B configuration for tenants with sensitivity labels.
SharePoint Admin Center columns to identify user-owned containers.
Published by
I work, blog and speak about Future Work : AI, Microsoft 365, Copilot, Microsoft Mesh, Metaverse, and other services & platforms in the cloud connecting digital and physical and people together.
I have about 30 years of experience in IT business on multiple industries, domains, and roles.
View all posts by Vesa Nopanen