Fixes for PR review

shsagir · shsagir · commit 09225500be1a · 2021-10-29T10:30:13.000+03:00
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-authentication.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-authentication.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 ## Authentication
 
 To run the following example, you need an Azure Active Directory (Azure AD) application and service principal that can access resources. To create a free Azure AD application and add role assignment at the subscription level, see [Create an Azure AD application](/azure/active-directory/develop/howto-create-service-principal-portal). You also need the directory (tenant) ID, application ID, and client secret.
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-clean-resources.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-clean-resources.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 ## Clean up resources
 
 When the Azure resources are no longer needed, clean up the resources you deployed by deleting the resource group. 
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-container-system-properties.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-container-system-properties.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 ### Schema mapping examples
 
 **Table schema mapping example**
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-create-table-studio.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-create-table-studio.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 1. In Synapse Studio, on the left-side pane, select **Develop**.
 1. Under **KQL scripts**, Select **&plus;** (Add new resource) > **KQL script**. On the right-side pane, you can name your script.
 1. In the **Connect to** menu, select *contosodataexplorer*.
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-data-connection-clean-resources-csharp.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-data-connection-clean-resources-csharp.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 ## Clean up resources
 
 To delete the data connection, use the following command:
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-data-connection-clean-resources-python.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-data-connection-clean-resources-python.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 ## Clean up resources
 
 To delete the data connection, use the following command:
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-data-connection-install-nuget-csharp.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-data-connection-install-nuget-csharp.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 ## Install C# NuGet
 
 * Install the [Microsoft.Azure.Management.Kusto NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Management.Kusto/).
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-data-connection-install-package-python.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-data-connection-install-package-python.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 ## Install Python package
 
 To install the Python package for Azure Synapse Data Explorer, open a command prompt that has Python in its path. Run the following command:
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-event-hub-intro.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-event-hub-intro.md
@@ -1 +1,9 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 Azure Synapse Data Explorer is a fast and highly scalable data exploration service for log and telemetry data. Azure Synapse Data Explorer offers ingestion (data loading) from Event Hubs, IoT Hubs, and blobs written to blob containers.
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-event-hub-system-mapping.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-event-hub-system-mapping.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 > [!NOTE]
 > * System properties are supported for `json` and tabular formats (`csv`, `tsv` etc.) and aren't supported on compressed data. When using a non-supported format, the data will still be ingested, but the properties will be ignored.
 > * For tabular data, system properties are supported only for single-record event messages.
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-get-endpoint.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-get-endpoint.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 1. In Synapse Studio, on the left-side pane, select **Manage** > **Data Explorer pools**.
 1. Select the Data Explorer pool you want to use to view its details.
 
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-ingest-event-hub-table-mapping.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-ingest-event-hub-table-mapping.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 ### Create a table on your test cluster
 
 Create a table named `StormEvents` that matches the schema of the data in the `StormEvents.csv` file.
