Skip to content

Commit 5dc934e

Browse files
committed
H2s
1 parent 8563d9d commit 5dc934e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ With [managed identity](../active-directory/managed-identities-azure-resources/o
2323

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

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

2929
To use system assigned identity, the capture destination must have the required role assignment enabled for the corresponding system assigned identity.
@@ -296,7 +296,7 @@ Here's an example Azure Resource Manager template to configure capturing of data
296296
}
297297
```
298298

299-
### Use a user-assigned managed identity to capture events
299+
## Use a user-assigned managed identity to capture events
300300
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.
301301

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

0 commit comments

Comments
 (0)