
There isn’t a supported way today to directly automate reports from the reaction (thumbs up/down) details themselves.
Those reactions are captured for built‑in analytics, but they’re not currently exposed via a stable API or connector. That’s why a Power Automate “UI‑driven” approach feels brittle and you’re right to avoid it.
What does work in practice:
Use built‑in analytics for high‑level reporting : If all you need is trends (positive vs negative, volume over time), the Analytics/Evaluation views are the supported path. You can export summaries, but not the raw reaction events in an automated way.
Implement a custom feedback loop (most reliable option) : This is what most teams end up doing. When a user gives a negative reaction (or even proactively), prompt for structured feedback and store it in Dataverse, SQL, or App Insights. That gives you full control and makes reporting trivial.
If this is a Bot Framework / custom channel scenario : Logging reactions into Application Insights (or your own telemetry store) is the cleanest approach. You can then build dashboards or scheduled reports without depending on the Copilot UI.
At the moment, reactions are best treated as signal for in‑product analytics, not as a reporting data source.
If you need automation, a custom feedback capture is the least fragile and most future‑proof solution.
If Microsoft exposes reaction events via Dataverse or an API later, this will get easier but today, you’re not missing anything obvious.