Summary
GitHub's Copilot impact dashboard now shows how many active users engaged with each key Copilot feature on at least two days in a 28-day window, broken out across code completion, agent edits, passive and active code review, Copilot cloud agent, Copilot CLI, and the Copilot app. The same breakdown is exposed through enterprise and organization report APIs.
What changed
The Copilot impact dashboard and the enterprise/organization report APIs gained a 28-day feature-engagement breakdown, counting active users who used each feature (code completion, agent edit, passive/active code review, Copilot cloud agent, Copilot CLI, Copilot app) on at least two days in the period; the metric is aggregate-only and not added to user-level reports.
Why it matters
As enterprises spend heavily on AI coding tools, leaders need to know which capabilities are actually adopted versus shelfware. Per-feature engagement data lets admins target enablement, justify spend, and steer investment toward the agentic features developers use, making Copilot governance a measurable adoption-management problem rather than a seat-count guess.
Evidence excerpt
The dashboard shows how many active users engaged with each included feature on at least two days during the 28-day period.