What is the correct way to provide feedback on Copilot preview features like Tasks? Too many overlapping channels with no clear guidance

For Copilot preview features, feedback is primarily handled through in-product mechanisms and a few specific support/developer channels. From the available information, the following applies:

1. Which channels are actually monitored by Copilot product teams?

• In-product feedback controls are explicitly monitored:
  • Thumbs up / thumbs down in Copilot chat panes (for example, in Excel, Teams, Viva Connections, and Copilot Pages) are reviewed by Microsoft to improve Copilot and prioritize updates.
    • Excel: “Share your feedback directly in Copilot by clicking the thumbs-up or thumbs-down icons in the chat pane. The product team reviews all feedback to help improve Copilot and set priorities for future updates.”
    • Viva Connections: Users can select thumbs up/down on Copilot-powered news summaries; this feedback is “directed to Microsoft for review and consideration.”
    • Teams chats: Thumbs up/down on Copilot messages is called out as a best practice for sharing satisfaction and verbatim comments.
    • Copilot Pages: In-product feedback is part of the Responsible AI pipeline so users can report offensive or problematic content.
• For extensibility and developer-related issues (for example, Copilot plugins, Teams integration, or Copilot extensibility samples), the product/engineering teams monitor:
  • GitHub issue trackers for Microsoft 365 Copilot extensibility docs and samples.
  • Microsoft Teams developer-related GitHub repos using the teams-developer-support tag.
• For Partner Center–related Copilot issues (environment setup, publishing, etc.), the Partner Center AI Assistant channel is the monitored path.

Other generic forums (Microsoft Q&A, general community forums, Windows Feedback Hub, etc.) may surface issues but are not identified in the provided material as primary, product-team-owned channels for Copilot feedback.

2. Recommended channel for preview features like Copilot Tasks

Based on the documented patterns across Copilot experiences, the recommended path for preview features is:

• Use the in-product feedback entry point associated with that Copilot experience:
  • Thumbs up/down in the Copilot response area (and add verbatim comments when prompted).
  • Any dedicated Feedback entry in the app hosting Copilot (for example, in Copilot Pages: Settings and more → Feedback; in Teams: header → three dots → Feedback → Report a Problem and select the appropriate Copilot category).

For developer or extensibility-related preview scenarios, use the appropriate GitHub repo issues (for example, Microsoft 365 Copilot extensibility samples or Teams developer repos) as documented.

3. What does the thumbs down button do?

• Thumbs up/down in Copilot is not just generic telemetry; it is explicitly described as feedback that is:
  • Reviewed by the product team (Excel Copilot).
  • Directed to Microsoft for review and consideration (Viva Connections Copilot summaries).
  • Used to share satisfaction plus verbatim comments (Teams Copilot in chats).
• In Copilot Pages, in-product feedback is part of a Responsible AI handling pipeline that allows users to report offensive or problematic content back to Microsoft.

While the internal tracking mechanics are not described, the documentation consistently treats these controls as actionable feedback channels that feed into product review and prioritization, not as anonymous, unstructured telemetry only.

4. Plans or guidance for a clear “How to give feedback” page

• For several Copilot experiences, there is already explicit “how to provide feedback” guidance embedded in the help/FAQ content:
  • Copilot in Excel: a dedicated FAQ section “How do I provide feedback on editing with Copilot in Excel?” describing the thumbs up/down path and admin escalation via Microsoft support channels.
  • Copilot in Viva Connections: FAQ section “How do I provide feedback on this feature?” describing thumbs up/down on summaries.
  • Copilot in Teams chats: “Providing Feedback” section with step-by-step instructions for using Teams’ Feedback → Report a Problem and the thumbs up/down controls.
  • Copilot Pages: FAQ section “Where can I provide feedback for Copilot Pages?” describing the Settings and more → Feedback entry.
• For Microsoft 365 Copilot extensibility, there is a consolidated “Support and feedback” page that lists the official developer support channels (GitHub issues for docs, samples, Teams libraries, Partner Center AI Assistant, and Power Platform community forums).

This shows an emerging pattern: each Copilot surface has its own documented “how to provide feedback” guidance, and there is a central extensibility feedback page for developer scenarios. For a specific preview feature like Copilot Tasks, the most reliable approach is to:

• Use the in-product thumbs up/down and any visible Feedback or Report a problem entry.
• For admin/tenant issues, escalate via standard Microsoft support channels as described for similar Copilot features (for example, Excel Copilot guidance for admins).
• For extensibility or integration issues, use the GitHub and Partner Center channels listed in the Copilot extensibility support and feedback documentation.

References:

• Support and feedback
• Frequently asked questions about editing with Copilot in Excel
• Copilot in Viva Connections FAQ
• Copilot in Teams Chats
• Frequently asked questions about Microsoft 365 Copilot Pages