// AI Platform Drift

GitHub Copilot adds granular telemetry controls for identity and content capture

GitHub Copilot changelog · published 2026-10-13 14:15 UTC
WORTH KNOWING VERIFY_ONLY SECURITYAPI
WHAT CHANGEDGitHub Copilot now supports six independent telemetry capture settings in managed enterprise configurations: telemetry.capture.identity (adds user.name, process.user.name, host.name to OpenTelemetry data) and five content classes (prompts, responses, toolArguments, toolOutput, policyDetail). All six are off by default. Explicit managed settings override local configuration, SDK settings, and environment variables. The existing captureContent setting remains as a legacy shorthand for the five content classes but never enables identity capture.
WHY IT MATTERSIf your organization currently uses the captureContent setting for audit purposes, you are not collecting user attribution data — identity capture requires the new separate setting. Prompt, tool, and policy capture can include source code, file contents, workspace paths, and user-profile paths, so enabling the wrong class sends more data to your telemetry endpoint than you may have approved.
WHAT TO DOReview your current Copilot telemetry configuration against the six new capture classes. If you need user attribution for audit trails, explicitly enable telemetry.capture.identity in managed settings. If you are using captureContent, determine which of the five content classes you actually need and configure them individually, sending data only to approved collection endpoints.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Client telemetry user attribution and configurable capture
+https://github.blog/changelog/2026-10-12-client-telemetry-user-attribution-and-configurable-capture
+Mon, 12 Oct 2026 22:38:00 +0000
+
+Enterprise administrators can now use telemetry in managed settings to attribute GitHub Copilot activity to a user without collecting their prompts, responses, or tool content.
+The telemetry.capture.identity setting adds three attributes to OpenTelemetry (OTel) data:
+
+user.name: The authenticated Copilot account name, currently the GitHub login.
+process.user.name: The local operating-system account.
+host.name: The local machine name.
+
+Identity capture is off by default and remains separate from the existing pseudonymous user identifier. Fine-grained capture controls are available in Copilot CLI, the GitHub Copilot app, and VS Code sessions using Agent Host.
+Administrators can also independently control five additional capture classes:
+
+prompts: User, system, and developer prompts and supported input context.
+responses: Assistant responses and supported reasoning content.
+toolArguments: Raw tool arguments, commands, tool schemas, and identifiers for tools, MCP servers, plugins, and hooks.
+toolOutput: Tool results and execution-error details.
+policyDetail: Raw policy details such as sandbox filesystem paths.
+
+Every capture class is off by default. Explicit managed values take precedence over local settings, SDK configuration, and environment variables. The existing captureContent setting remains available as a legacy shorthand for the five content classes, but it never enables identity.
+Prompt, tool, and policy capture can include source code, file contents, commands, tool results, and workspace or user-profile paths. Enable only the classes required for your audit use case and send them to an approved collection endpoint.
+To learn more, see the enterprise managed settings reference and monitor agent usage with OpenTelemetry.
+Join the discussion within GitHub Community.
+
+The post Client telemetry user attribution and configurable capture appeared first on The GitHub Blog.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew telemetry configuration and data-capture controls materially affect what data is collected and how it is attributed in managed Copilot deployments.
signalsnew security/privacy feature: identity capture controls · new configuration options: telemetry.capture.identity and five capture classes · data handling change: prompts, responses, tool arguments, tool output, policy details now independently controllable · default-off security posture documented · enterprise administrator capability addition · future date: 2026-10-12
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)