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
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,7 @@ ms.date: 03/20/2024
7
7
8
8
9
9
# Authenticate modes for capturing events to destinations in Azure Event Hubs
10
+
10
11
Azure Event Hubs allows you to select different authentication modes when capturing events to a destination such as [Azure Blob storage](https://azure.microsoft.com/services/storage/blobs/) or [Azure Data Lake Storage Gen 1 or Gen 2](https://azure.microsoft.com/services/data-lake-store/) account of your choice. The authentication mode determines how the capture agent running in Event Hubs authenticate with the capture destination.
11
12
12
13
## Use managed identity
@@ -17,18 +18,18 @@ Azure Event Hubs allows you to select different authentication modes when captur
17
18
18
19
You can use system-assigned or user-assigned managed identities with Event Hubs Capture destinations.
19
20
20
-
## Use a system-assigned managed identity to capture events
21
+
###Use a system-assigned managed identity to capture events
21
22
System-assigned Managed Identity is automatically created and associated with an Azure resource, which is an Event Hubs namespace in this case.
22
23
23
24
To use system assigned identity, the capture destination must have the required role assignment enabled for the corresponding system assigned identity.
24
25
Then you can select `System Assigned` managed identity option when enabling the capture feature in an event hub.
25
26
26
27
:::image type="content" source="./media/event-hubs-capture-overview/event-hubs-captute-system-assigned.png" alt-text="Image showing capturing of Event Hubs data into Azure Storage or Azure Data Lake Storage using System Assigned managed identity.":::
27
28
28
-
Then capture agent would use the identity of the namespace for authentication and authorization with the capture destination.
29
+
Then capture agent would use the identity of the namespace for authentication and authorization with the capture destination.
29
30
30
-
### Azure Resource Manager template
31
-
Here's an example Azure Resource Manager template to configure capturing of data using a system-assigned managed identity.
31
+
####Azure Resource Manager template
32
+
Here's an example Azure Resource Manager (ARM) template to configure capturing of data using a system-assigned managed identity.
32
33
33
34
```json
34
35
{
@@ -290,7 +291,7 @@ Here's an example Azure Resource Manager template to configure capturing of data
290
291
}
291
292
```
292
293
293
-
## Use a user-assigned managed identity to capture events
294
+
###Use a user-assigned managed identity to capture events
294
295
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.
295
296
296
297
Then you can select `User Assigned` managed identity option when enabling the capture feature in an event hub and assign the required user assigned identity when enabling the capture feature.
@@ -300,7 +301,7 @@ Then you can select `User Assigned` managed identity option when enabling the ca
300
301
Then capture agent would use the configured user assigned identity for authentication and authorization with the capture destination.
301
302
302
303
303
-
### Capturing events to a capture destination in a different subscription
304
+
####Capturing events to a capture destination in a different subscription
304
305
The Event Hubs Capture feature also support capturing data to a capture destination in a different subscription with the use of managed identity.
0 commit comments