Skip to content

Commit 8487b0b

Browse files
authored
Update articles/event-hubs/event-hubs-capture-managed-identity.md
alt text fix
1 parent 8301fca commit 8487b0b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ You can create a user-assigned managed identity and use it for authenticate and
4040
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.
4141

4242

43-
:::image type="content" source="./media/event-hubs-capture-overview/event-hubs-capture-user-assigned.png" alt-text="Image showing capturing of Event Hubs data into Azure Storage or Azure Data Lake Storage" lightbox="./media/event-hubs-capture-overview/event-hubs-capture-user-assigned.png":::
43+
:::image type="content" source="./media/event-hubs-capture-overview/event-hubs-capture-user-assigned.png" alt-text="Image showing capturing of Event Hubs data into Azure Storage or Azure Data Lake Storage." lightbox="./media/event-hubs-capture-overview/event-hubs-capture-user-assigned.png":::
4444

4545
Then capture agent would use the configured user assigned identity for authentication and authorization with the capture destination.
4646

0 commit comments

Comments
 (0)