diff --git a/docs/reference/compatibility/features.md b/docs/reference/compatibility/features.md
index 907074bb..dedd0fd5 100644
--- a/docs/reference/compatibility/features.md
+++ b/docs/reference/compatibility/features.md
@@ -39,7 +39,7 @@ The following table shows Elastic features and their level of support and compat
 | Usage of [Time Series Data Streams]                         | [Compatible]     | [Supported]      |
 | **Central Management**                                      | [Incompatible]   | [Not supported]  |
 | Central management of OTel collectors                       | [Incompatible]   | [Not supported]  |
-| Central management of OTel SDKs                             | [Compatible]     | [Supported]      |
+| Central management of OTel SDKs                             | [Compatible]^5^  | [Supported]^5^   |
 
 
 ^1^ Refer to [limitations on host metrics](limitations.md#infrastructure-and-host-metrics)
@@ -50,6 +50,8 @@ The following table shows Elastic features and their level of support and compat
 
 ^4^ While ingesting traces that have been sampled using TBS is technically possible, there are important limitations to consider. Refer to [Tail-based sampling (TBS) limitations](../compatibility/limitations.md#tail-based-sampling-tbs) for more information.
 
+^5^ Available as Technical Preview on {{stack}} 9.1+. Not available on {{serverless-full}}.
+
 [Incompatible]: nomenclature.md
 [Compatible]: nomenclature.md
 [Not supported]: nomenclature.md
diff --git a/docs/reference/compatibility/limitations.md b/docs/reference/compatibility/limitations.md
index 33f4848c..5cd6d661 100644
--- a/docs/reference/compatibility/limitations.md
+++ b/docs/reference/compatibility/limitations.md
@@ -22,7 +22,7 @@ While {{edot}} and OTel-native data collection already covers most of the core O
 
 {{edot}} already supports most core observability use cases, but in some scenarios, you may prefer to use classic Elastic ingestion components, such as {{agent}} ({{product.fleet}}-managed), {{product.apm-agent}} or {{product.apm-server}}:
 
-* **Real user monitoring (RUM):** RUM ingestion and visualizations are not yet available for OTel-native data.
+* **Real user monitoring (RUM):** [EDOT Browser](elastic-otel-rum-js://reference/edot-browser/index.md) is available as Technical Preview for OTel-native browser instrumentation. For production RUM, continue using the classic Elastic {{product.apm}} [browser agent](apm-agent-rum-js://reference/index.md).
 * **Universal profiling:** This capability is currently only supported in the classic stack.
 * **Existing integrations and dashboards:** Many prebuilt Elastic integrations and dashboards are designed for ECS-formatted data and may not work as expected with the OpenTelemetry semantic conventions without customization.
 * **Managed processing of logs:** Elastic doesn't provide curated, centralized {{es}} ingest pipelines for OTel-native data. Process logs in the Collector instead, or define your own ingest pipeline. Refer to [Centralized parsing and processing of data](#centralized-parsing-and-processing-of-data) for more information.