Skip to content

Commit 883b3e2

Browse files
committed
fixed broken link
1 parent 9f2e1f9 commit 883b3e2

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/service-bus-messaging/service-bus-managed-service-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ Before you assign an RBAC role to a security principal, determine the scope of a
5252

5353
The following list describes the levels at which you can scope access to Service Bus resources, starting with the narrowest scope:
5454

55-
- **Queue**, **topic**, or **subscription**: Role assignment applies to the specific Service Bus entity. Currently, the Azure portal doesn't support assigning users/groups/managed identities to Service Bus RBAC roles at the subscription level. Here's an example of using the Azure CLI command: [az-role-assignment-create](../cli/azure/role/assignment?view=azure-cli-latest#az-role-assignment-create) to assign an identity to a Service Bus RBAC role:
55+
- **Queue**, **topic**, or **subscription**: Role assignment applies to the specific Service Bus entity. Currently, the Azure portal doesn't support assigning users/groups/managed identities to Service Bus RBAC roles at the subscription level. Here's an example of using the Azure CLI command: [az-role-assignment-create](/cli/azure/role/assignment?view=azure-cli-latest#az-role-assignment-create) to assign an identity to a Service Bus RBAC role:
5656

5757
```powershell
5858
az role assignment create \

0 commit comments

Comments
 (0)