From the source
GitHub's Copilot usage metrics API now flags which users are missing client telemetry or running IDE and extension versions below the usage metrics minimums.
- The change answers a reporting gap: users without client telemetry still count as active, but their reports lack detail such as lines of code, feature breakdowns, and model breakdowns.
- New per-user fields appear in enterprise and organization user reports, including client_telemetry_present, which is false when Copilot saw activity but no usage events arrived from the editor, and usage_metrics_requirements, which lists each IDE and Copilot extension as met, unmet or unknown.
- Daily affected-user counts appear in enterprise and organization reports: missing_client_telemetry_user_count and below_usage_metrics_minimum_user_count.
- GitHub lists outdated editors or extensions, disabled IDE telemetry, and proxies or firewalls that block events as common causes, and says the fields show how many users are affected and who to follow up with, so gaps can be closed without opening a support ticket.
- The fields are available to enterprise owners, enterprise billing managers, organization owners, and anyone with a custom role granting the View Copilot Metrics permission, with the Copilot usage metrics policy enabled.
- Each count covers a single day, a user can appear in both counts, and null or omitted values mean the data is unavailable rather than false or zero; days before this release have no values.
