diff --git a/data-explorer/includes/kusto-emulator-limitations.md b/data-explorer/includes/kusto-emulator-limitations.md
index 9736151bae..797dce05d9 100644
--- a/data-explorer/includes/kusto-emulator-limitations.md
+++ b/data-explorer/includes/kusto-emulator-limitations.md
@@ -1,7 +1,7 @@
 ---
 ms.service: azure
 ms.topic: include
-ms.date: 09/25/2025
+ms.date: 10/01/2025
 ---
 
 ## Limitations
@@ -18,7 +18,7 @@ In general, this offering isn't suited for production workloads.
   - Event Hubs
   - IoT Hub
   - Event Grid
-- No support for ingestion endpoints, including Kusto.Ingest SDKs
+- The dedicated ingestion endpoint (that is, `https://ingest-<YourClusterName><Region>.kusto.windows.net`) and the Kusto. Ingest APIs that depend on it aren't supported
 - Although ingested data can be stored externally to the container, we don't recommend persisting data for long periods of time for the following reasons:
   - There's no guarantee the [extent](/kusto/management/extents-overview?view=azure-data-explorer&preserve-view=true) format or the metadata format are compatible between versions of the Kusto emulator
   - Extents aren't [merged](/kusto/management/merge-policy?view=azure-data-explorer&preserve-view=true) and therefore can become fragmented as data get ingested