GitHub lets enterprises pin Copilot's OpenTelemetry endpoint

GitHub added a control on July 8 that lets an enterprise mandate where the Copilot Chat extension in VS Code and Copilot CLI send OpenTelemetry data, removing the need for individual developers to set OTEL_* environment variables.

Per the GitHub changelog, the setting is delivered through a telemetry block in the enterprise-managed settings, and a managed value takes precedence over environment variables and user settings.

Configurable Options

Four things are configurable in the block:

• The OTLP export endpoint and transport (otlp-http or otlp-grpc)
• The OTel service name and resource attributes
• Exporter headers such as an authentication token for the collector
• Whether prompt, response, and tool content is captured, with a separate flag for whether developers can change that

Delivery Channels

Delivery uses the channels documented on the same page:

• Native MDM (Windows Registry or macOS managed preferences)
• Server-managed settings from a signed-in GitHub account
• A file-based managed-settings.json

Where This Bites

The precedence rule is the point. If a platform team owns the collector and needs traces routed to it, this is exactly the switch they wanted. If a developer had their own OTLP endpoint pointed at a local sink, they will see the session start emitting somewhere else. The changelog does not describe a per-user override once a managed value is set.

Scoping Note

A scoping note is worth reading twice. The changelog states that managed exporter headers apply only to the Copilot Chat extension's OTLP exporter. The endpoint and transport policy still reach the CLI agent host, but the auth-token flow the changelog calls out is bound to the Chat surface. On-call teams standing up the collector should plan for that asymmetry before it lands as a surprise during triage.