Repo sync for protected branch

data-explorer/includes/kusto-emulator-limitations.md

@@ -1,7 +1,7 @@
 ---
 ms.service: azure
 ms.topic: include
-ms.date: 10/01/2025
+ms.date: 12/11/2025
 ---
 
 ## Limitations
@@ -14,10 +14,12 @@ In general, this offering isn't suited for production workloads.
   - Access control
   - Encrypted connections; connection is through an HTTP connection
   - Encryption at rest
-- No managed pipelines, including:  
+- No managed ingestion pipelines, including:  
   - Event Hubs
   - IoT Hub
   - Event Grid
+  - Cosmos DB
+- No streaming ingestion
 - 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

data-explorer/kusto-emulator-overview.md

@@ -3,7 +3,7 @@ title: Azure Data Explorer Kusto emulator overview
 description: In this article, you learn about the Azure Data Explorer Kusto emulator.
 ms.reviewer: vplauzon
 ms.topic: conceptual
-ms.date: 09/30/2025
+ms.date: 12/11/2025
 ---
 # Azure Data Explorer Kusto emulator
 
@@ -23,7 +23,7 @@ The emulator is available as a *Linux* Docker container image. It exposes a quer
 
 The emulator supports all commands and queries within its [architecture limitations](#limitations). For instance, [Row Level Security policy commands](/kusto/management/row-level-security-policy?view=azure-data-explorer&preserve-view=true) are supported but since there's no authentication in the emulator, they aren't useful.
 
-The emulator doesn't include the [data management service](ingest-data-overview.md) and hence doesn't support queued (managed) ingestion. However, you can ingest data using [ingestion commands](/kusto/management/data-ingestion/ingest-from-query?view=azure-data-explorer&preserve-view=true) or [streaming ingestion] (ingest-data-streaming.md). Data can be ingested from local files, [external tables](/kusto/query/schema-entities/external-tables?view=azure-data-explorer&preserve-view=true), or [external data](/kusto/query/externaldata-operator?pivots=azuredataexplorer?view=azure-data-explorer&preserve-view=true). By default, ingested data is persisted on the disk within the container; hence, the data is as transient as the container itself. If you want to retain the data, you can persist it outside the container by mounting a volume on the container and persisting the data to the volume.
+The emulator doesn't include the [data management service](ingest-data-overview.md) and hence doesn't support queued (managed) ingestion. However, you can ingest data using [ingestion commands](/kusto/management/data-ingestion/ingest-from-query?view=azure-data-explorer&preserve-view=true). Data can be ingested from local files, [external tables](/kusto/query/schema-entities/external-tables?view=azure-data-explorer&preserve-view=true), or [external data](/kusto/query/externaldata-operator?pivots=azuredataexplorer?view=azure-data-explorer&preserve-view=true). By default, ingested data is persisted on the disk within the container; hence, the data is as transient as the container itself. If you want to retain the data, you can persist it outside the container by mounting a volume on the container and persisting the data to the volume.
 
 ## Kusto emulator scenarios