// AI Platform Drift

GitHub Copilot usage metrics API adds telemetry and version gap fields

GitHub Copilot changelog · published 2026-11-11 19:37 UTC
WORTH KNOWING VERIFY_ONLY API
WHAT CHANGEDThe Copilot usage metrics API added four new fields effective 5 November 2026. Per-user fields client_telemetry_present (boolean) and usage_metrics_requirements (IDE/extension version status) now appear in enterprise and organization user reports. Aggregate counts missing_client_telemetry_user_count and below_usage_metrics_minimum_user_count now appear in daily reports and 28-day day_totals entries. Null or omitted values mean data unavailable, not false or zero.
WHY IT MATTERSUsers without client telemetry count as active but produce incomplete reports—no lines-of-code counts, no feature breakdowns, no model breakdowns. These fields identify which users are affected and whether the cause is outdated tooling or blocked telemetry, so you can close reporting gaps without opening support tickets. Users can appear in both counts on the same day; adding counts across days or combining the two counts produces incorrect totals.
WHAT TO DOQuery the usage metrics API for your enterprise or organization. Check missing_client_telemetry_user_count and below_usage_metrics_minimum_user_count in recent daily reports. For users with client_telemetry_present false or unmet usage_metrics_requirements, verify their IDE and extension versions against the minimums in the API documentation and check whether proxies or firewalls block telemetry events.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Usage metrics API flags telemetry and version gaps
+https://github.blog/changelog/2026-11-05-usage-metrics-api-flags-telemetry-and-version-gaps
+Fri, 06 Nov 2026 00:08:31 +0000
+
+The Copilot usage metrics API now shows which users are missing client telemetry or are running IDE or extension versions below the usage metrics minimums. New per-user fields appear in enterprise and organization user reports, and daily affected-user counts appear in enterprise and organization reports.
+What’s new
+
+client_telemetry_present: Whether client telemetry was received for the user that day. false means Copilot saw the user’s activity, but no usage events arrived from their editor.
+usage_metrics_requirements: Lists each of the user’s IDEs and Copilot extensions as met, unmet, or unknown against the minimum supported versions.
+missing_client_telemetry_user_count: The number of users that day with client_telemetry_present set to false.
+below_usage_metrics_minimum_user_count: The number of users that day with at least one IDE or extension below the minimum version.
+
+Why this 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. These fields show how many users are affected and who to follow up with. This way you can close gaps without opening a support ticket.
+Important notes
+
+Scope: User fields appear in enterprise and organization user reports (1-day and 28-day). Counts appear in enterprise and organization 1-day reports and in each day_totals entry of 28-day reports.
+Access: These fields are available to enterprise owners, enterprise billing managers, organization owners, and anyone with a custom organization or enterprise role that grants the View Copilot Metrics permission. The Copilot usage metrics policy must be enabled.
+Daily counts: Each count covers a single day. A user can be counted in both missing_client_telemetry_user_count and below_usage_metrics_minimum_user_count, so don’t add the two counts together. Don’t add counts across days to count unique users.
+Independent signals: A user can meet every version minimum and still be missing telemetry (e.g., they’re behind a proxy).
+Unavailable values: Null or omitted values mean the data is unavailable, not false or zero. Days before this release have no values.
+
+Visit the Copilot usage metrics API documentation to get started.
+
+The post Usage metrics API flags telemetry and version gaps appeared first on The GitHub Blog.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew API fields and reporting capabilities change what data engineering teams can retrieve and how they must interpret results.
signalsnew API fields added to usage metrics endpoint · new per-user reporting fields in enterprise and organization reports · new aggregate counts in daily and 28-day reports · changes to what data is available and how to interpret it · permission scope clarified for access to new fields · breaking interpretation note: null/omitted values mean unavailable, not false/zero
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)