Repo sync for protected branch

data-explorer/kusto/api/get-started/app-client-network-restrictions.md

@@ -5,7 +5,7 @@ ms.reviewer: yogilad
 ms.author: spelluru
 author: spelluru
 ms.topic: how-to
-ms.date: 11/16/2025
+ms.date: 12/01/2025
 ms.custom: 
 ---
 
@@ -35,9 +35,9 @@ This article gives step-by-step guidance on managing DNS restrictions in Kusto t
 
     :::image type="content" source="../../media/bypass-dns-restrictions/kusto-explorer-options.png" alt-text="Screenshot of the Options editor open with the Additional Trusted Hosts field highlighted.":::
 
-## Bypass DNS restrictions with Azure Data Explorer
+## Bypass DNS restrictions with Azure Data Explorer web UI
 
-1. Open Azure Data Explorer.
+1. Open [Azure Data Explorer](https://dataexplorer.azure.com/home).
 1. Select the *Settings* icon in the top-right corner.
 1. Select **Connection**.
 1. In **Additional trusted hosts**, add the fully qualified hostname or DNS suffix (preceded with an asterisk `*`) you want to work with. List multiple FQDNs or DNS suffixes by separating them with a semicolon `;`.
@@ -49,7 +49,7 @@ This article gives step-by-step guidance on managing DNS restrictions in Kusto t
 For command-line applications and tools, disable DNS validation entirely by passing a command-line argument or setting an environment variable.
 
 > [!NOTE]
-> Disabling DNS validation using environment variables affects all applications and tools using the C# SDK, including Kusto Explorer, Light Ingest, Kusto CLI, Perkus, and any third-party application developed with the C# Kusto SDK.
+> Disabling DNS validation using environment variables affects all applications and tools using the C# SDK, including Kusto Explorer, Light Ingest, Kusto CLI, and any third-party application developed with the C# Kusto SDK.
 
 To disable using a command-line argument, add the following argument to the tool's command line.
 

data-explorer/lightingest.md

@@ -3,11 +3,11 @@ title: Use LightIngest to ingest data into Azure Data Explorer
 description: Learn about LightIngest, a command-line utility for ad-hoc data ingestion into Azure Data Explorer.
 ms.reviewer: tzgitlin
 ms.topic: how-to
-ms.date: 11/03/2025
+ms.date: 11/18/2025
 ---
 
 # Use LightIngest to ingest data into Azure Data Explorer
- 
+
 [LightIngest](https://github.com/Azure/Kusto-Lightingest/blob/main/README.md) is a command-line utility for ad-hoc data ingestion into Azure Data Explorer. The utility can pull source data from a local folder, an Azure blob storage container, or an Amazon S3 bucket.
 
 LightIngest is most useful when you want to ingest a large amount of data, because there's no time constraint on ingestion duration. It's also useful when you want to later query records according to the time they were created, and not the time they were ingested.
@@ -20,13 +20,16 @@ For an example of how to autogenerate a LightIngest command, see [ingest histori
 
 * LightIngest. Get LightIngest in one of two ways:
   * [Download LightIngest binaries for your operating system](https://github.com/Azure/Kusto-Lightingest/releases). Make sure to unzip the binaries after download.
-  
+
   * [Install LightIngest as a .NET tool](https://www.nuget.org/packages/Microsoft.Azure.Kusto.LightIngest). This method requires that you have the .NET SDK version 6.0 or higher installed on your machine. Then, run the following command:
 
       ```
       dotnet tool install -g Microsoft.Azure.Kusto.LightIngest
       ```
 
+> [!NOTE]
+> Consider using the [queued ingestion commands](/kusto/management/data-ingestion/queued-ingestion-use-case?view=azure-data-explorer&preserve-view=true) as they do not require installing software.
+
 ## Run LightIngest
 
 To run LightIngest:
@@ -110,18 +113,18 @@ The argument values must include:
 > [!IMPORTANT]
 > When you specify that the creation time should be overridden, make sure the `Lookback` property in the target table's effective [Extents merge policy](/kusto/management/merge-policy?view=azure-data-explorer&preserve-view=true) aligns with the values in your file or blob paths.
 
-**Examples** 
+**Examples**
+
+* A blob name that contains the datetime as follows: `historicalvalues19840101.parquet` (the timestamp is four digits for the year, two digits for the month, and two digits for the day of month),
 
-* A blob name that contains the datetime as follows: `historicalvalues19840101.parquet` (the timestamp is four digits for the year, two digits for the month, and two digits for the day of month), 
-
     The value for `-creationTimePattern` argument is part of the filename: *"'historicalvalues'yyyyMMdd'.parquet'"*
 
     ```kusto
     LightIngest "https://ingest-{Cluster name and region}.kusto.windows.net;Fed=True" -db:{Database} -table:Trips -source:"https://{Account}.blob.core.windows.net/{ROOT_CONTAINER};{StorageAccountKey}" -creationTimePattern:"'historicalvalues'yyyyMMdd'.parquet'"
      -pattern:"*.parquet" -format:parquet -limit:2 -cr:10.0 -dontWait:true
     ```
 
-* For a blob URI that refers to hierarchical folder structure, like `https://storageaccount/mycontainer/myfolder/2002/12/01/blobname.extension`, 
+* For a blob URI that refers to hierarchical folder structure, like `https://storageaccount/mycontainer/myfolder/2002/12/01/blobname.extension`,
 
     The value for `-creationTimePattern` argument is part of the folder structure: *"'folder/'yyyy/MM/dd'/blob'"*
 
@@ -220,4 +223,3 @@ LightIngest performs three actions that can use managed identity for authenticat
 * **Connect to Azure Storage to download blobs**: Use "-ingestmi" to specify a managed identity installed on the Kusto service that has read privileges on the storage container.
 
 * **Connect to Azure Storage to list container blobs**: Use the "-storageMi" argument to specify a managed identity installed on the client VM that has list privileges on the storage container. If you use this method but not the previous one (connect to Azure storage to download blobs), the managed identity must have read privileges as well and a token is passed to the Kusto service to be used for the ingestion. Set all three arguments.
-