Copilot adds usage metrics

- GitHub now aggregates Copilot code review user counts into its usage metrics API for organisation and enterprise reports. - Copilot for Jira received enhancements, and Copilot analytics data export is in public preview in the Copilot dashboard. - The new exportable metrics and team-level reporting underline a move to manage AI features through instrumentation and governance ( ).

GitHub has started counting Copilot code review users in its usage metrics API, giving companies a new way to measure who is actually using the feature. (github.blog) The April 22 update adds six fields to 1-day and 28-day enterprise and organization reports: daily, weekly, and monthly counts for both active and passive Copilot code review users. GitHub said active users are people who manually request a review or apply a suggestion, while passive users are counted when reviews run automatically under repository or organization policy. (github.blog) GitHub rolled out the underlying user-level split earlier, on April 6, when it began marking whether a person’s Copilot code review activity was active or passive in daily and 28-day reports. In that release, GitHub said an active signal overrides a passive one if both happen in the same period. (github.blog) The change lands in a broader reporting push. GitHub’s Copilot usage metrics documentation says the API is meant to show adoption, activity, code generation, and pull request lifecycle trends across enterprises, organizations, and users, and GitHub now recommends that API for new integrations and analyses. (docs.github.com) GitHub has been widening those reports through April. On April 10, it added aggregated active-user counts for Copilot cloud agent, and on April 8 it added pull-request metrics for changes that were both reviewed by Copilot and later merged. (github.blog (github.blog) GitHub also updated Copilot for Jira on April 22. The Jira integration now lets teams pick custom agents from a GitHub repository, pull context from Atlassian custom fields such as acceptance criteria, follow branch-naming rules from tickets, and post review-request notifications back into Jira when Copilot opens a draft pull request. (github.blog) Microsoft is making a parallel move in Microsoft 365 Copilot. Its Copilot Dashboard export feature, now in public preview documentation, lets eligible tenants download de-identified, user-level weekly metrics covering the past six months for custom reporting and analysis. (learn.microsoft.com) Microsoft’s documentation says the export requires at least 50 Copilot or Viva Insights licenses and global access to the dashboard, and that the feature is on by default for eligible tenants and users. A Microsoft 365 Message Center post updated on March 25 said worldwide general availability is scheduled to begin in late April 2026 and finish by early May 2026. (learn.microsoft.com) (mc.merill.net) The common thread is that vendors are turning Copilot from a seat you assign into a system you can audit week by week, team by team, and workflow by workflow. The newest GitHub fields do not just show whether code review ran; they show whether people asked for it or whether policy turned it on for them. (github.blog) (learn.microsoft.com)

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.