Copilot usage metrics reports now draw on server-side telemetry in addition to client signals, so more of your active Copilot users show up in reports. Enterprise usage reports returned by the Copilot usage metrics API now surface active users that client-side telemetry alone would have missed, giving you a more complete and consistent picture of who is using Copilot.
What’s new
Copilot usage reports have historically been built from client-side telemetry emitted by IDEs and other clients. That telemetry is the richest source we have, but it does not always reach us. Network conditions, proxy configurations, client settings, and other factors outside of your control or ours can prevent a client from reporting activity. When that happened, an active, billed user could be absent from your reports.
This update incorporates additional server-side telemetry to identify active users. Any active user we can confirm from the server side who was not already captured from client telemetry is now included in your enterprise single-day and 28-day reports, increasing your daily active user (DAU) coverage.
These newly surfaced users are fully identified and counted toward your active user totals. What server-side telemetry does not yet carry is the rich, per-interaction detail that client telemetry provides (i.e., the specific IDE, feature, model, and lines-of-code activity). So for these users, the high-level counts go up while the detailed breakdowns stay empty until richer telemetry is available for them.