diff --git a/articles/synapse-analytics/data-explorer/includes/data-explorer-ingest-prerequisites.md b/articles/synapse-analytics/data-explorer/includes/data-explorer-ingest-prerequisites.md
@@ -1,3 +1,11 @@
+---
+ms.topic: include
+ms.date: 11/02/2021
+author: shsagir
+ms.author: shsagir
+ms.service: synapse-analytics
+ms.subservice: data-explorer
+---
 - An Azure subscription. Create a [free Azure account](https://azure.microsoft.com/free/).
 
 - Create a Data Explorer pool using [Synapse Studio](../data-explorer-create-pool-studio.md) or [the Azure portal](../data-explorer-create-pool-portal.md)
diff --git a/articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-csharp.md b/articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-csharp.md
@@ -45,7 +45,7 @@ In this article, you create an Event Hub data connection for Azure Synapse Data
 
 ## Add an Event Hub data connection
 
-The following example shows you how to add an Event Hub data connection programmatically. See [connect to the event hub](data-explorer-ingest-event-hub-portal.md#connect-to-the-event-hub) for adding an Event Hub data connection using the Azure portal.
+The following example shows you how to add an Event Hub data connection programmatically. See [connect to the event hub](data-explorer-ingest-event-hub-portal.md#connect-to-the-event-hub) for information about adding an Event Hub data connection using the Azure portal.
 
 ```csharp
 var tenantId = "xxxxxxxx-xxxxx-xxxx-xxxx-xxxxxxxxx";//Directory (tenant) ID
diff --git a/articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-overview.md b/articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-overview.md
@@ -1,6 +1,6 @@
 ---
 title: Event Hub data connection for Azure Synapse Data Explorer (Preview)
-description: This article describes provides an overview of how to ingest (load) data into Azure Synapse Data Explorer from Event Hub.
+description: This article provides an overview of how to ingest (load) data into Azure Synapse Data Explorer from Event Hub.
 ms.topic: how-to
 ms.date: 11/02/2021
 author: shsagir
diff --git a/articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-portal.md b/articles/synapse-analytics/data-explorer/ingest-data/data-explorer-ingest-event-hub-portal.md
@@ -64,7 +64,7 @@ Create an Event Hub by using an Azure Resource Manager template in the Azure por
 
 1. To create an Event Hub, use the following button to start the deployment. Right-click and select **Open in new window**, so you can follow the rest of the steps in this article.
 
-    [![Deploy to Azure button](../media/ingest-data-event-hub/deploybutton.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.eventhub%2Fevent-hubs-create-event-hub-and-consumer-group%2Fazuredeploy.json)
+    [![Deploy to Azure button](../media/ingest-data-event-hub/deploy-button.png)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.eventhub%2Fevent-hubs-create-event-hub-and-consumer-group%2Fazuredeploy.json)
 
     The **Deploy to Azure** button takes you to the Azure portal.
 
@@ -100,7 +100,7 @@ Create an Event Hub by using an Azure Resource Manager template in the Azure por
 
 ### Authentication considerations
 
-Depending on the type of identity you are using to authenticate with the Event Hub, you may need some additional configurations.
+Depending on the type of identity, you are using to authenticate with the Event Hub, you may need some additional configurations.
 
 - If you are authenticating with Event Hub using a user assigned managed identity, go to your Event Hub > **Networking**, and then under **Allow access from**, select **All networks** and save the changes.
 
@@ -133,13 +133,13 @@ Fill out the form with the following information, and then select **Create**.
 **Setting** | **Suggested value** | **Field description**
 |---|---|---|
 | Data connection name | *test-hub-connection* | The name of the connection you want to create in Azure Synapse Data Explorer.|
-| Subscription |      | The subscription ID where the Event Hub resource is located. This field is auto-populated. |
+| Subscription |      | The subscription ID where the Event Hub resource is located. This field is autopopulated. |
 | Event Hub namespace | A unique namespace name | The name you chose earlier that identifies your namespace. |
 | Event Hub | *test-hub* | The Event Hub you created. |
 | Consumer group | *test-group* | The consumer group defined in the Event Hub you created. |
 | Event system properties | Select relevant properties | The [Event Hub system properties](/azure/service-bus-messaging/service-bus-amqp-protocol-guide#message-annotations). If there are multiple records per event message, the system properties will be added to the first record. When adding system properties, [create](/azure/data-explorer/kusto/management/create-table-command?context=/azure/synapse-analytics/context/context) or [update](/azure/data-explorer/kusto/management/alter-table-command?context=/azure/synapse-analytics/context/context) table schema and [mapping](/azure/data-explorer/kusto/management/mappings?context=/azure/synapse-analytics/context/context) to include the selected properties. |
 | Compression | *None* | The compression type of the Event Hub messages payload. Supported compression types: *None, Gzip*.|
-| Managed Identity (recommended) | System-assigned | The managed identity used by the Data Explorer cluster for access to read from the Event Hub. We recommend using managed identities to control access to your Event Hub.<br /><br />**Note**:<br />When the data connection is created:<br/>\* *System-assigned* identities are automatically created if they don't exist<br />\* The managed identity is automatically assigned the *Azure Event Hubs Data Receiver* role and is added to your Data Explorer cluster. We recommend verifying that the role was assigned and that the identity was added to the cluster. |
+| Managed Identity (recommended) | System-assigned | The managed identity used by the Data Explorer cluster for access to read from the Event Hub. We recommend using managed identities to control access to your Event Hub.<br /><br />**Note**:<br />When the data connection is created:<br/>\- *System-assigned* identities are automatically created if they don't exist<br />\- The managed identity is automatically assigned the *Azure Event Hubs Data Receiver* role and is added to your Data Explorer cluster. We recommend verifying that the role was assigned and that the identity was added to the cluster. |
 
 > [!NOTE]
 > If you have an existing data connection that is not using managed identities, we recommend updating it to use managed identities.
@@ -197,7 +197,7 @@ Use the [sample app](https://github.com/Azure-Samples/event-hubs-dotnet-ingest)
     const string connectionString = @"<YourConnectionString>";
     ```
 
-1. Build and run the app. The app sends messages to the Event Hub, and prints out its status every 10 seconds.
+1. Build and run the app. The app sends messages to the Event Hub, and prints its status every 10 seconds.
 1. After the app has sent a few messages, move on to the next step: reviewing the flow of data into your Event Hub and test table.
 
 ## Review the data flow
@@ -227,7 +227,7 @@ With the app generating data, you can now see the flow of that data from the Eve
 
     > [!NOTE]
     >
-    > * Azure Synapse Data Explorer has an aggregation (batching) policy for data ingestion, designed to optimize the ingestion process. The default batching policy is configured to seal a batch once one of the following conditions is true for the batch: a maximum delay time of 5 minutes, total size of 1G, or 1000 blobs. Therefore, you may experience a latency. For more information see [batching policy](/azure/data-explorer/kusto/management/batchingpolicy?context=/azure/synapse-analytics/context/context).
+    > * Azure Synapse Data Explorer has an aggregation (batching) policy for data ingestion, designed to optimize the ingestion process. The default batching policy is configured to seal a batch once one of the following conditions is true for the batch: a maximum delay time of 5 minutes, total size of 1G, or 1000 blobs. Therefore, you may experience a latency. For more information, see [batching policy](/azure/data-explorer/kusto/management/batchingpolicy?context=/azure/synapse-analytics/context/context).
     > * Event Hub ingestion includes Event Hub response time of 10 seconds or 1 MB.
     > * To reduce response time lag, configure your table to support streaming. See [streaming policy](/azure/data-explorer/kusto/management/streamingingestionpolicy?context=/azure/synapse-analytics/context/context).
 
diff --git a/articles/synapse-analytics/data-explorer/media/create-data-explorer-pool-portal/confirm-deletion-data-explorer-pool-portal.png b/articles/synapse-analytics/data-explorer/media/create-data-explorer-pool-portal/confirm-deletion-data-explorer-pool-portal.png
diff --git a/articles/synapse-analytics/data-explorer/media/create-data-explorer-pool-portal/goto-data-explorer-pool-portal.png b/articles/synapse-analytics/data-explorer/media/create-data-explorer-pool-portal/goto-data-explorer-pool-portal.png
diff --git a/articles/synapse-analytics/data-explorer/media/create-data-explorer-pool-portal/list-data-explorer-pool-portal.png b/articles/synapse-analytics/data-explorer/media/create-data-explorer-pool-portal/list-data-explorer-pool-portal.png
diff --git a/articles/synapse-analytics/data-explorer/media/create-data-explorer-pool-portal/verify-data-explorer-pool-portal.png b/articles/synapse-analytics/data-explorer/media/create-data-explorer-pool-portal/verify-data-explorer-pool-portal.png
diff --git a/articles/synapse-analytics/data-explorer/media/ingest-data-event-hub/connection-string.png b/articles/synapse-analytics/data-explorer/media/ingest-data-event-hub/connection-string.png
diff --git a/articles/synapse-analytics/data-explorer/media/ingest-data-event-hub/delete-resources-select.png b/articles/synapse-analytics/data-explorer/media/ingest-data-event-hub/delete-resources-select.png
diff --git a/articles/synapse-analytics/data-explorer/media/ingest-data-event-hub/deploy-button.png b/articles/synapse-analytics/data-explorer/media/ingest-data-event-hub/deploy-button.png
