Update 8/11: We previously stated that monthly enterprise channel support was available for Microsoft 365 Copilot. As we continue to make frequent product updates and enhancements during the early access program, the time between updates in the Monthly Enterprise Channel limits Microsoft’s ability to deliver an optimal Copilot experience on desktop clients. In the future, early access program users must be on the current channel to receive Copilot updates as they become available. We look forward to support in the Monthly Business Channel in the future.

To use Copilot, your organization must meet some technical requirements and have some features enabled. Copilot users must have a Microsoft 365 E3 or E5 license and an Azure Active Directory account, which gives them access to Microsoft 365 applications and services that work with Copilot, including Word, Excel, PowerPoint, OneDrive, Outlook, Loop, and more. Once available to your organization, your users will need to be on the current Microsoft 365 applications channel to access Copilot on desktop clients.

In addition to some requirements, we share some recommendations that prepare your organization for a better experience with technology. Copilot services connect to connection points contained in the Microsoft 365 connection point taxonomy. As with all Microsoft 365 services, we recommend that customers align their network with Microsoft 365 network connectivity principles. This will help provide the best Copilot experience by minimizing latency and improving network Quality of Service (QoS) for critical network flows. Some Copilot experiences require a WebSocket connection from the device running the Microsoft 365 application to a Microsoft service. Therefore, WebSockets must be unblocked from user endpoints. Finally, to take advantage of cross-application intelligence experiences in Teams, you will need to enable add-ins through the Teams admin center.

For more information here