Copilot’s telemetry flags make missing usage data a reporting decision

What Changed

The client_telemetry_present field can flag active users whose editor usage events did not arrive. usage_metrics_requirements reports version status. GitHub says missing telemetry can remove feature, model and code detail even while users remain counted as active. [1]

Why It Matters

Analysis Imagine two departments with similar active-user totals but very different detailed usage. Before treating that difference as adoption quality, check whether the same fraction of each department is observable. A network configuration or client-version difference could change the measurement population. That makes coverage part of the report, alongside the usage result.

A practical dashboard should show a coverage note beside its conclusions and assign follow-up to the relevant administrator. That creates a way to distinguish a measurement repair from a training intervention. It also gives leadership a clearer explanation when detailed usage changes after a client update without a corresponding change in business output.

Evidence & Uncertainty

GitHub says the two daily affected-user counts can overlap: do not add them or sum daily counts into unique users. Null or omitted values indicate unavailable data, not zero. Meeting version minimums does not guarantee telemetry arrives. BriefSpire has not tested the API. [1]