From 3b1509dc4f188ccf3a96519254d5245943d6db80 Mon Sep 17 00:00:00 2001 From: hkirschner_microsoft Date: Wed, 26 Aug 2026 20:31:26 -0700 Subject: [PATCH] Clarify managed telemetry protocol Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- docs/enterprise/ai-settings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/enterprise/ai-settings.md b/docs/enterprise/ai-settings.md index 7c2dc7388b..72e61970b9 100644 --- a/docs/enterprise/ai-settings.md +++ b/docs/enterprise/ai-settings.md @@ -462,7 +462,7 @@ Deliver these settings through the `telemetry` block in [Copilot managed setting |---------------------|---------|-------------| | `telemetry.enabled` | `setting(chat.agentHost.otel.enabled)` | Enable or disable Copilot OpenTelemetry export. When managed, users cannot override the value. | | `telemetry.endpoint` | `setting(chat.agentHost.otel.otlpEndpoint)` | OTLP collector endpoint that receives the telemetry. | -| `telemetry.protocol` | `setting(chat.agentHost.otel.exporterType)` | OTLP transport, such as `otlp-http` or `otlp-grpc`. The managed wire protocol (protobuf or JSON) is applied to both surfaces. | +| `telemetry.protocol` | `setting(chat.agentHost.otel.exporterType)` | OTLP wire protocol. Use `http/json` or `http/protobuf`; both select the `otlp-http` exporter. `grpc` is accepted for forward compatibility but currently falls back to the HTTP default. | | `telemetry.captureContent` | `setting(chat.agentHost.otel.captureContent)` | Whether export captures prompt, response, and tool content. | | `telemetry.lockCaptureContent` | — | Prevents developers from overriding the managed `captureContent` value. | | `telemetry.serviceName` | `setting(chat.agentHost.otel.serviceName)` | The OTel `service.name` resource attribute. |