MC920307 - Copilot Pages coming to Microsoft Copilot

As communicated in MC862983, Microsoft Copilot with enterprise data protection is available to users who sign in with an Entra account. Starting early November 2024, Copilot Pages will become available for Microsoft Copilot users when signed in with an Entra account. This feature was previously only available for users with a paid Microsoft 365 Copilot license. Pages will be enabled by default and admin controls are available should you need to control the experience differently within your tenant.

Note: In September 2024, Pages started to roll out for Microsoft 365 Copilot users in Work mode of Business Chat (MC890882). This update will also roll out Pages to Web mode in Business Chat for Microsoft 365 Copilot users.

Note: Copilot Pages will only be available in Microsoft Copilot for users signed in with an Entra account who have an underlying SharePoint license.

When this will happen:

General Availability (Worldwide): We will begin rolling out Copilot Pages in early November 2024 and expect to complete by late November 2024.

How this will affect your organization:

Recently, we announced Copilot Pages, a first step in our new design system for knowledge work. Copilot Pages is a dynamic, persistent canvas in Copilot chat designed for multi-player collaboration. With Copilot Pages, you can turn insightful Copilot responses into something durable with a side-by-side page that you can view and edit and, when ready, share with your team to collaborate.

In a multiplayer approach, you can work together as a team to learn from each other’s prompts, and organize complex information. We see collaboration using Copilot Pages as the next great step forward in evolving Copilot from an individual, point-in-time exercise into a collaborative experience.

You can return to a page at any time by clicking the link in chat or the Open Page icon at the top of the associated Copilot session. Additionally, users can view all their pages in the Pages module in Microsoft365.com where they can also collaborate with others.

Created pages are stored in a user-owned SharePoint Embedded container. The container is lifetime-managed with the user account, so like OneDrive, the container and its content are deleted when the user account is deleted.

What you need to do to prepare:

The feature will be automatically enabled when it rolls out unless you’ve used the following controls to manage the experience. If you wish to change the configuration of the feature, there are two ways to consider based on your needs.

You can use a Cloud Policy setting to prevent users from creating new Copilot pages in Microsoft Copilot, and/or use Conditional Access or Information Barriers policies to block certain users from accessing Copilot pages as needed.

Note: The controls for Copilot pages are the same for both free Microsoft Copilot (when signed in with an Entra account) and the paid Microsoft 365 Copilot license.

More information can be found here: Copilot pages for IT Admins - Sep 2024 update

Instructions for using the Cloud Policy to enable/disable Copilot pages in your tenant repeated here for ready reference:

1. Sign in to https://config.office.com/ with your Microsoft 365 admin credentials.
2. Select Customization from the left pane.
3. Select Policy Management.
4. Create a new policy configuration or edit an existing one.
5. From the Choose the scope dropdown list, choose either All users or select the group for which you want to apply the policy. For more information, See Microsoft 365 Groups for Cloud Policy.
6. In Configure Settings, choose this setting:
   1. For Create and view Loop files in Microsoft 365 Copilot Chat:
      1. Enabled: Copilot chat experience is available to the users.
      2. Disabled: Copilot chat experience isn't available to the users.
      3. Not configured: Copilot chat experience is available to the users.
7. Save the policy configuration.
8. Reassign priority for any security group, if required. (If two or more policy configurations are applicable to the same set of users, the one with the higher priority is applied.)

In case you create a new policy configuration or change the configuration for an existing policy, there can be a delay in the change being reflected as described below:

• If there were existing policy configurations prior to the change, then it may take 90 minutes for the change to be reflected.
• If there were no policy configurations prior to the change, then it may take 24 hours for the change to be reflected.