You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/event-hubs/event-hubs-capture-managed-identity.md
+264-2Lines changed: 264 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Use managed Identities to capture Azure Event Hubs events
3
3
description: This article explains how to use managed identities to capture events to a destination such as Azure Blob Storage and Azure Data Lake Storage.
4
4
ms.topic: article
5
-
ms.date: 05/23/2023
5
+
ms.date: 03/20/2024
6
6
---
7
7
8
8
@@ -14,7 +14,7 @@ The default authentication method is to use Shared Access Signature(SAS) to acce
14
14
15
15
:::image type="content" source="./media/event-hubs-capture-overview/event-hubs-capture-default.png" alt-text="Image showing capturing of Event Hubs data into Azure Storage or Azure Data Lake Storage using default SAS authentication mode":::
16
16
17
-
With this approach, you can capture data to destinations resources that are in the same subscription only.
17
+
With this approach, you can capture data to destinations resources that are in the **same subscription** only.
18
18
19
19
## Use Managed Identity
20
20
With [managed identity](../active-directory/managed-identities-azure-resources/overview.md), users can seamlessly capture data to a preferred destination by using Microsoft Entra ID based authentication and authorization.
@@ -33,6 +33,268 @@ Then you can select `System Assigned` managed identity option when enabling the
33
33
34
34
Then capture agent would use the identity of the namespace for authentication and authorization with the capture destination.
35
35
36
+
### Azure Resource Manager template
37
+
Here's an example Azure Resource Manager template to configure capturing of data using a system-assigned managed identity.
"description": "A Capture Name Format must contain {Namespace}, {EventHub}, {PartitionId}, {Year}, {Month}, {Day}, {Hour}, {Minute} and {Second} fields. These can be arranged in any order with or without delimiters. E.g. Prod_{EventHub}/{Namespace}\\{PartitionId}_{Year}_{Month}/{Day}/{Hour}/{Minute}/{Second}"
94
+
}
95
+
},
96
+
"existingStgSubId": {
97
+
"type": "String",
98
+
"metadata": {
99
+
"description": "The ID of the Azure subscription that has your existing storage account."
100
+
}
101
+
},
102
+
"existingStgAccRG": {
103
+
"type": "String",
104
+
"metadata": {
105
+
"description": "The resource group that has the storage account."
### Use a user-assigned managed identity to capture events
38
300
You can create a user-assigned managed identity and use it for authenticate and authorize with the capture destination of Event hubs. Once the managed identity is created, you can assign it to the Event Hubs namespace and make sure that the capture destination has the required role assignment enabled for the corresponding user assigned identity.
0 commit comments