Merge pull request #2443 from MicrosoftDocs/main638676147308230920sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

data-explorer/create-table-wizard.md

@@ -3,7 +3,7 @@ title: Create a table in Azure Data Explorer
 description: Learn how to easily create a table and manually define the schema in Azure Data Explorer with the table creation wizard.
 ms.reviewer: aksdi
 ms.topic: how-to
-ms.date: 03/07/2024
+ms.date: 11/13/2024
 # Customer intent: As a data engineer, I want to create an empty table in Azure Data Explorer so that I can ingest data and query it.
 ---
 # Create a table in Azure Data Explorer
@@ -33,19 +33,19 @@ Creating a table is an important step in the process of [data ingestion](ingest-
 
 The **Create table** window opens with the **Destination** tab selected.
 
-1. The **Cluster** and **Database** fields are prepopulated. You may select different values from the drop-down menu.
+1. The **Cluster** and **Database** fields are prepopulated. You can select different values from the drop-down menu.
 1. In **Table name**, enter a name for your table.
 
     > [!TIP]
-    >  Table names can be up to 1024 characters including alphanumeric, hyphens, and underscores. Special characters aren't supported.
+    > Table names can be up to 1024 characters including alphanumeric, hyphens, and underscores. Special characters aren't supported.
 
 1. Select **Next: Schema**
 
 ## Schema tab
 
 1. Select **Add new column** and the **Edit columns** panel opens.
 1. For each column, enter **Column name** and **Data type**. Create more columns by selecting **Add column**.
-    
+
     :::image type="content" source="media/create-table-wizard/edit-columns.png" alt-text="Screenshot of Edit columns pane, in which you input the column name and data type in Azure Data Explorer.":::
 
 1. Select **Save**. The schema is displayed.
@@ -59,3 +59,8 @@ A new table is created in your target destination, with the schema you defined.
 
 * [Data ingestion overview](ingest-data-overview.md)
 * [Write queries for Azure Data Explorer](/azure/data-explorer/kusto/query/tutorials/learn-common-operators)
+* [Ingest data using the Kusto .NET SDK](net-sdk-ingest-data.md)
+* [Ingest data using the Azure Data Explorer Python library](python-ingest-data.md)
+* [Ingest data using the Azure Data Explorer Node library](node-ingest-data.md)
+* [Ingest data using the Azure Data Explorer Go SDK](go-ingest-data.md)
+* [Ingest data using the Kusto Java SDK](java-ingest-data.md)

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

@@ -3,7 +3,7 @@ title: Stored query results
 description: Learn how to manage stored query results.
 ms.reviewer: mispecto
 ms.topic: reference
-ms.date: 08/11/2024
+ms.date: 11/18/2024
 ---
 
 # Stored query results
@@ -47,3 +47,13 @@ The following table lists the management commands and functions used for managin
 |[.show stored_query_result command](show-stored-query-result-command.md)| Shows information on active query results. |
 |[.drop stored_query_result command](drop-stored-query-result-command.md)| Deletes active query results.|
 |[stored_query_result()](../query/stored-query-result-function.md)| Retrieves a stored query result. |
+
+## Related Content
+
+* [Stored functions](../query/schema-entities/stored-functions.md)
+:::moniker range="azure-data-explorer"
+* [Pin a query to Azure Data Explorer dashboards](/azure/data-explorer/azure-data-explorer-dashboards#pin-tile-from-query)
+::: moniker-end
+:::moniker range="microsoft-fabric"
+* [Add a query to a Real-Time Dashboard tile](/fabric/real-time-intelligence/dashboard-real-time-create#add-tile)
+::: moniker-end

data-explorer/kusto/management/stored-query-results.md

@@ -3,7 +3,7 @@ title:  .update table command
 description: Learn how to use the .update table command to perform transactional data updates.
 ms.reviewer: vplauzon
 ms.topic: reference
-ms.date: 08/22/2024
+ms.date: 11/18/2024
 ---
 # .update table command
 
@@ -25,9 +25,6 @@ You must have at least [Table Admin](../access-control/role-based-access-control
 
 ## Syntax
 
-> [!NOTE]
-> The *simplified* syntax, which was available during preview, has been deprecated.
-
 [!INCLUDE [syntax-conventions-note](../includes/syntax-conventions-note.md)]
 
 `.update` `[async]` `table` *TableName* `delete` *DeleteIdentifier* `append` *AppendIdentifier* [`with` `(` *propertyName* `=` *propertyValue* `)`] `<|` <br>

data-explorer/kusto/management/update-table-command.md

@@ -1,14 +1,14 @@
 ---
 title: Create a managed private endpoint for Azure Data Explorer
-description: In this article, you'll learn how to create a managed private endpoint for Azure Data Explorer.
+description: In this article, you learn how to create a managed private endpoint for Azure Data Explorer.
 ms.reviewer: eladb
 ms.topic: how-to
-ms.date: 04/05/2022
+ms.date: 11/18/2024
 ---
 
 # Create a managed private endpoint for Azure Data Explorer
 
-Managed private endpoints are required to connect to Azure resources that are highly protected. They are one-way private connections that allow Azure Data Explorer to connect to other protected services. In this article, you'll learn how to create a managed private endpoint and connect it to your data source.
+Managed private endpoints are required to connect to Azure resources that are highly protected. They're one-way private connections that allow Azure Data Explorer to connect to other protected services. In this article, you'll learn how to create a managed private endpoint and connect it to your data source.
 
 ## Prerequisites
 
@@ -37,15 +37,14 @@ You can create a managed private endpoint using the portal for your cluster to u
     | Resource type | *Microsoft.Storage/storageAccounts* | Select the relevant resources type you want for your data source. |
     | Resource name | *share* | Choose the cluster that should be used as the destination for the new Azure Private Endpoint |
     | Target sub-resource | *blob* | Select the relevant target for your data source. |
-    | | | |
 
 1. select **Create** to create the managed private endpoint resource.
 
 ## Create a managed private endpoint using the REST API
 
 Creating a managed private endpoint requires a single API call to the *Kusto* resource provider. You can establish a managed private endpoint to the following resource types:
 
-* Microsoft.Storage/storageAccounts (sub-resource may be "blob" or "dfs")
+* Microsoft.Storage/storageAccounts (sub-resource can be "blob" or "dfs")
 * Microsoft.EventHub/namespaces (sub-resource "namespace")
 * Microsoft.Devices/IoTHubs (sub-resource "iotHub")
 * Microsoft.KeyVault/vaults (sub-resource "vault")
@@ -183,7 +182,7 @@ To check the progress of the managed private endpoint migration, use the followi
 
 ## Approve the managed private endpoint
 
-Whichever method you used to create the managed private endpoint using, you must approve its creation on target resource. The following example shows the approval of a managed private endpoint to an Event Hubs service.
+Whichever method you used to create the managed private endpoint, you must approve its creation on the target resource. To approve a managed private endpoint to an Event Hubs service:
 
 1. In the Azure portal, navigate to your Event Hubs service and then select **Networking**.
 
@@ -197,6 +196,123 @@ Whichever method you used to create the managed private endpoint using, you must
 
 Your cluster can now connect to the resource using the managed private endpoint connection.
 
+## Create multiple managed private endpoints
+
+You can create multiple managed private endpoints using ARM templates and Terraform. The following examples ensure that the managed private endpoint to the Event Hubs namespace is created before the one to the Storage account.
+
+### [ARM template](#tab/ARM-template)
+
+The following example uses an ARM template to create two managed private endpoints in an Azure Data Explorer cluster. The first endpoint connects to an Event Hubs namespace. The second endpoint connects to a Storage account, with a dependency that ensures that the Event Hubs endpoint is created first.
+
+```json
+{
+    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+    "contentVersion": "1.0.0.0",
+    "parameters": {
+        "cluster_name": {
+            "defaultValue": "<ADX cluster name>",
+            "type": "String"
+        },
+        "eventhub_resource_id": {
+            "defaultValue": "<Eventhub resource id>",
+            "type": "String"
+        },
+        "storage_resource_id": {
+            "defaultValue": "<Storage resource id>",
+            "type": "String"
+        },
+        "managed_pe_eventhub_name": {
+            "defaultValue": "<name of the managed private endpoint to Event Hub>",
+            "type": "String"
+        },
+        "managed_pe_storage_name": {
+            "defaultValue": "<name of the managed private endpoint to Storage>",
+            "type": "String"
+        }
+    },
+    "variables": {},
+    "resources": [
+        {
+            "type": "Microsoft.Kusto/Clusters",
+            "apiVersion": "2023-08-15",
+            "name": "[parameters('cluster_name')]",
+            "location": "<region of the cluster>",
+            "sku": {...},
+            "zones": {...}
+            "properties": {...}
+        },
+        {
+            "type": "Microsoft.Kusto/Clusters/ManagedPrivateEndpoints",
+            "apiVersion": "2023-08-15",
+            "name": "[concat(parameters('cluster_name'), '/', parameters('managed_pe_eventhub_name'))]",
+            "dependsOn": [
+                "[resourceId('Microsoft.Kusto/Clusters', parameters('cluster_name'))]"
+            ],
+            "properties": {
+                "privateLinkResourceId": "[parameters('eventhub_resource_id')]",
+                "groupId": "namespace",
+                "requestMessage": "Please approve"
+            }
+        },
+        {
+            "type": "Microsoft.Kusto/Clusters/ManagedPrivateEndpoints",
+            "apiVersion": "2023-08-15",
+            "name": "[concat(parameters('cluster_name'), '/', parameters('managed_pe_storage_name'))]",
+            "dependsOn": [
+                "[resourceId('Microsoft.Kusto/Clusters', parameters('cluster_name'))]",
+                "[resourceId('Microsoft.Kusto/Clusters/ManagedPrivateEndpoints', parameters('cluster_name'), parameters('managed_pe_eventhub_name'))]"
+            ],
+            "properties": {
+                "privateLinkResourceId": "[parameters('storage_resource_id')]",
+                "groupId": "blob",
+                "requestMessage": "Please approve"
+            }
+        }
+    ]
+}
+```
+
+### [Terraform configuration](#tab/Terraform-configuration)
+
+The following example uses a Terraform configuration that creates two managed private endpoints in an Azure Data Explorer cluster. The first endpoint connects to an Event Hubs namespace. The second endpoint connects to a Storage account, with a dependency that ensures that the Event Hubs endpoint is created first.
+
+```hcl
+resource "azapi_resource" "mpe_to_eventhub" {
+  type = "Microsoft.Kusto/clusters/managedPrivateEndpoints@2023-08-15"
+  name                 = "mpeToEventHub"
+  parent_id            = "<the resource id of the cluster>"
+  body = jsonencode({
+    properties = {
+      groupId = "namespace"
+      privateLinkResourceId = "<The ARM resource ID of the EventHub for which the managed private endpoint is created.>"
+      requestMessage = "Please Approve."
+    }
+  })
+}
+
+resource "azapi_resource" "mpe_to_storage" {
+  type = "Microsoft.Kusto/clusters/managedPrivateEndpoints@2023-08-15"
+  name                 = "mpeToStorage"
+  parent_id            = "<the resource id of the cluster>"
+  body = jsonencode({
+    properties = {
+      groupId = "blob"
+      privateLinkResourceId = "<The ARM resource ID of the Storage Account for which the managed private endpoint is created.>"
+      requestMessage = "Please Approve."
+    }
+  })
+  depends_on = [
+    azapi_resource.mpe_to_eventhub
+  ]
+}
+```
+
+---
+
+## Automatic approval
+
+You can [automatically approve](/azure/private-link/private-endpoint-overview#access-to-a-private-link-resource-using-approval-workflow) a managed private endpoint if the requesting identity has the **Microsoft.\<Provider>/\<ResourceType>/privateEndpointConnectionsApproval/action** permission on the target resource of the managed private endpoint.
+
 ## Related content
 
 * [Troubleshooting private endpoints in Azure Data Explorer](security-network-private-endpoint-troubleshoot.md)