The latest update to the Copilot impact dashboard adds two previously untracked experiences—Copilot Chat and the VS Code Agents window—to the agent adoption chart, increasing the count of monitored features to nine. At the same time, the cohort formerly labeled “Passive users” is now called “Chat‑first users”, reflecting its actual usage pattern. Practitioners need to understand these changes because they affect how usage data is interpreted for capacity planning, adoption analysis, and reporting.
Copilot usage metrics: new feature coverage
The adoption chart now includes entries for chat and vscode_agent. These are treated like the existing seven features: a user is considered engaged with a feature when they have used it on at least two separate days within a 28‑day window, and a single user can be counted for multiple features. The renamed “Chat‑first users” cohort groups developers who are active in Copilot but have not met the two‑day threshold for any qualifying feature, meaning they remain outside the formal adoption phases.
Impact on adoption phase reporting
Although the new features appear in the feature‑engagement totals, they do not contribute to the adoption‑phase calculations. The adoption phases themselves remain unchanged, and the API still reports “Chat‑first users” under the generic No Cohort value. Cohort sizes are therefore identical to prior releases.
Operational considerations
Reporting for the added features is limited to enterprise and organization 28‑day reports; historical reports generated before this change continue to show only the original seven features. Access to the expanded data set requires the View Copilot Metrics permission, which is granted to enterprise owners, billing managers, organization owners, and any custom role that includes this permission. Additionally, the Copilot usage metrics policy must be enabled for the data to be visible.
Related CloudNinjas coverage: AI engineering.
What This Means For Practitioners
- Update any internal dashboards or alerting logic to ingest the new
chatandvscode_agentfields. - Re‑evaluate adoption‑phase analyses to remember that these features do not affect phase counts.
- Verify that the required permissions and the usage‑metrics policy are in place for the teams that need visibility.
- Monitor metric trends after deployment to detect any shifts in developer behavior that could influence capacity or licensing decisions.
- Stay alert for future updates that might alter how feature engagement maps to adoption phases.
