The latest Copilot usage metrics API release introduces two new per‑user attributes—client_telemetry_present and usage_metrics_requirements—as well as daily aggregate counters for missing telemetry and version shortfalls. For teams that rely on Copilot data to understand developer activity, these signals surface gaps that previously required manual investigation or support tickets.
New per‑user telemetry and version fields
Each user entry in enterprise and organization reports now includes:
- client_telemetry_present: a boolean flag that is false when Copilot observed activity but did not receive any telemetry events from the editor.
- usage_metrics_requirements: a list describing the status of every IDE and Copilot extension the user runs, marked as met, unmet, or unknown against the minimum versions required for full metrics collection.
These fields appear in both 1‑day and 28‑day user reports, giving a granular view of who is missing data and why.
Daily aggregate counts and reporting scope
Two new counters are added to the 1‑day enterprise and organization reports and to each day_totals entry of 28‑day reports:
- missing_client_telemetry_user_count: number of users without telemetry for that day.
- below_usage_metrics_minimum_user_count: number of users whose IDE or extension version falls below the required baseline.
Both counters are independent; a single user can be counted in both categories. Counts are not cumulative across days, so they must be interpreted as per‑day snapshots rather than unique user totals.
Operational considerations
From an implementation standpoint, the new signals highlight three practical areas to monitor:
- IDE telemetry configuration: Ensure that telemetry settings in supported editors are enabled and that network paths allow outbound events. Proxies or firewalls that block these events will cause
client_telemetry_presentto be false even when versions are up‑to‑date. - Extension and IDE version hygiene: Establish a process to keep Copilot extensions and supported IDEs at or above the documented minimums. The
usage_metrics_requirementslist makes it possible to target specific users for updates. - Data completeness handling: Treat null or omitted values as unavailable data rather than zero. When analyzing trends, factor in days before the release that lack these fields.
Access to these fields is limited to enterprise owners, billing managers, organization owners, or custom roles granted the View Copilot Metrics permission, and the Copilot usage metrics policy must be enabled.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
Teams should add the new per‑user flags and daily counters to their monitoring dashboards, set alerts for rising missing_client_telemetry_user_count or below_usage_metrics_minimum_user_count, and create remediation workflows that verify telemetry settings and push extension updates. By treating these metrics as early‑warning signals, you can maintain accurate usage reporting without escalating to support.
