Merge pull request #102576 from orspod/2020-1-ADX-proxy

ADX proxy updates

Author: TedA-M

articles/data-explorer/media/adx-proxy/cross-query-adx-proxy.png

@@ -7,14 +7,14 @@ ms.author: orspodek
 ms.reviewer: rkarlin
 ms.service: data-explorer
 ms.topic: conceptual
-ms.date: 07/10/2019
+ms.date: 01/28/2020
 
 #Customer intent: I want to query data in Azure Monitor using Azure Data Explorer by creating an Azure Data Explorer (ADX) proxy for cross product queries with Log Analytics and Application Insights 
 ---
 
 # Query data in Azure Monitor using Azure Data Explorer (Preview)
 
-The Azure Data Explorer proxy cluster (ADX Proxy) is an entity that enables you to perform cross product queries between Azure Data Explorer, [Application Insights (AI)](/azure/azure-monitor/app/app-insights-overview), and [Log Analytics (LA)](/azure/azure-monitor/platform/data-platform-logs) in the [Azure Monitor](/azure/azure-monitor/) service. You can map Azure Monitor Log Analytics workspaces or Application Insights apps as a proxy cluster. You can then query the proxy cluster using Azure Data Explorer tools and refer to it in a cross cluster query. The article shows how to connect to a proxy cluster, add a proxy cluster to Azure Data Explorer Web UI, and run queries against your AI apps or LA workspaces from Azure Data Explorer.
+The Azure Data Explorer proxy cluster (ADX Proxy) is an entity that enables you to perform cross product queries between Azure Data Explorer, [Application Insights (AI)](/azure/azure-monitor/app/app-insights-overview), and [Log Analytics (LA)](/azure/azure-monitor/platform/data-platform-logs) in the [Azure Monitor](/azure/azure-monitor/) service. You can map Azure Monitor Log Analytics workspaces or Application Insights apps as proxy clusters. You can then query the proxy cluster using Azure Data Explorer tools and refer to it in a cross cluster query. The article shows how to connect to a proxy cluster, add a proxy cluster to Azure Data Explorer Web UI, and run queries against your AI apps or LA workspaces from Azure Data Explorer.
 
 The Azure Data Explorer proxy flow: 
 
@@ -23,7 +23,7 @@ The Azure Data Explorer proxy flow:
 ## Prerequisites
 
 > [!NOTE]
-> The ADX Proxy is in preview mode. To enable this feature, contact the [ADXProxy](mailto:[email protected]) team.
+> The ADX Proxy is in preview mode. [Connect to the proxy](#connect-to-the-proxy) to enable the ADX proxy feature for your clusters. Contact the [ADXProxy](mailto:[email protected]) team with any questions.
 
 ## Connect to the proxy
 
@@ -33,9 +33,10 @@ The Azure Data Explorer proxy flow:
 
 1. In the Azure Data Explorer UI (https://dataexplorer.azure.com/clusters), select **Add Cluster**.
 
-1. In the **Add Cluster** window:
-
-    * Add the URL to the LA or AI cluster. For example: `https://ade.loganalytics.io/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/microsoft.operationalinsights/workspaces/<workspace-name>`
+1. In the **Add Cluster** window, add the URL to the LA or AI cluster. 
+    
+    * For LA: `https://ade.loganalytics.io/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/microsoft.operationalinsights/workspaces/<workspace-name>`
+    * For AI: `https://ade.applicationinsights.io/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/microsoft.insights/components/<ai-app-name>`
 
     * Select **Add**.
 
@@ -49,46 +50,25 @@ The Azure Data Explorer proxy flow:
 
 ## Run queries
 
-You can use Kusto Explorer, ADX web Explorer, Jupyter Kqlmagic, or REST API to query the proxy clusters. 
+You can run the queries using client tools that support Kusto queries, such as: Kusto Explorer, ADX Web UI, Jupyter Kqlmagic, Flow, PowerQuery, PowerShell, Jarvis, Lens, REST API.
 
 > [!TIP]
 > * Database name should have the same name as the resource specified in the proxy cluster. Names are case sensitive.
 > * In cross cluster queries, make sure that the naming of Application Insights apps and Log Analytics workspaces is correct.
 >     * If names contain special characters, they're replaced by URL encoding in the proxy cluster name. 
 >     * If names include characters that don't meet [KQL identifier name rules](/azure/kusto/query/schema-entities/entity-names), they are replaced by the dash **-** character.
 
-### Query against the native Azure Data Explorer cluster 
-
-Run queries on your Azure Data Explorer cluster (such as *StormEvents* table in *help* cluster). When running the query, verify that your native Azure Data Explorer cluster is selected in the left pane.
-
-```kusto
-StormEvents | take 10 // Demonstrate query through the native ADX cluster
-```
-
-![Query StormEvents table](media/adx-proxy/query-adx.png)
-
-### Query against your LA or AI cluster
+### Direct query from your LA or AI ADX Proxy cluster
 
-When you run queries on your LA or AL cluster, verify that your LA or AI cluster is selected in the left pane. 
+Run queries on your LA or AI cluster. Verify that your cluster is selected in the left pane. 
 
 ```kusto
 Perf | take 10 // Demonstrate query through the proxy on the LA workspace
 ```
 
 ![Query LA workspace](media/adx-proxy/query-la.png)
 
-### Query your LA or AI cluster from the ADX proxy  
-
-When you run queries on your LA or AI cluster from the proxy, verify your ADX native cluster is selected in the left pane. The following example demonstrates a query of the LA workspace using the native ADX cluster
-
-```kusto
-cluster('https://ade.loganalytics.io/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/microsoft.operationalinsights/workspaces/<workspace-name>').database('<workspace-name').Perf
-| take 10 
-```
-
-![Query from Azure Data Explorer proxy](media/adx-proxy/query-adx-proxy.png)
-
-### Cross query of LA or AI cluster and the ADX cluster from the ADX proxy 
+### Cross query of your LA or AI ADX Proxy cluster and the ADX native cluster 
 
 When you run cross cluster queries from the proxy, verify your ADX native cluster is selected in the left pane. The following examples demonstrate combining ADX cluster tables (using `union`) with LA workspace.