diff --git a/docs/concepts/otlp/sentry-with-otel.mdx b/docs/concepts/otlp/sentry-with-otel.mdx
index cc6619664a831..8f072db128695 100644
--- a/docs/concepts/otlp/sentry-with-otel.mdx
+++ b/docs/concepts/otlp/sentry-with-otel.mdx
@@ -68,6 +68,10 @@ The following SDKs support the `propagateTraceparent` option:
-
-
+ ### .NET
+
+ -
+
diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx
index 7fd7f2e92c5f8..80d9ef70819d3 100644
--- a/docs/platforms/dotnet/common/configuration/options.mdx
+++ b/docs/platforms/dotnet/common/configuration/options.mdx
@@ -345,3 +345,13 @@ Disables the `SentryHttpMessageHandler`, which normally instruments outgoing HTT
This option was added in SDK version 5.1.0.
+
+
+
+If set to `true`, the SDK adds the [W3C `traceparent` header](https://www.w3.org/TR/trace-context/) to outgoing HTTP requests, in addition to the `sentry-trace` and `baggage` headers. Enable this when your backend services are instrumented with a W3C Trace Context compatible library, such as OpenTelemetry, and you want to continue the trace from the client.
+
+The `traceparent` header is only attached to requests whose URLs match `TracePropagationTargets`.
+
+This option was added in SDK version 6.0.0.
+
+