Skip to content

Commit 8301fca

Browse files
committed
Enable identity for event hub capture
1 parent aaa5b0d commit 8301fca

File tree

5 files changed

+25
-342
lines changed

5 files changed

+25
-342
lines changed

articles/event-hubs/enable-managed-identity.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: Enable managed identity for a namespace
33
description: Learn how to enable a system-assigned or user-assigned managed identity for an Azure Event Hubs namespace.
44
ms.topic: how-to
55
ms.date: 01/29/2025
6+
# Customer intent: As a developer or administrator, I want to learn how to enable managed identity for an Azure Event Hubs namespace.
67
---
78

89
# Enable managed identity for an Azure Event Hubs namespace
@@ -39,4 +40,4 @@ Here are the steps to enable a user-assigned managed identity for an Event Hubs
3940
:::image type="content" source="./media/enable-managed-identity/select-user-assigned-identity.png" alt-text="Screenshot that shows the selection of a user assigned identity." :::
4041

4142
## Related content
42-
After you enable managed identity for your Event Hubs namespace, grant the identity appropriate role on a target resource. For example, if you want to enable capturing of event data on an event hub using a managed identity, the managed identity should be added to the **Storage Blob Data Contributor** role on the Azure storage account. For more information on using identities for capturing event data, see [Authenticate modes for capturing events to destinations in Azure Event Hubs](event-hubs-capture-managed-identity.md).
43+
After you enable managed identity for your Event Hubs namespace, grant the identity appropriate role on a target resource. For example, if you want to enable capturing of event data on an event hub using a managed identity, the managed identity should be added to the **Storage Blob Data Contributor** role on the Azure storage or Data Lake Store account. For more information on using identities for capturing event data, see [Authenticate modes for capturing events to destinations in Azure Event Hubs](event-hubs-capture-managed-identity.md).

articles/event-hubs/event-hubs-capture-enable-through-portal.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,8 @@ Azure [Event Hubs Capture][capture-overview] enables you to automatically delive
1616
## Prerequisites
1717

1818
- An Azure subscription. If you don't have one, [create a free account](https://azure.microsoft.com/free/) before you begin.
19-
- If you are new to Azure Event Hubs, read through [Event Hubs overview](event-hubs-about.md) and [Event Hubs features](event-hubs-features.md).
19+
- If you're new to Azure Event Hubs, read through [Event Hubs overview](event-hubs-about.md) and [Event Hubs features](event-hubs-features.md).
20+
- Learn about Event Hubs capture by reading the [Event Hubs Capture overview][capture-overview].
2021

2122
> [!IMPORTANT]
2223
> Event Hubs only supports **Premium** Storage account with **Block Blob** support.
@@ -44,7 +45,7 @@ See one of the following sections based on the type of storage you want to use t
4445

4546

4647
> [!IMPORTANT]
47-
> Azure Data Lake Storage Gen1 is retired, so don't use it for capturing event data. For more information, see the [official announcement](https://azure.microsoft.com/updates/action-required-switch-to-azure-data-lake-storage-gen2-by-29-february-2024/). If you are using Azure Data Lake Storage Gen1, migrate to Azure Data Lake Storage Gen2. For more information, see [Azure Data Lake Storage migration guidelines and patterns](../storage/blobs/data-lake-storage-migrate-gen1-to-gen2.md).
48+
> Azure Data Lake Storage Gen1 is retired, so don't use it for capturing event data. For more information, see the [official announcement](https://azure.microsoft.com/updates/action-required-switch-to-azure-data-lake-storage-gen2-by-29-february-2024/). If you're using Azure Data Lake Storage Gen1, migrate to Azure Data Lake Storage Gen2. For more information, see [Azure Data Lake Storage migration guidelines and patterns](../storage/blobs/data-lake-storage-migrate-gen1-to-gen2.md).
4849
4950
## Capture data to Azure Storage
5051

@@ -110,9 +111,10 @@ You can configure Capture on existing event hubs that are in Event Hubs namespac
110111
- [Capture data to Azure Data Lake Storage Gen 2](#capture-data-to-azure-data-lake-storage-gen-2)
111112

112113
## Related content
114+
You can use a system-assigned or a user-assigned managed identity when capturing event data. First, you enable a managed identity for a namespace, grant the identity an appropriate role on the target storage for capturing events, and then configure the event hub to capture events using the managed identity. For more information, see the following articles:
115+
116+
- [Enable managed identity for a namespace](enable-managed-identity.md).
117+
- [Use a managed identity to capture events](event-hubs-capture-managed-identity.md)
113118

114-
- Learn more about Event Hubs capture by reading the [Event Hubs Capture overview][capture-overview].
115-
- You can also configure Event Hubs Capture using Azure Resource Manager templates. For more information, see [Enable Capture using an Azure Resource Manager template](event-hubs-resource-manager-namespace-event-hub-enable-capture.md).
116-
- [Learn how to create an Azure Event Grid subscription with an Event Hubs namespace as its source](store-captured-data-data-warehouse.md)
117119

118120
[capture-overview]: event-hubs-capture-overview.md

0 commit comments

Comments
 (0)