Simplifying Microsoft 365 Copilot app web experiences

Based on your feedback, we’re simplifying how users access Copilot Chat on the web by consolidating entry points.  Today, users without chat pinned in the Microsoft 365 Copilot app access Copilot Chat in a standalone experience on copilot.cloud.microsoft, while users with chat pinned access Copilot Chat on m365.cloud.microsoft. To simplify and improve the Microsoft 365 Copilot Chat experience, we’re consolidating the chat functionality into the Microsoft 365 Copilot app. Having two separate entry points has created customer confusion and extra effort for our customers. By unifying the experience, we’re making it easier to access the full value of Copilot in one place. Below is the new experience on m365.cloud.microsoft for users without chat pinned in the Microsoft 365 Copilot app who visit Microsoft 365 Copilot app via a direct chat link (m365.cloud.microsoft/chat). Users with pinning disabled will continue to see chat unpinned by default on m365.cloud.microsoft, on mobile, and on desktop. Users who continue to navigate to copilot.cloud.microsoft will automatically be redirected to the below chat experience on m365.cloud.microsoft/chat. If users come to chat via a direct link (m365.cloud.microsoft/chat) they will see chat in a transient state in their navigation. If a user navigates away from chat, it will disappear from the navigation unless the user chooses to pin it.   Below is the default experience on m365.cloud.microsoft for users with chat pinned in the Microsoft 365 Copilot app. No change to the end users’ experience. There is no change for users with a Microsoft 365 Copilot license and no change for users whose access to Copilot has been blocked in Integrated Apps. Users with bookmarks or favorites saved to copilot.cloud.microsoft will be redirected to m365.cloud.microsoft/chat automatically. How this will affect your organization: Users who previously landed on copilot.cloud.microsoft for chat access will now be automatically directed to m365.cloud.microsoft/chat for chat access. There is no change for users who do not have access to Copilot. There is no change for users who already access Copilot Chat via the Microsoft 365 Copilot app. When this will happen: The rollout begins with 301 traffic redirections in mid-September. The copilot.cloud.microsoft will be deprecated at the end of September. Users with bookmarks or favorites saved to copilot.cloud.microsoft or who navigate directly to copilot.cloud.microsoft will be redirected to m365.cloud.microsoft/chat automatically going forward. What you need to do to prepare: No admin action is required. If you would like to inform users of this update, you could consider the following message: “Copilot Chat is now available in the Microsoft 365 Copilot app. This change simplifies access and ensures a consistent experience across Microsoft 365 Copilot app web entry points.” To learn more about your options for managing Microsoft 365 Copilot Chat, see Manage Microsoft 365 Copilot Chat | Microsoft Learn. Compliance considerations: Does the change alter how existing customer data is processed, stored, or accessed? No. Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to customer data? No. Does the change provide a new way of communicating between users, tenants, or subscriptions? No. Does the change provide end users any new way of interacting with generative AI? No – it improves access to existing capabilities