From 118cca4ff9f8b11f619f077f11cc80e51de45c62 Mon Sep 17 00:00:00 2001 From: Sreedhar Pelluru <6722422+spelluru@users.noreply.github.com> Date: Tue, 26 Aug 2025 17:26:00 -0400 Subject: [PATCH 1/3] ADX - Freshness Review --- data-explorer/create-event-hubs-connection.md | 18 +++++------ .../create-iot-hub-connection-sdk.md | 10 +++---- .../ingest-data-event-hub-overview.md | 30 +++++++++---------- data-explorer/start-for-free-event-hubs.md | 2 +- 4 files changed, 30 insertions(+), 30 deletions(-) diff --git a/data-explorer/create-event-hubs-connection.md b/data-explorer/create-event-hubs-connection.md index fdaf45f38d..c544b365fd 100644 --- a/data-explorer/create-event-hubs-connection.md +++ b/data-explorer/create-event-hubs-connection.md @@ -3,7 +3,7 @@ title: 'Create an Event Hubs data connection - Azure Data Explorer' description: Learn how to ingest data from Event Hubs into Azure Data Explorer. ms.topic: how-to ms.custom: -ms.date: 08/04/2025 +ms.date: 08/26/2025 --- # Create an Event Hubs data connection for Azure Data Explorer @@ -12,13 +12,13 @@ Azure Data Explorer offers ingestion from [Event Hubs](/azure/event-hubs/event-h In this article, you connect to an event hub and ingest data into Azure Data Explorer. For an overview on ingesting from Event Hubs, see [Azure Event Hubs data connection](ingest-data-event-hub-overview.md). -To learn how to create the connection using the Kusto SDKs, see [Create an Event Hubs data connection with SDKs](create-event-hubs-connection-sdk.md). +To learn how to create the connection using the Kusto software developer kits (SDKs), see [Create an Event Hubs data connection with SDKs](create-event-hubs-connection-sdk.md). > For code samples based on previous SDK versions, see the [archived article](/previous-versions/azure/data-explorer/create-event-hubs-connection). > [!WARNING] > -> The Get Data Wizard doesn't support creating a data connection to Event Hubs through [private endpoints](security-network-private-endpoint.md) or [managed private endpoints](security-network-private-endpoint.md#managed-private-endpoints). To create a data connection from the Azure Portal, follow the instructions in the **Portal - Azure Event Hubs page** tab. +> The Get Data Wizard doesn't support creating a data connection to Event Hubs through [private endpoints](security-network-private-endpoint.md) or [managed private endpoints](security-network-private-endpoint.md#managed-private-endpoints). To create a data connection from the Azure portal, follow the instructions in the **Portal - Azure Event Hubs page** tab. ## Create an event hub data connection @@ -53,7 +53,7 @@ Select the data source from the available list. In this example, you're ingestin 1. Select a target database and table. If you want to ingest data into a new table, select **+ New table** and enter a table name. > [!NOTE] - > Table names can be up to 1024 characters including spaces, alphanumeric, hyphens, and underscores. Special characters aren't supported. + > Table names can be up to 1,024 characters including spaces, alphanumeric, hyphens, and underscores. Special characters aren't supported. :::image type="content" source="media/get-data-event-hubs/configure-tab.png" alt-text="Screenshot of configure tab with fields for configuring the data source of Event Hubs in Azure Data Explorer." lightbox="media/get-data-event-hubs/configure-tab.png"::: @@ -139,11 +139,11 @@ In the **Data preparation** window, all three steps are marked with green check | 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 are added to the first record. When adding system properties, [create](/kusto/management/create-table-command?view=azure-data-explorer&preserve-view=true) or [update](/kusto/management/alter-table-command?view=azure-data-explorer&preserve-view=true) table schema and [mapping](/kusto/management/mappings?view=azure-data-explorer&preserve-view=true) to include the selected properties. | - | Compression | *None* | The compression type of the event hub messages payload. Supported compression types: *None, gzip*.| + | 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.

