Skip to content

Commit d9f4d58

Browse files
committed
updated articles
1 parent 63436f7 commit d9f4d58

File tree

3 files changed

+21
-13
lines changed

3 files changed

+21
-13
lines changed

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

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -23,18 +23,11 @@ With managed identities, the Azure platform manages this runtime identity. You d
2323

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

26-
## Event Hubs roles and permissions
27-
28-
You can only add a managed identity to the "Owner" or "Contributor" roles of an Event Hubs namespace, which grants the identity full control on all entities in the namespace. However, management operations that change the namespace topology are initially supported only though Azure Resource Manager. It's not through the native Event Hubs REST management interface. This support also means that you cannot use the .NET Framework client [NamespaceManager](/dotnet/api/microsoft.servicebus.namespacemanager) object within a managed identity.
29-
30-
3126
## Event Hubs roles and permissions
3227
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.
3328

3429
>[!IMPORTANT]
35-
> We earlier supported adding managed identity to the **Owner** or **Contributor** role.
36-
>
37-
> 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.
30+
> 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.
3831
3932
To use the new built-in role, follow these steps:
4033

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

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: event-hubs
1010
ms.devlang: na
1111
ms.topic: article
1212
ms.custom: seodec18
13-
ms.date: 12/06/2018
13+
ms.date: 05/21/2019
1414
ms.author: shvija
1515

1616
---
@@ -26,12 +26,10 @@ 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-
* [Event Hubs Data Owner (preview)](../role-based-access-control/built-in-roles.md#service-bus-data-owner): 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]
32-
> We earlier supported adding managed identity to the **Owner** or **Contributor** role.
33-
>
34-
> 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.
32+
> 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.
3533
3634

3735
## Use Event Hubs with an Azure AD domain user account

articles/role-based-access-control/built-in-roles.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,7 @@ The following table provides a brief description of each built-in role. Click th
8484
| [DevTest Labs User](#devtest-labs-user) | Lets you connect, start, restart, and shutdown your virtual machines in your Azure DevTest Labs. |
8585
| [DNS Zone Contributor](#dns-zone-contributor) | Lets you manage DNS zones and record sets in Azure DNS, but does not let you control who has access to them. |
8686
| [DocumentDB Account Contributor](#documentdb-account-contributor) | Can manage Azure Cosmos DB accounts. Azure Cosmos DB is formerly known as DocumentDB. |
87+
| [Event Hubs Data Owner](#event-hubs-data-owner) | Allows full access to Azure Event Hubs resources |
8788
| [EventGrid EventSubscription Contributor](#eventgrid-eventsubscription-contributor) | Lets you manage EventGrid event subscription operations. |
8889
| [EventGrid EventSubscription Reader](#eventgrid-eventsubscription-reader) | Lets you read EventGrid event subscriptions. |
8990
| [HDInsight Cluster Operator](#hdinsight-cluster-operator) | Lets you read and modify HDInsight cluster configurations. |
@@ -1404,6 +1405,22 @@ The following table provides a brief description of each built-in role. Click th
14041405
> | **NotDataActions** | |
14051406
> | *none* | |
14061407
1408+
## Event Hubs Data Owner
1409+
1410+
> [!div class="mx-tableFixed"]
1411+
> | | |
1412+
> | --- | --- |
1413+
> | **Description** | Allows for full access to Azure Event Hubs resources. |
1414+
> | **Id** | 090c5cfd-751d-490a-894a-3ce6f1109419 |
1415+
> | **Actions** | |
1416+
> | Microsoft.EventHubs/* | Allows full management access to Event Hubs namespace |
1417+
> | **NotActions** | |
1418+
> | *none* | |
1419+
> | **DataActions** | |
1420+
> | Microsoft.EventHubs/* | Allows full data access to Event Hubs namespace |
1421+
> | **NotDataActions** | |
1422+
> | *none* | |
1423+
14071424
## EventGrid EventSubscription Contributor
14081425
> [!div class="mx-tableFixed"]
14091426
> | | |

0 commit comments

Comments
 (0)