Skip to content

Commit bc9f6fd

Browse files
committed
Update
1 parent b9fe1cf commit bc9f6fd

File tree

1 file changed

+2
-4
lines changed

1 file changed

+2
-4
lines changed

articles/service-bus-messaging/service-bus-authentication-and-authorization.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Service Bus authentication and authorization
33
description: Learn how to securely authenticate and authorize access to Azure Service Bus, including best practices for managing access keys and using Microsoft Entra ID.
44
ms.topic: article
5-
ms.date: 02/23/2024
5+
ms.date: 03/21/2025
66
---
77

88
# Service Bus authentication and authorization
@@ -13,8 +13,6 @@ There are two ways to authenticate and authorize access to Azure Service Bus res
1313

1414
This article gives you details on using these two types of security mechanisms.
1515

16-
<a name='azure-active-directory'></a>
17-
1816
## Microsoft Entra ID
1917
Microsoft Entra integration with Service Bus provides role-based access control (RBAC) to Service Bus resources. You can use Azure RBAC to grant permissions to a security principal, which can be a user, a group, an application service principal, or a managed identity. Microsoft Entra authenticates the security principal and returns an OAuth 2.0 token. This token can be used to authorize a request to access a Service Bus resource (queue, topic, and subscription).
2018

@@ -27,7 +25,7 @@ For more information about authenticating with Microsoft Entra ID, see the follo
2725
> [Service Bus REST API](/rest/api/servicebus/) supports OAuth authentication with Microsoft Entra ID.
2826
2927
> [!IMPORTANT]
30-
> Authorizing users or applications using OAuth 2.0 token returned by Microsoft Entra ID provides superior security and ease of use over shared access signatures (SAS). With Microsoft Entra ID, there is no need to store tokens in your code and risk potential security vulnerabilities. We recommend that you use Microsoft Entra ID with your Azure Service Bus applications when possible.
28+
> Authorizing users or applications using OAuth 2.0 token returned by Microsoft Entra ID provides superior security and ease of use over shared access signatures (SAS). With Microsoft Entra ID, there's no need to store tokens in your code and risk potential security vulnerabilities. We recommend that you use Microsoft Entra ID with your Azure Service Bus applications when possible.
3129
>
3230
> You can disable local or SAS key authentication for a Service Bus namespace and allow only Microsoft Entra authentication. For step-by-step instructions, see [Disable local authentication](disable-local-authentication.md).
3331

0 commit comments

Comments
 (0)