**Note**:
When the data connection is created:
\* *System-assigned* identities are automatically created if they don't exist
\* 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. + > If you have an existing data connection that isn't using managed identities, we recommend updating it to use managed identities. ### [Portal - Azure Event Hubs page](#tab/portalEH) @@ -161,7 +161,7 @@ In the **Data preparation** window, all three steps are marked with green check 1. Under the **Features** side menu, select **Analyze data with Kusto**. 1. Select **Start** to open the ingestion wizard to Azure Data Explorer. - :::image type="content" source="media/create-event-hubs-connection/access-from-portal-event-hubs.png" alt-text="Screenshot of the Azure portal with the analyze data with Kusto feature selected." lightbox="media/create-event-hubs-connection/access-from-portal-event-hubs.png"::: + :::image type="content" source="media/create-event-hubs-connection/access-from-portal-event-hubs.png" alt-text="Screenshot of the Azure portal with the Analyze data with Kusto feature selected." lightbox="media/create-event-hubs-connection/access-from-portal-event-hubs.png"::: > [!NOTE] > @@ -169,7 +169,7 @@ In the **Data preparation** window, all three steps are marked with green check > * To enable access between a cluster and a storage account without public access, see [Create a Managed Private Endpoint](security-network-private-endpoint-create.md). > * The cluster and event hub should be associated with the same tenants. If not, use one of the SDK options, such as C# or Python. -1. The **Ingest data** side pane opens with the **Destination** tab selected. Select the **Cluster** and **Database** fields from the dropdowns. Make sure you select a cluster that is running. Otherwise, you won't be able to select Database and proceed with the ingestion process. +1. The **Ingest data** side pane opens with the **Destination** tab selected. Select the **Cluster** and **Database** fields from the dropdowns. Make sure you select a cluster that is running. Otherwise, you can't select Database and proceed with the ingestion process. 1. Under **Table**, select **New table** and enter a name for the new table. Alternatively, use an **Existing table**. @@ -351,7 +351,7 @@ Remove the data connection through the Azure portal as explained in the portal t ### [Portal](#tab/portal-2) -To remove the event hub connection from the Azure portal, do the following: +To remove the event hub connection from the Azure portal, do the following steps: 1. Go to your cluster. From the left menu, select **Databases**. Then, select the database that contains the target table. 1. From the left menu, select **Data connections**. Then, select the checkbox next to the relevant event hub data connection. diff --git a/data-explorer/create-iot-hub-connection-sdk.md b/data-explorer/create-iot-hub-connection-sdk.md index 49b27e6de1..547f47ac12 100644 --- a/data-explorer/create-iot-hub-connection-sdk.md +++ b/data-explorer/create-iot-hub-connection-sdk.md @@ -2,12 +2,12 @@ title: 'Create an IoT Hub data connection with SDKs - Azure Data Explorer' description: 'In this article, you learn how to ingest data into Azure Data Explorer from IoT Hub using SDKs.' ms.topic: how-to -ms.date: 07/16/2023 +ms.date: 08/26/2025 --- # Create an IoT Hub data connection for Azure Data Explorer with SDKs -This article shows you how to ingest data into Azure Data Explorer from IoT Hub, a big data streaming platform and IoT ingestion service. +This article shows you how to ingest data into Azure Data Explorer from IoT Hub, a big data streaming platform, and IoT ingestion service. To learn how to create the connection using the Kusto SDKs, see [Create an IoT Hub data connection with SDKs](create-iot-hub-connection-sdk.md). @@ -28,13 +28,13 @@ For general information about ingesting into Azure Data Explorer from IoT Hub, s ## Create an IoT Hub data connection -In this section, you'll establish a connection between the IoT Hub and your Azure Data Explorer table. As long as this connection is in place, data is transmitted from the IoT Hub into your target table. +In this section, you establish a connection between the IoT Hub and your Azure Data Explorer table. As long as this connection is in place, data is transmitted from the IoT Hub into your target table. ### [C#](#tab/c-sharp) 1. Install the [Microsoft.Azure.Management.Kusto NuGet package](https://www.nuget.org/packages/Microsoft.Azure.Management.Kusto/). -1. [Create a Microsoft Entra application principal](/azure/active-directory/develop/howto-create-service-principal-portal) to use for authentication. You'll need the directory (tenant) ID, application ID, and client secret. +1. [Create a Microsoft Entra application principal](/azure/active-directory/develop/howto-create-service-principal-portal) to use for authentication. You need the directory (tenant) ID, application ID, and client secret. 1. Run the following code. @@ -101,7 +101,7 @@ In this section, you'll establish a connection between the IoT Hub and your Azur pip install azure-mgmt-kusto ``` -1. [Create a Microsoft Entra application principal](/azure/active-directory/develop/howto-create-service-principal-portal) to use for authentication. You'll need the directory (tenant) ID, application ID, and client secret. +1. [Create a Microsoft Entra application principal](/azure/active-directory/develop/howto-create-service-principal-portal) to use for authentication. You need the directory (tenant) ID, application ID, and client secret. 1. Run the following code. diff --git a/data-explorer/ingest-data-event-hub-overview.md b/data-explorer/ingest-data-event-hub-overview.md index 3885978334..67cc708ea0 100644 --- a/data-explorer/ingest-data-event-hub-overview.md +++ b/data-explorer/ingest-data-event-hub-overview.md @@ -1,15 +1,15 @@ --- -title: Ingest from event hub - Azure Data Explorer +title: Ingest from Event Hub - Azure Data Explorer description: This article describes how to ingest data from Azure Event Hubs into Azure Data Explorer. ms.reviewer: orspodek ms.topic: how-to -ms.date: 06/04/2024 +ms.date: 08/26/2025 --- # Azure Event Hubs data connection [Azure Event Hubs](/azure/event-hubs/event-hubs-about) is a big data streaming platform and event ingestion service. Azure Data Explorer offers continuous ingestion from customer-managed Event Hubs. -The Event Hubs ingestion pipeline transfers events to Azure Data Explorer in several steps. First you create an event hub in the Azure portal. Then create a target table in Azure Data Explorer into which the [data in a particular format](#data-format), is ingested using the provided [ingestion properties](#ingestion-properties). The Event Hubs connection needs to be aware of [events routing](#events-routing). Data may be embedded with selected properties according to the [event system properties](#event-hubs-system-properties-mapping). Create a connection to Event Hubs to [create an event hub](#create-event-hubs) and [send events](#send-events). This process can be managed through the [Azure portal](create-event-hubs-connection.md?tabs=portalADX), programmatically with [C#](create-event-hubs-connection-sdk.md?tabs=c-sharp) or [Python](create-event-hubs-connection-sdk.md?tabs=python), or with the [Azure Resource Manager template](create-event-hubs-connection.md?tabs=arm-template). +The Event Hubs ingestion pipeline transfers events to Azure Data Explorer in several steps. First you create an event hub in the Azure portal. Then create a target table in Azure Data Explorer into which the [data in a particular format](#data-format), is ingested using the provided [ingestion properties](#ingestion-properties). The Event Hubs connection needs to be aware of [events routing](#events-routing). Data can be embedded with selected properties according to the [event system properties](#event-hubs-system-properties-mapping). Create a connection to Event Hubs to [create an event hub](#create-event-hubs) and [send events](#send-events). This process can be managed through the [Azure portal](create-event-hubs-connection.md?tabs=portalADX), programmatically with [C#](create-event-hubs-connection-sdk.md?tabs=c-sharp) or [Python](create-event-hubs-connection-sdk.md?tabs=python), or with the [Azure Resource Manager template](create-event-hubs-connection.md?tabs=arm-template). For general information about data ingestion in Azure Data Explorer, see [Azure Data Explorer data ingestion overview](ingest-data-overview.md). @@ -23,7 +23,7 @@ Setup of a data connection using managed identity requires the following steps: 1. Create a data connection using the managed identity authentication to fetch data. > [!CAUTION] - > If the managed identity permissions are removed from the data source, the data connection will no longer work and will be unable to fetch data from the data source. + > If the managed identity permissions are removed from the data source, the data connection doesn't work any long and can't fetch data from the data source. [!INCLUDE [data-connection-auth](includes/data-connection-auth.md)] @@ -35,7 +35,7 @@ Setup of a data connection using managed identity requires the following steps: > [!NOTE] > > * Ingestion from Event Hubs doesn't support RAW format. -> * [Azure Event Hubs Schema Registry](/azure/event-hubs/schema-registry-overview) and schema-less Avro are not supported. +> * [Azure Event Hubs Schema Registry](/azure/event-hubs/schema-registry-overview) and schema-less Avro aren't supported. > * Data can be compressed using the `gzip` compression algorithm. You can specify `Compression` dynamically using [ingestion properties](#ingestion-properties), or in the static Data Connection settings. > * Data compression isn't supported for binary formats (Avro, ApacheAvro, Parquet, ORC, and W3CLOGFILE). > * Custom encoding and embedded [system properties](#event-hubs-system-properties-mapping) aren't supported with binary formats and compressed data. @@ -71,14 +71,14 @@ Ingestion properties instruct the ingestion process, where to route the data, an | RawHeaders | Indicates that event source is Kafka and Azure Data Explorer must use byte array deserialization to read other routing properties. Value is ignored. | > [!NOTE] -> Only events enqueued after you create the data connection are ingested, unless a custom retrieval start date is provided. In any case, the lookback period cannot exceed the actual Event Hub retention period. +> Only events enqueued after you create the data connection are ingested, unless a custom retrieval start date is provided. In any case, the lookback period can't exceed the actual retention period configured for the event hub. ## Events routing When you create a data connection to your cluster, you can specify the routing for where to send ingested data. The default routing is to the target table specified in the connection string that is associated with the target database. The default routing for your data is also referred to as *static routing*. You can specify an alternative routing and processing options for your data by setting one or more of event data properties mentioned in the previous paragraph. > [!NOTE] -> Event Hubs data connection will attempt to process all the events it reads from the Event Hub, and every event it cannot process for whatever reason will be reported as an ingestion failure. +> Event Hubs data connection attempts to process all the events it reads from the event hub, and every event it can't process for whatever reason is reported as an ingestion failure. > Read on how to monitor Azure Data Explorer ingestion [here](/azure/data-explorer/using-diagnostic-logs?tabs=ingestion). ### Route event data to an alternate database @@ -88,14 +88,14 @@ Routing data to an alternate database is off by default. To send the data to a d To specify an alternate database, set the *Database* [ingestion property](#ingestion-properties). > [!WARNING] -> Specifying an alternate database without setting the connection as a multi-database data connection will cause the ingestion to fail. +> Specifying an alternate database without setting the connection as a multi-database data connection causes the ingestion to fail. ### Route event data to an alternate table To specify an alternate table for each event, set the *Table*, *Format*, *Compression*, and mapping [ingestion properties](#ingestion-properties). The connection dynamically routes the ingested data as specified in the [EventData.Properties](/dotnet/api/microsoft.servicebus.messaging.eventdata.properties#Microsoft_ServiceBus_Messaging_EventData_Properties), overriding the static properties for this event. The following example shows you how to set the event hub details and send weather metric data to alternate database (*MetricsDB*) and table (*WeatherMetrics*). -The data is in JSON format and *mapping1* is pre-defined on table *WeatherMetrics*. +The data is in JSON format and *mapping1* is predefined on table *WeatherMetrics*. ```csharp // This sample uses Azure.Messaging.EventHubs which is a .Net Framework library. @@ -116,7 +116,7 @@ await producerClient.SendAsync(events); ## Event Hubs system properties mapping -System properties are fields set by the Event Hubs service, at the time the event is enqueued. +System properties are fields set by the Event Hubs service when the event is enqueued. Azure Data Explorer Event Hubs data connection can embed a predefined set of system properties into the data ingested into a table based on a given mapping. [!INCLUDE [event-hub-system-mapping](includes/event-hub-system-mapping.md)] @@ -139,7 +139,7 @@ If you selected **Event system properties** in the **Data Source** section of th ### Schema mapping for Event Hubs Capture Avro files -One way to consume Event Hubs data is to [capture events through Azure Event Hubs in Azure Blob Storage or Azure Data Lake Storage](/azure/event-hubs/event-hubs-capture-overview). You can then ingest the capture files as they are written using an [Event Grid Data Connection in Azure Data Explorer](ingest-data-event-grid-overview.md). +One way to consume Event Hubs data is to [capture events through Azure Event Hubs in Azure Blob Storage or Azure Data Lake Storage](/azure/event-hubs/event-hubs-capture-overview). You can then ingest the capture files as they're written using an [Event Grid Data Connection in Azure Data Explorer](ingest-data-event-grid-overview.md). The schema of the capture files is different from the schema of the original event sent to Event Hubs. You should design the destination table schema with this difference in mind. Specifically, the event payload is represented in the capture file as a byte array, and this array isn't automatically decoded by the Event Grid Azure Data Explorer data connection. For more information on the file schema for Event Hubs Avro capture data, see [Exploring captured Avro files in Azure Event Hubs](/azure/event-hubs/explore-captured-avro-files). @@ -151,7 +151,7 @@ To correctly decode the event payload: ## Ingest custom properties -When ingesting events from Event Hubs, data is taken from the `body` section of the event data object. However, Event Hubs [custom properties](/azure/event-hubs/add-custom-data-event) are defined in the `properties` section of the object and are not ingested. To ingest customer properties, you must embed them into the data in `body` section of the object. +When ingesting events from Event Hubs, data is taken from the `body` section of the event data object. However, Event Hubs [custom properties](/azure/event-hubs/add-custom-data-event) are defined in the `properties` section of the object and aren't ingested. To ingest customer properties, you must embed them into the data in `body` section of the object. The following example compares the events data object containing custom property `customProperty` as *defined* by Event Hubs (left) with the *embedded* property required for ingestion (right). @@ -187,10 +187,10 @@ The following example compares the events data object containing custom property You can use one of the following methods to embed custom properties into the data in `body` section of the event data object: * In Event Hubs, when creating the event data object, embed the custom properties as part of the data in the `body` section of the object. -* Use Azure Stream Analytics to [process events from the event hub and embed the custom properties](/azure/event-hubs/process-data-azure-stream-analytics) in the event data. From Azure Stream Analytics you can ingest the data natively using the [Azure Data Explorer output connector](/azure/stream-analytics/azure-database-explorer-output), or route the data into another event hub and from there into your cluster. +* Use Azure Stream Analytics to [process events from the event hub and embed the custom properties](/azure/event-hubs/process-data-azure-stream-analytics) in the event data. From Azure Stream Analytics, you can ingest the data natively using the [Azure Data Explorer output connector](/azure/stream-analytics/azure-database-explorer-output), or route the data into another event hub and from there into your cluster. * Use [Azure Functions](/azure/azure-functions/functions-overview) to add the custom properties and then ingest the data. -## Create Event Hubs +## Create event hub If you don't already have one, [Create an event hub](/azure/event-hubs/event-hubs-create). Connecting to event hub can be managed through the [Azure portal](create-event-hubs-connection.md?tabs=portalADX), programmatically with [C#](create-event-hubs-connection-sdk.md?tabs=c-sharp) or [Python](create-event-hubs-connection-sdk.md?tabs=python), or with the [Azure Resource Manager template](create-event-hubs-connection.md?tabs=arm-template). @@ -201,7 +201,7 @@ If you don't already have one, [Create an event hub](/azure/event-hubs/event-hub ### Cross-region Event Hubs data connection -For best performance, create the event hub in the same region as the cluster. If this is not possible, consider using [Premium](/azure/event-hubs/event-hubs-premium-overview) or [Dedicated](/azure/event-hubs/event-hubs-dedicated-overview) Event Hubs tiers. For a comparison of tiers, see [Compare Azure Event Hubs tiers](/azure/event-hubs/compare-tiers). +For best performance, create the event hub in the same region as the cluster. If it isn't possible, consider using [Premium](/azure/event-hubs/event-hubs-premium-overview) or [Dedicated](/azure/event-hubs/event-hubs-dedicated-overview) Event Hubs tiers. For a comparison of tiers, see [Compare Azure Event Hubs tiers](/azure/event-hubs/compare-tiers). ## Send events diff --git a/data-explorer/start-for-free-event-hubs.md b/data-explorer/start-for-free-event-hubs.md index 3bd1fd9612..5c12b73ef1 100644 --- a/data-explorer/start-for-free-event-hubs.md +++ b/data-explorer/start-for-free-event-hubs.md @@ -3,7 +3,7 @@ title: Manage Event Hubs data connections in your free Azure Data Explorer clust description: Learn how to manage Azure Event Hubs data connections in your free cluster. ms.reviewer: guregini ms.topic: how-to -ms.date: 03/20/2023 +ms.date: 08/26/2025 --- # Manage Event Hubs data connections in your free Azure Data Explorer cluster From d38c6459dbadb5aa4a9e3c81c4f065a760d72b25 Mon Sep 17 00:00:00 2001 From: Sreedhar Pelluru <6722422+spelluru@users.noreply.github.com> Date: Tue, 26 Aug 2025 17:35:19 -0400 Subject: [PATCH 2/3] Fixed broken link --- data-explorer/ingest-data-event-hub-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data-explorer/ingest-data-event-hub-overview.md b/data-explorer/ingest-data-event-hub-overview.md index 67cc708ea0..8f393a79f7 100644 --- a/data-explorer/ingest-data-event-hub-overview.md +++ b/data-explorer/ingest-data-event-hub-overview.md @@ -9,7 +9,7 @@ ms.date: 08/26/2025 [Azure Event Hubs](/azure/event-hubs/event-hubs-about) is a big data streaming platform and event ingestion service. Azure Data Explorer offers continuous ingestion from customer-managed Event Hubs. -The Event Hubs ingestion pipeline transfers events to Azure Data Explorer in several steps. First you create an event hub in the Azure portal. Then create a target table in Azure Data Explorer into which the [data in a particular format](#data-format), is ingested using the provided [ingestion properties](#ingestion-properties). The Event Hubs connection needs to be aware of [events routing](#events-routing). Data can be embedded with selected properties according to the [event system properties](#event-hubs-system-properties-mapping). Create a connection to Event Hubs to [create an event hub](#create-event-hubs) and [send events](#send-events). This process can be managed through the [Azure portal](create-event-hubs-connection.md?tabs=portalADX), programmatically with [C#](create-event-hubs-connection-sdk.md?tabs=c-sharp) or [Python](create-event-hubs-connection-sdk.md?tabs=python), or with the [Azure Resource Manager template](create-event-hubs-connection.md?tabs=arm-template). +The Event Hubs ingestion pipeline transfers events to Azure Data Explorer in several steps. First you create an event hub in the Azure portal. Then create a target table in Azure Data Explorer into which the [data in a particular format](#data-format), is ingested using the provided [ingestion properties](#ingestion-properties). The Event Hubs connection needs to be aware of [events routing](#events-routing). Data can be embedded with selected properties according to the [event system properties](#event-hubs-system-properties-mapping). Create a connection to Event Hubs to [create an event hub](#create-event-hub) and [send events](#send-events). This process can be managed through the [Azure portal](create-event-hubs-connection.md?tabs=portalADX), programmatically with [C#](create-event-hubs-connection-sdk.md?tabs=c-sharp) or [Python](create-event-hubs-connection-sdk.md?tabs=python), or with the [Azure Resource Manager template](create-event-hubs-connection.md?tabs=arm-template). For general information about data ingestion in Azure Data Explorer, see [Azure Data Explorer data ingestion overview](ingest-data-overview.md). From 847281bea4e763afa3f1fc0dbbafae0804c6a22f Mon Sep 17 00:00:00 2001 From: Sreedhar Pelluru <6722422+spelluru@users.noreply.github.com> Date: Tue, 26 Aug 2025 17:36:52 -0400 Subject: [PATCH 3/3] Acrolynx --- data-explorer/start-for-free-event-hubs.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/data-explorer/start-for-free-event-hubs.md b/data-explorer/start-for-free-event-hubs.md index 5c12b73ef1..54b140ad00 100644 --- a/data-explorer/start-for-free-event-hubs.md +++ b/data-explorer/start-for-free-event-hubs.md @@ -34,7 +34,7 @@ Use the following steps to create an Event Hubs data connection in your free clu 1. Select the **Data connections** tab, and then select **Ingest from Event Hubs**. The **Ingest data** window opens with the **Destination** tab selected. - :::image type="content" source="media/start-for-free-event-hubs/start-for-free-create-event-hubs-data-connection.png" alt-text="Screenshot of the data connections tab, showing the ingest from Event Hubs option." lightbox="media/start-for-free-event-hubs/start-for-free-create-event-hubs-data-connection.png"::: + :::image type="content" source="media/start-for-free-event-hubs/start-for-free-create-event-hubs-data-connection.png" alt-text="Screenshot of the data connections tab, showing the ingestion from Event Hubs option." lightbox="media/start-for-free-event-hubs/start-for-free-create-event-hubs-data-connection.png"::: 1. Fill out the destination details using the information in [Destination tab](create-event-hubs-connection.md?tabs=portalEH#create-an-event-hub-data-connection), and then select **Next**. 1. Fill out the source details using the information in Source tab, and then select **Next**. @@ -43,7 +43,7 @@ Use the following steps to create an Event Hubs data connection in your free clu 1. Select **Close** to return to the **My cluster** page. 1. Select the **Data connections** tab, and verify that the connection appears and the status is **Connected**. - :::image type="content" source="media/start-for-free-event-hubs/start-for-free-verify-event-hubs-data-connection.png" alt-text="Screenshot of the data connections tab, showing the ingest from Event Hubs connection is connected." lightbox="media/start-for-free-event-hubs/start-for-free-verify-event-hubs-data-connection.png"::: + :::image type="content" source="media/start-for-free-event-hubs/start-for-free-verify-event-hubs-data-connection.png" alt-text="Screenshot of the data connections tab, showing the ingestion from Event Hubs connection is connected." lightbox="media/start-for-free-event-hubs/start-for-free-verify-event-hubs-data-connection.png"::: ## View data connection details @@ -51,14 +51,14 @@ To view data connection details: 1. In the **Data connections** tab, select the data connection name. - :::image type="content" source="media/start-for-free-event-hubs/start-for-free-view-event-hubs-data-connection-details.png" alt-text="Screenshot of the data connections tab, showing the ingest from Event Hubs connection details pane." lightbox="media/start-for-free-event-hubs/start-for-free-view-event-hubs-data-connection-details.png"::: + :::image type="content" source="media/start-for-free-event-hubs/start-for-free-view-event-hubs-data-connection-details.png" alt-text="Screenshot of the data connections tab, showing the ingestion from Event Hubs connection details pane." lightbox="media/start-for-free-event-hubs/start-for-free-view-event-hubs-data-connection-details.png"::: -1. Optionally, select field dropdowns to view additional details. +1. Optionally, select field dropdowns to view more details. 1. Select **Close** to return to the **Data connections** tab. ## Reconnect a data connection -If there is a connectivity issue with a connecting, its status in the **Data connections** tab will be **Disconnected**. The issue can result from the regeneration of the event hub account keys, or the deletion of the event hub. +If there's a connectivity issue with a connecting, its status in the **Data connections** tab is set to **Disconnected**. The issue can result from the regeneration of the event hub account keys, or the deletion of the event hub. Use the following tab to determine how to resolve the issue: