You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> If it's not the namespace you created, ensure that you're a member of one of these roles on the namespace or the entities you want to send or receive (including peek and purge) operations on:
38
+
> -[Service Bus Data Owner](../role-based-access-control/built-in-roles.md#azure-service-bus-data-owner); Allows both send and receive operations.
39
+
> -[Service Bus Data Sender](../role-based-access-control/built-in-roles.md#azure-service-bus-data-sender); Allows send operations.
40
+
> -[Service Bus Data Receiver](../role-based-access-control/built-in-roles.md#azure-service-bus-data-receiver); Allows receive operations.
41
41
42
42
## Use the Service Bus Explorer
43
43
@@ -223,11 +223,6 @@ After peeking or receiving a message, we can resend it, which will send a copy o
223
223
224
224
## Switch authentication type
225
225
226
-
> [!NOTE]
227
-
> To use Microsoft Entra ID (Azure Active Directory) authentication the following are required:
228
-
> - The user/service principal is assigned the 'Azure Service Bus Data Owner' role. No other built in or customer roles are supported.
229
-
> - The 'Azure Service Bus Data Owner' role has to be assigned at the namespace scope. Assignment at queue or topic scope is not supported.
230
-
231
226
When working with Service Bus Explorer, it's possible to use either **Access Key** or **Microsoft Entra ID** authentication.
0 commit comments