From the source
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.
…
