Skip to content

Commit e45124b

Browse files
committed
fixing headings
1 parent e21b632 commit e45124b

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ ms.date: 03/20/2024
77

88

99
# Authenticate modes for capturing events to destinations in Azure Event Hubs
10+
1011
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.
1112

1213
## Use managed identity
@@ -17,18 +18,18 @@ Azure Event Hubs allows you to select different authentication modes when captur
1718

1819
You can use system-assigned or user-assigned managed identities with Event Hubs Capture destinations.
1920

20-
## Use a system-assigned managed identity to capture events
21+
### Use a system-assigned managed identity to capture events
2122
System-assigned Managed Identity is automatically created and associated with an Azure resource, which is an Event Hubs namespace in this case.
2223

2324
To use system assigned identity, the capture destination must have the required role assignment enabled for the corresponding system assigned identity.
2425
Then you can select `System Assigned` managed identity option when enabling the capture feature in an event hub.
2526

2627
:::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.":::
2728

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.
2930

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.
3233

3334
```json
3435
{
@@ -290,7 +291,7 @@ Here's an example Azure Resource Manager template to configure capturing of data
290291
}
291292
```
292293

293-
## Use a user-assigned managed identity to capture events
294+
### Use a user-assigned managed identity to capture events
294295
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.
295296

296297
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
300301
Then capture agent would use the configured user assigned identity for authentication and authorization with the capture destination.
301302

302303

303-
### Capturing events to a capture destination in a different subscription
304+
#### Capturing events to a capture destination in a different subscription
304305
The Event Hubs Capture feature also support capturing data to a capture destination in a different subscription with the use of managed identity.
305306

306307
> [!IMPORTANT]

0 commit comments

Comments
 (0)