Copilot BYOK and Custom-Model Usage Metrics Explained

GitHub announced on November 3, 2026 that Copilot usage reports now distinguish two bring-your-own-key paths. Local BYOK sends requests from Copilot CLI or the Copilot app to a developer’s provider key or local model. Enterprise custom models are configured by administrators and route through GitHub to the organization’s provider. The reporting change improves attribution; it does not make the paths technically or financially equivalent.

Local and enterprise routes expose different evidence

User reports can show used_local_byok and totals_by_local_byok, including session, request, prompt and token counts split by BYOK kind and surface. Aggregate reports add daily, weekly and monthly active local-BYOK user counts. Local models can include tools such as Ollama, Foundry Local, LM Studio and llama-server.

Enterprise custom-model entries use is_custom_enterprise_model within model totals. GitHub observes those requests server-side and covers clients beyond CLI and Copilot app. A model used both through Copilot hosting and as a custom model appears twice so routes stay distinct.

Local BYOK reporting is explicitly a lower bound

GitHub says local BYOK fields depend on client telemetry. Disabled or blocked telemetry can hide activity. Some local providers do not report token use, so token totals can undercount even when a request is visible. Local reporting also lacks model-name detail.

Enterprise custom-model counts avoid that client dependency because GitHub sees the routed request. However, unrecognized names can appear as unknown, and earlier days have no is_custom_enterprise_model backfill. Comparisons need route and availability notes.

Separating traffic is necessary but not sufficient for cost analysis

BYOK activity was already included in existing totals. The new fields identify subsets rather than adding absent requests, so organizations must not add the new figures to old totals. Reconcile Copilot usage with provider invoices, local infrastructure costs and staff operating time.

A local model may have no per-token charge while still consuming hardware and electricity. An enterprise model can share a name with a hosted model but have different retention or regional terms. Verify policy outside the usage API.

Canadian teams should map residency and authorization by route

Local inference can support data minimization, but the workflow may still contact GitHub, registries or telemetry endpoints. Enterprise custom models may route to an external provider region. Document every data path, administrator, credential owner and permitted repository class.

Use metrics to find unapproved routes and estimate coverage, not to assume compliance. Confirm provider logs, retention and Canadian contractual requirements directly. A missing local-BYOK event may mean missing telemetry rather than no use.

Sources and editorial method

We use the linked original statements and reports to distinguish documented facts from our analysis. Company announcements describe their authors’ plans and claims; they are not independent verification of future outcomes. This article is dated and will be revised if material evidence changes. Read our editorial standards and corrections process.

GitHub: BYOK and enterprise custom models in the Copilot usage API ↗ — Official November 3, 2026 changelog; routes, fields, telemetry limits, access and no historical backfill.