Skip to content

Commit 24352a0

Browse files
authored
Merge pull request #217680 from spelluru/sbusqstopics1108
make connection string option default
2 parents 464265a + b7f7237 commit 24352a0

10 files changed

+208
-184
lines changed

includes/passwordless/service-bus/service-bus-assign-roles.md renamed to articles/service-bus-messaging/includes/service-bus-assign-roles.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ The following example assigns the `Azure Service Bus Data Owner` role to your us
1818
For Azure Service Bus, the management of namespaces and all related resources through the Azure portal and the Azure resource management API is already protected using the Azure RBAC model. Azure provides the below Azure built-in roles for authorizing access to a Service Bus namespace:
1919

2020
- [Azure Service Bus Data Owner](../../../articles/role-based-access-control/built-in-roles.md#azure-service-bus-data-owner): Enables data access to Service Bus namespace and its entities (queues, topics, subscriptions, and filters)
21-
- [Azure Service Bus Data Sender](../../../articles/role-based-access-control/built-in-roles.md#azure-service-bus-data-sender): Use this role to give send access to Service Bus namespace and its entities.
22-
- [Azure Service Bus Data Receiver](../../../articles/role-based-access-control/built-in-roles.md#azure-service-bus-data-receiver): Use this role to give receiving access to Service Bus namespace and its entities.
21+
- [Azure Service Bus Data Sender](../../../articles/role-based-access-control/built-in-roles.md#azure-service-bus-data-sender): Use this role to give the send access to Service Bus namespace and its entities.
22+
- [Azure Service Bus Data Receiver](../../../articles/role-based-access-control/built-in-roles.md#azure-service-bus-data-receiver): Use this role to give the receive access to Service Bus namespace and its entities.
2323

2424
If you want to create a custom role, see [Rights required for Service Bus operations](../../../articles/service-bus-messaging/service-bus-sas.md#rights-required-for-service-bus-operations).
2525

@@ -36,7 +36,7 @@ If you want to create a custom role, see [Rights required for Service Bus operat
3636

3737
4. Select **+ Add** from the top menu and then **Add role assignment** from the resulting drop-down menu.
3838

39-
:::image type="content" source="media/add-role.png" alt-text="A screenshot showing how to assign a role.":::
39+
:::image type="content" source="media/service-bus-assign-roles/add-role.png" alt-text="A screenshot showing how to assign a role.":::
4040

4141
5. Use the search box to filter the results to the desired role. For this example, search for `Azure Service Bus Data Owner` and select the matching result. Then choose **Next**.
4242

articles/service-bus-messaging/includes/service-bus-create-namespace-portal.md

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -46,15 +46,3 @@ To create a namespace:
4646

4747
:::image type="content" source="./media/service-bus-create-namespace-portal/service-bus-namespace-home-page.png" lightbox="./media/service-bus-create-namespace-portal/service-bus-namespace-home-page.png" alt-text="Image showing the home page of the Service Bus namespace created." :::
4848

49-
## Get the connection string
50-
Creating a new namespace automatically generates an initial Shared Access Signature (SAS) policy with primary and secondary keys, and primary and secondary connection strings that each grant full control over all aspects of the namespace. See [Service Bus authentication and authorization](../service-bus-authentication-and-authorization.md) for information about how to create rules with more constrained rights for regular senders and receivers.
51-
52-
A client can use the connection string to connect to the Service Bus namespace. To copy the primary connection string for your namespace, follow these steps:
53-
54-
1. On the **Service Bus Namespace** page, select **Shared access policies** on the left menu.
55-
3. On the **Shared access policies** page, select **RootManageSharedAccessKey**.
56-
4. In the **Policy: RootManageSharedAccessKey** window, select the copy button next to **Primary Connection String**, to copy the connection string to your clipboard for later use. Paste this value into Notepad or some other temporary location.
57-
58-
:::image type="content" source="./media/service-bus-create-namespace-portal/connection-string.png" lightbox="./media/service-bus-create-namespace-portal/connection-string.png" alt-text="Screenshot shows an S A S policy called RootManageSharedAccessKey, which includes keys and connection strings.":::
59-
60-
You can use this page to copy primary key, secondary key, primary connection string, and secondary connection string.
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
---
2+
title: "include file"
3+
description: "include file"
4+
services: storage
5+
author: alexwolfmsft
6+
ms.service: storage
7+
ms.topic: include
8+
ms.date: 09/09/2022
9+
ms.author: alexwolf
10+
ms.custom: include file
11+
---
12+
13+
14+
15+
## [Connection String](#tab/connection-string)
16+
17+
## Get the connection string
18+
Creating a new namespace automatically generates an initial Shared Access Signature (SAS) policy with primary and secondary keys, and primary and secondary connection strings that each grant full control over all aspects of the namespace. See [Service Bus authentication and authorization](../service-bus-authentication-and-authorization.md) for information about how to create rules with more constrained rights for regular senders and receivers.
19+
20+
A client can use the connection string to connect to the Service Bus namespace. To copy the primary connection string for your namespace, follow these steps:
21+
22+
1. On the **Service Bus Namespace** page, select **Shared access policies** on the left menu.
23+
3. On the **Shared access policies** page, select **RootManageSharedAccessKey**.
24+
4. In the **Policy: RootManageSharedAccessKey** window, select the copy button next to **Primary Connection String**, to copy the connection string to your clipboard for later use. Paste this value into Notepad or some other temporary location.
25+
26+
:::image type="content" source="./media/service-bus-create-namespace-portal/connection-string.png" lightbox="./media/service-bus-create-namespace-portal/connection-string.png" alt-text="Screenshot shows an SAS policy called RootManageSharedAccessKey, which includes keys and connection strings.":::
27+
28+
You can use this page to copy primary key, secondary key, primary connection string, and secondary connection string.
29+
30+
31+
## [Passwordless](#tab/passwordless)
32+
33+
## Authenticate the app to Azure
34+
35+
[!INCLUDE [passwordless-overview](../../../includes/passwordless/passwordless-overview.md)]
36+
37+
[!INCLUDE [passwordless-default-azure-credential-overview](../../../includes/passwordless/dotnet-default-azure-credential-overview.md)]
38+
39+
### Assign roles to your Azure AD user
40+
41+
[!INCLUDE [service-bus-assign-roles](service-bus-assign-roles.md)]
42+
43+
### Sign in and add the Azure Identity package
44+
45+
You can authorize access to the service bus namespace using the following steps:
46+
47+
[!INCLUDE [default-azure-credential-sign-in](../../../includes/passwordless/default-azure-credential-sign-in.md)]
48+
49+
[!INCLUDE [visual-studio-add-identity](../../../includes/passwordless/visual-studio-add-identity.md)]
50+
51+
52+
---

0 commit comments

Comments
 (0)