GitHub Copilot usage metrics API now flags telemetry and version gaps

GitHub has updated the Copilot usage metrics API to flag two kinds of reporting gaps: users who are missing client telemetry, and users running IDE or extension versions below the usage metrics minimums. The new per-user fields appear in enterprise and organization user reports for both 1-day and 28-day periods. Daily affected-user counts appear in enterprise and organization 1-day reports and in each day_totals entry of 28-day reports.

The per-user field client_telemetry_present shows whether client telemetry was received for a user on a given day. A value of false means Copilot saw the user’s activity, but no usage events arrived from their editor. The usage_metrics_requirements field lists each IDE and Copilot extension as met, unmet, or unknown against the minimum supported versions. Each count covers a single day, and a user can appear in both missing_client_telemetry_user_count and below_usage_metrics_minimum_user_count, so the two counts should not be added together.

Why it matters

Users without client telemetry still count as active, but their reports lack detail such as lines of code, feature breakdowns, and model breakdowns. Common causes include outdated editors or extensions, disabled IDE telemetry, and proxies or firewalls that block events. A user can meet every version minimum and still be missing telemetry, so admins need to check the two signals separately.

What to do

Use the daily counts to see how many users are affected, then review the per-user fields to identify who to follow up with. Start with outdated IDEs and extensions, then check telemetry settings and proxies or firewalls for users who still show false. Confirm the Copilot usage metrics policy is enabled, and check the vendor’s site for current minimum versions, which this post does not list.