Skip to content

Commit 225d978

Browse files
committed
minor updates
1 parent d9f4d58 commit 225d978

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,16 +24,16 @@ With managed identities, the Azure platform manages this runtime identity. You d
2424
Once it is associated with a managed identity, an Event Hubs client can do all authorized operations. Authorization is granted by associating a managed identity with Event Hubs roles.
2525

2626
## Event Hubs roles and permissions
27-
You can add a managed identity to the **Event Hubs Data Owner** role of an Event Hubs namespace. It grants the identity, full control (for management and data operations) on all entities in the namespace.
27+
You can add a managed identity to the **Event Hubs Data Owner** role of an Event Hubs namespace. This role grants the identity, full control (for management and data operations) on all entities in the namespace.
2828

2929
>[!IMPORTANT]
3030
> We earlier supported adding managed identity to the **Owner** or **Contributor** role. However, data access privileges for **Owner** and **Contributor** role are no longer honored. If you are using the **Owner** or **Contributor** role, switch to using the **Event Hubs Data Owner** role.
3131
3232
To use the new built-in role, follow these steps:
3333

3434
1. Navigate to the [Azure portal](https://portal.azure.com)
35-
2. Navigate to the Event Hubs namespace where you have currently setup the **Owner** or **Contributor** role.
36-
3. Select **Access Control(IAM)** from the left menu.
35+
2. Navigate to the Event Hubs namespace.
36+
3. On the **Event Hubs Namespace** page, select **Access Control(IAM)** from the left menu.
3737
4. On the **Access Control (IAM)** page, select **Add** in the **Add a role assignment** section.
3838

3939
![Add a role assignment button](./media/event-hubs-managed-service-identity/add-role-assignment-button.png)

articles/event-hubs/event-hubs-role-based-access-control.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ An application that uses Azure AD RBAC does not need to handle SAS rules and key
2626
## Event Hubs roles and permissions
2727
Azure provides the following built-in RBAC roles for authorizing access to an Event Hubs namespace:
2828

29-
The [Event Hubs Data Owner (preview)](../role-based-access-control/built-in-roles.md#service-bus-data-owner) role enables data access to an Event Hubs namespace and its entities (queues, topics, subscriptions, and filters)
29+
The [Event Hubs Data Owner (Preview)](../role-based-access-control/built-in-roles.md#service-bus-data-owner) role enables data access to an Event Hubs namespace and its entities (queues, topics, subscriptions, and filters)
3030

3131
>[!IMPORTANT]
3232
> We earlier supported adding managed identity to the **Owner** or **Contributor** role. However, data access privileges for **Owner** and **Contributor** role are no longer honored. If you are using the **Owner** or **Contributor** role, switch to using the **Event Hubs Data Owner** role.

0 commit comments

Comments
 (0)