Repo sync for protected branch

data-explorer/kusto/api/connection-strings/sql-connection-strings.md

@@ -27,9 +27,12 @@ Regardless of the authentication method used, the principal must have the necess
 
 The following table shows the supported authentication methods for each type of database acting as the source for the external table.
 
+::: moniker range="azure-data-explorer"
 > [!NOTE]
 > Where possible, the preferred authentication method is managed identity.
 
+::: moniker-end
+
 ::: moniker range="microsoft-fabric"
 
 | Authentication method | SQL Server | PostgreSQL | MySQL | Cosmos DB |

data-explorer/kusto/management/data-ingestion/cancel-queued-ingestion-operation-command.md

@@ -50,6 +50,9 @@ You must have at least [Table Ingestor](../../access-control/role-based-access-c
 |Database | `string` |The database where the ingestion process is occurring.|
 |Table | `string` | The table where the ingestion process is occurring.|
 
+>[!NOTE]
+>  If the ingestion operation was initiated with tracking disabled, cancellation commands execute on a best‑effort basis. The returned state may indicate: "Cancellation request received – service will attempt best effort cancellation (tracking isn't enabled on operation)"
+
 ## Example
 
 The following example cancels the ingestion of operation `00001111;11112222;00001111-aaaa-2222-bbbb-3333cccc4444`.

data-explorer/kusto/management/data-ingestion/ingest-from-storage-queued.md

@@ -51,6 +51,7 @@ The result of the command is a table with one row and one column.
 | IngestionOperationId | `string` | A unique ID used to track the set of blobs, whether or not tracking is enabled. |
 | ClientRequestId | `string` | The client request ID of the command. |
 | OperationInfo | `string` | Displays the command to run to retrieve the current status of the operation. |
+| CancelationInfo | `string` | Displays the command to run to cancel the operation. |
 
 >[!NOTE]
 > This command doesn't modify the schema of the target table. If necessary, the data is converted to fit the table's schema during ingestion. Extra columns are ignored and missing columns are treated as null values.

data-explorer/kusto/management/data-ingestion/queued-ingestion-use-case.md

@@ -77,6 +77,8 @@ with (format='parquet')
 
 The `OperationInfo`, which includes the `IngestionOperationId`, is then used to [track the ingestion status](#track-ingestion-status).
 
+The `CancelationInfo`, which includes the `IngestionOperationId`, is then used to [cancel the ingestion operation](#cancel-ingestion).
+
 ### Track ingestion status
 
 You run the `.show queued ingestion operations` command to check whether the ingestion is complete or if there are any errors.
@@ -169,9 +171,9 @@ with (format='parquet')
 
 **Output**
 
-| IngestionOperationId | ClientRequestId | OperationInfo |
-|----------------------|-----------------|---------------|
-|22223333;22223333;11110000-bbbb-2222-cccc-4444dddd5555|Kusto.Web.KWE,Query;22223333;22223333;33334444-dddd-4444-eeee-5555eeee5555|.show queued ingestion operations "22223333;22223333;11110000-bbbb-2222-cccc-4444dddd5555" |
+| IngestionOperationId | ClientRequestId | OperationInfo | CancelationInfo |
+|----------------------|-----------------|---------------|---------------|
+|22223333;22223333;11110000-bbbb-2222-cccc-4444dddd5555|Kusto.Web.KWE,Query;22223333;22223333;33334444-dddd-4444-eeee-5555eeee5555|.show queued ingestion operations "22223333;22223333;11110000-bbbb-2222-cccc-4444dddd5555" |.cancel queued ingestion operations "22223333;22223333;11110000-bbbb-2222-cccc-4444dddd5555" |
 
 The `OperationInfo` is then used to [track the ingestion status](#track-ingestion-status).