GitHub separates BYOK usage in Copilot metrics, with telemetry limits
GitHub announced on November 3 that the Copilot usage metrics API now distinguishes bring-your-own-key activity from Copilot-hosted model usage. The reports cover developer-configured local BYOK and administrator-configured enterprise custom models, which use different request paths.
Local BYOK requests go from Copilot CLI or the Copilot app directly to a developer's provider key or local model. Reports include a used_local_byok flag, totals_by_local_byok breakdowns and daily, weekly and monthly active-user counts. Local BYOK usage is not broken out by model name.
Enterprise custom models are configured in GitHub settings and route requests through GitHub to the organization's provider. The is_custom_enterprise_model field identifies them in model totals. A model used both through Copilot hosting and as a custom model appears as separate entries.
The distinction matters for teams checking BYOK policy and understanding costs, but it does not add new usage to existing totals. Local BYOK is already a subset of the CLI and Copilot app totals, and custom-model usage is already included in client totals. Adding the subsets again would double count.
Local BYOK figures are a lower bound because they rely on client telemetry and undercount when telemetry is disabled. Token counts can also undercount when a local provider does not report them. GitHub says server-observed enterprise custom-model counts do not have that limitation, although unrecognized model names still appear as unknown.
The fields appear in enterprise and organization reports at user and aggregate levels, across one-day and 28-day reports. Access requires the relevant owner, billing-manager or custom metrics permission, and the Copilot usage metrics policy must be enabled. Report days before this release do not gain the new custom-model flag through backfill.