Check your environment:
1、Network requirements：
Copilot experiences are deeply integrated with Microsoft 365 applications and often use the same network connections and endpoints that Microsoft 365 apps use. As such, baseline network configuration customers should ensure that Microsoft 365 endpoints are not blocked within their environment and that network setup follows Microsoft 365 network connectivity principles and best practices.
In addition to standard Microsoft 365 domains and IPs, there are some extra network endpoints (domains) that Copilot scenarios may need to connect to enable richer integrations (such as Copilot experiences for the Web). Customers should ensure that traffic to these domains is also not blocked by their network solutions:
copilot.microsoft.com, *.copilot.microsoft.com
*.bing.com, *.bingapis.com
challenges.cloudflare.com
https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worl...Microsoft recommends that customers verify that their network supports full WSS connectivity (including addressing the issues above) from user devices running Microsoft 365 applications to the following domains:
Microsoft 365 Copilot experiences (Enterprise): *.cloud.microsoft, *.office.com
Additional Copilot experiences (including Consumer): *.bing.com, copilot.microsoft.com, *.copilot.microsoft.com
2、Privacy settings for Microsoft 365 Apps:
Review your privacy settings for Microsoft 365 Apps because those settings might have an effect on the availability of Microsoft Copilot for Microsoft 365 features
If you turn off connected experiences that analyze content for Microsoft 365 Apps on Windows or Mac devices in your organization, Microsoft Copilot for Microsoft 365 features won’t be available to your users in the following apps:Excel/PowerPoint/OneNote/Word
https://learn.microsoft.com/en-us/deployoffice/privacy/manage-privacy-controlshttps://learn.microsoft.com/en-us/deployoffice/privacy/mac-privacy-preferences
