Skip to content

Commit 9a35df0

Browse files
committed
fixed broken links
1 parent 886ff75 commit 9a35df0

5 files changed

Lines changed: 5 additions & 5 deletions

File tree

articles/app-service/webjobs-sdk-how-to.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@ The following table shows built-in roles that we recommend when you use triggers
158158
[Azure Service Bus Data Receiver]: ../role-based-access-control/built-in-roles.md#azure-service-bus-data-receiver
159159
[Azure Service Bus Data Sender]: ../role-based-access-control/built-in-roles.md#azure-service-bus-data-sender
160160
[Azure Service Bus Data Owner]: ../role-based-access-control/built-in-roles.md#azure-service-bus-data-owner
161-
[role-assignment-scope]: ../service-bus-messaging/service-bus-managed-service-identity.md#resource-scope
161+
[role-assignment-scope]: ../service-bus-messaging/service-bus-managed-service-identity.md#choose-the-resource-scope
162162

163163
#### Connection strings in version 2.*x*
164164

articles/event-grid/deliver-events-using-managed-identity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ To deliver events to event hubs in your Event Hubs namespace using managed ident
3737
To deliver events to Service Bus queues or topics in your Service Bus namespace using managed identity, follow these steps:
3838

3939
1. Enable system-assigned or user-assigned managed identity: [system topics](enable-identity-system-topics.md), [custom topics, and domains](enable-identity-custom-topics-domains.md).
40-
1. [Add the identity to the **Azure Service Bus Data Sender**](../service-bus-messaging/service-bus-managed-service-identity.md#azure-built-in-roles-for-azure-service-bus) role on the Service Bus namespace
40+
1. [Add the identity to the **Azure Service Bus Data Sender**](../service-bus-messaging/service-bus-managed-service-identity.md#assign-a-service-bus-role-to-the-managed-identity) role on the Service Bus namespace
4141
1. [Enable the **Allow trusted Microsoft services to bypass this firewall** setting on your Service Bus namespace](../service-bus-messaging/service-bus-service-endpoints.md#trusted-microsoft-services).
4242
1. [Configure the event subscription](managed-service-identity.md) that uses a Service Bus queue or topic as an endpoint to use the system-assigned or user-assigned managed identity.
4343

articles/service-bus-messaging/jms-developer-guide.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ Each connection factory is an instance of `ConnectionFactory`, `QueueConnectionF
6161
To simplify connecting with Azure Service Bus, these interfaces are implemented through `ServiceBusJmsConnectionFactory`, `ServiceBusJmsQueueConnectionFactory`, or `ServiceBusJmsTopicConnectionFactory` respectively.
6262

6363
> [!IMPORTANT]
64-
> Java applications leveraging JMS 2.0 API can connect to Azure Service Bus using the connection string, or using a `TokenCredential` for leveraging Microsoft Entra backed authentication. When using Microsoft Entra backed authentication, ensure to [assign roles and permissions](service-bus-managed-service-identity.md#azure-built-in-roles-for-azure-service-bus) to the identity as needed.
64+
> Java applications leveraging JMS 2.0 API can connect to Azure Service Bus using the connection string, or using a `TokenCredential` for leveraging Microsoft Entra backed authentication. When using Microsoft Entra backed authentication, ensure to [assign roles and permissions](service-bus-managed-service-identity.md#assign-a-service-bus-role-to-the-managed-identity) to the identity as needed.
6565
6666
# [System Assigned Managed Identity](#tab/system-assigned-managed-identity-backed-authentication)
6767

articles/service-bus-messaging/service-bus-dotnet-multi-tier-app-using-service-bus-queues.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ In this tutorial, you'll use Microsoft Entra authentication to create `ServiceBu
8181
1. [Add the application to the `Service Bus Data Owner` role](/azure/role-based-access-control/role-assignments-portal).
8282
1. Set the `AZURE-CLIENT-ID`, `AZURE-TENANT-ID`, AND `AZURE-CLIENT-SECRET` environment variables. For instructions, see [this article](/dotnet/api/overview/azure/identity-readme#environment-variables).
8383

84-
For a list of Service Bus built-in roles, see [Azure built-in roles for Service Bus](service-bus-managed-service-identity.md#azure-built-in-roles-for-azure-service-bus).
84+
For a list of Service Bus built-in roles, see [Azure built-in roles for Service Bus](service-bus-managed-service-identity.md#assign-a-service-bus-role-to-the-managed-identity).
8585

8686
## Create a namespace
8787

includes/functions-service-bus-permissions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,4 +19,4 @@ You'll need to create a role assignment that provides access to your topics and
1919
[Azure Service Bus Data Sender]: ../articles/role-based-access-control/built-in-roles.md#azure-service-bus-data-sender
2020
[Azure Service Bus Data Owner]: ../articles/role-based-access-control/built-in-roles.md#azure-service-bus-data-owner
2121

22-
[role-assignment-scope]: ../articles/service-bus-messaging/service-bus-managed-service-identity.md#resource-scope
22+
[role-assignment-scope]: ../articles/service-bus-messaging/service-bus-managed-service-identity.md#choose-the-resource-scope

0 commit comments

Comments
 (0)