Merge pull request #226095 from spelluru/tutorialfix0202-2

missing instructions to get connection string

Author: v-shils

articles/service-bus-messaging/includes/get-namespace-connection-string.md

@@ -0,0 +1,24 @@
+---
+ title: include file
+ description: include file
+ services: service-bus-messaging
+ author: spelluru
+ ms.service: service-bus-messaging
+ ms.topic: include
+ ms.date: 02/02/2022
+ ms.author: spelluru
+ ms.custom: include file
+---
+
+## Get connection string to the namespace (Azure portal)
+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. 
+
+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: 
+
+1. On the **Service Bus Namespace** page, select **Shared access policies** on the left menu.
+3. On the **Shared access policies** page, select **RootManageSharedAccessKey**.
+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.
+
+    :::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.":::
+
+    You can use this page to copy primary key, secondary key, primary connection string, and secondary connection string. 

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

@@ -11,7 +11,7 @@ ms.custom: devx-track-csharp
 
 Developing for Microsoft Azure is easy using Visual Studio and the free Azure SDK for .NET. This tutorial walks you through the steps to create an application that uses multiple Azure resources running in your local environment.
 
-You will learn the following:
+You'll learn the following:
 
 * How to enable your computer for Azure development with a
   single download and install.
@@ -22,7 +22,7 @@ You will learn the following:
 
 [!INCLUDE [create-account-note](../../includes/create-account-note.md)]
 
-In this tutorial, you'll build and run the multi-tier application in an Azure cloud service. The front end is an ASP.NET MVC web role and the back end is a worker-role that uses a Service Bus queue. You can create the same multi-tier application with the front end as a web project, that is deployed to an Azure website instead of a cloud service. You can also try out the [.NET on-premises/cloud hybrid application](../azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md) tutorial.
+In this tutorial, you'll build and run the multi-tier application in an Azure cloud service. The front end is an ASP.NET MVC web role and the back end is a worker-role that uses a Service Bus queue. You can create the same multi-tier application with the front end as a web project that is deployed to an Azure website instead of a cloud service. You can also try out the [.NET on-premises/cloud hybrid application](../azure-relay/service-bus-dotnet-hybrid-app-using-service-bus-relay.md) tutorial.
 
 The following screenshot shows the completed application.
 
@@ -36,7 +36,7 @@ the communication between the tiers.
 
 Using Service Bus messaging between the web and middle tiers decouples the
 two components. In contrast to direct messaging (that is, TCP or HTTP),
-the web tier does not connect to the middle tier directly; instead it
+the web tier doesn't connect to the middle tier directly; instead it
 pushes units of work, as messages, into Service Bus, which reliably
 retains them until the middle tier is ready to consume and process them.
 
@@ -49,19 +49,12 @@ configured with filter rules that restrict the set of messages passed to
 the subscription queue to those that match the filter. The following example uses
 Service Bus queues.
 
-:::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-100.png" alt-text="Diagram showing the communication between the Web Role, the Service Bus, and the Worker Role.":::
+:::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-100.png" alt-text="Diagram showing the communication between the Web Role, Service Bus, and the Worker Role.":::
 
 This communication mechanism has several advantages over direct
 messaging:
 
-* **Temporal decoupling.** With the asynchronous messaging pattern,
-  producers and consumers need not be online at the same time. Service
-  Bus reliably stores messages until the consuming party is ready to
-  receive them. This enables the components of the distributed
-  application to be disconnected, either voluntarily, for example, for
-  maintenance, or due to a component crash, without impacting the
-  system as a whole. Furthermore, the consuming application might only
-  need to come online during certain times of the day.
+* **Temporal decoupling.**  When you use the asynchronous messaging pattern, producers and consumers don't need to be online at the same time. Service  Bus reliably stores messages until the consuming party is ready to receive them. This enables the components of the distributed application to be disconnected, either voluntarily, for example, for maintenance, or due to a component crash, without impacting the system as a whole. Furthermore, the consuming application might only need to come online during certain times of the day.
 * **Load leveling.** In many applications, system load varies over
   time, while the processing time required for each unit of work is
   typically constant. Intermediating message producers and consumers
@@ -73,7 +66,7 @@ messaging:
   added to read from the queue. Each message is processed by only one
   of the worker processes. Furthermore, this pull-based load balancing
   enables optimal use of the worker machines even if the
-  worker machines differ in terms of processing power, as they will
+  worker machines differ in terms of processing power, as they'll
   pull messages at their own maximum rate. This pattern is often
   termed the *competing consumer* pattern.
 
@@ -95,6 +88,8 @@ The first step is to create a *namespace*, and obtain a [Shared Access Signature
 
 [!INCLUDE [service-bus-create-namespace-portal](./includes/service-bus-create-namespace-portal.md)]
 
+[!INCLUDE [get-namespace-connection-string](./includes/get-namespace-connection-string.md)]
+
 ## Create a web role
 
 In this section, you build the front end of your application. First, you
@@ -105,12 +100,12 @@ queue and displays status information about the queue.
 ### Create the project
 
 1. Using administrator privileges, start Visual
-   Studio: right-click the **Visual Studio** program icon, and then click **Run as administrator**. The Azure Compute Emulator,
+   Studio: right-click the **Visual Studio** program icon, and then select **Run as administrator**. The Azure Compute Emulator,
    discussed later in this article, requires that Visual Studio be
    started with administrator privileges.
 
-   In Visual Studio, on the **File** menu, click **New**, and then
-   click **Project**.
+   In Visual Studio, on the **File** menu, select **New**, and then
+   select **Project**.
 2. On the **Templates** page, follow these steps:
     1. Select **C#** for programming language.
     1. Select **Cloud** for the project type.
@@ -124,24 +119,24 @@ queue and displays status information about the queue.
 1. On the **Roles** page, double-click **ASP.NET Web  Role**, and select **OK**. 
 
     :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-11.png" alt-text="Select Web Role":::
-4. Hover over **WebRole1** under **Azure Cloud Service solution**, click
-   the pencil icon, and rename the web role to **FrontendWebRole**. Then click **OK**. (Make sure you enter "Frontend" with a lower-case 'e,' not "FrontEnd".)
+4. Hover over **WebRole1** under **Azure Cloud Service solution**, select
+   the pencil icon, and rename the web role to **FrontendWebRole**. Then select **OK**. (Make sure you enter "Frontend" with a lower-case 'e,' not "FrontEnd".)
 
     :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-02.png" alt-text="Screenshot of the New Microsoft Azure Cloud Service dialog box with the solution renamed to FrontendWebRole.":::
 5. In the  **Create a new ASP.NET Web Application** dialog box, select **MVC**, and then select **Create**.
 
     :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-12.png" alt-text="Screenshot of the New ASP.NET Project dialog box with MVC highlighted and outlined in red and the Change Authentication option outlined in red.":::
-8. In **Solution Explorer**, in the **FrontendWebRole** project, right-click **References**, then click
+8. In **Solution Explorer**, in the **FrontendWebRole** project, right-click **References**, then select
    **Manage NuGet Packages**.
-9. Click the **Browse** tab, then search for **Azure.Messaging.ServiceBus**. Select the **Azure.Messaging.ServiceBus** package, select **Install**, and accept the terms of use.
+9. Select the **Browse** tab, then search for **Azure.Messaging.ServiceBus**. Select the **Azure.Messaging.ServiceBus** package, select **Install**, and accept the terms of use.
 
     :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-13.png" alt-text="Screenshot of the Manage NuGet Packages dialog box with the Azure.Messaging.ServiceBus highlighted and the Install option outlined in red.":::
 
    Note that the required client assemblies are now referenced and some new code files have been added.
 10. Follow the same steps to add the `Azure.Identity` NuGet package to the project.  
-10. In **Solution Explorer**, expand **FronendWebRole**, right-click **Models** and click **Add**,
-    then click **Class**. In the **Name** box, type the name
-    **OnlineOrder.cs**. Then click **Add**.
+10. In **Solution Explorer**, expand **FronendWebRole**, right-click **Models** and select **Add**,
+    then select **Class**. In the **Name** box, type the name
+    **OnlineOrder.cs**. Then select **Add**.
 
 ### Write the code for your web role
 In this section, you create the various pages that your application displays.
@@ -222,7 +217,7 @@ In this section, you create the various pages that your application displays.
        }
    }
    ```
-4. From the **Build** menu, click **Build Solution** to test the accuracy of your work so far.
+4. From the **Build** menu, select **Build Solution** to test the accuracy of your work so far.
 5. Now, create the view for the `Submit()` method you
    created earlier. Right-click within the `Submit()` method (the overload of `Submit()` that takes no parameters) in the **HomeController.cs** file, and then choose **Add View**.
 6. In the **Add New Scaffolded Item** dialog box, select **Add**. 
@@ -244,7 +239,7 @@ In this section, you create the various pages that your application displays.
     the queue. In **Solution Explorer**, double-click the
     **Views\Home\Submit.cshtml** file to open it in the Visual Studio
     editor. Add the following line after `<h2>Submit</h2>`. For now,
-    the `ViewBag.MessageCount` is empty. You will populate it later.
+    the `ViewBag.MessageCount` is empty. You'll populate it later.
 
     ```html
     <p>Current number of orders in queue waiting to be processed: @ViewBag.MessageCount</p>
@@ -262,8 +257,8 @@ Global.aspx.cs. Finally, update the submission code you
 created earlier in HomeController.cs to actually submit items to a
 Service Bus queue.
 
-1. In **Solution Explorer**, right-click **FrontendWebRole** (right-click the project, not the role). Click **Add**, and then click **Class**.
-2. Name the class **QueueConnector.cs**. Click **Add** to create the class.
+1. In **Solution Explorer**, right-click **FrontendWebRole** (right-click the project, not the role). Select **Add**, and then select **Class**.
+2. Name the class **QueueConnector.cs**. Select **Add** to create the class.
 3. Now, add code that encapsulates the connection information and initializes the connection to a Service Bus queue. Replace the entire contents of QueueConnector.cs with the following code, and enter values for `your Service Bus namespace` (your namespace name) and `yourKey`, which is the **primary key** you previously obtained from the Azure portal.
 
    ```csharp
@@ -360,25 +355,25 @@ Service Bus queue.
     :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-app2.png" alt-text="Screenshot of the application's Submit page with the message count incremented to 1.":::
 
 ## Create the worker role
-You will now create the worker role that processes the order
+You'll now create the worker role that processes the order
 submissions. This example uses the **Worker Role with Service Bus Queue** Visual Studio project template. You already obtained the required credentials from the portal.
 
 1. Make sure you have connected Visual Studio to your Azure account.
 2. In Visual Studio, in **Solution Explorer** right-click the
    **Roles** folder under the **MultiTierApp** project.
-3. Click **Add**, and then click **New Worker Role Project**. The **Add New Role Project** dialog box appears.
+3. Select **Add**, and then select **New Worker Role Project**. The **Add New Role Project** dialog box appears.
 
    :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/SBNewWorkerRole.png" alt-text="Screenshot of the Solution Explorer pane with the New Worker Role Project option and Add option highlighted.":::
 1. In the **Add New Role Project** dialog box, select **Worker Role**. Don't select **Worker Role with Service Bus Queue** as it generates code that uses the legacy Service Bus SDK. 
 
     :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/SBWorkerRole1.png" alt-text="Screenshot of the Ad New Role Project dialog box with the Worker Role with Service Bus Queue option highlighted and outlined in red.":::
-5. In the **Name** box, name the project **OrderProcessingRole**. Then click **Add**.
+5. In the **Name** box, name the project **OrderProcessingRole**. Then select **Add**.
 1. In **Solution Explorer**, right-click **OrderProcessingRole** project, and select **Manage NuGet Packages**.
 9. Select the **Browse** tab, then search for **Azure.Messaging.ServiceBus**. Select the **Azure.Messaging.ServiceBus** package, select **Install**, and accept the terms of use.
 
     :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-13.png" alt-text="Screenshot of the Manage NuGet Packages dialog box with the Azure.Messaging.ServiceBus highlighted and the Install option outlined in red.":::
 1. Follow the same steps to add the `Azure.Identity` NuGet package to the project.  
-1. Create an **OnlineOrder** class to represent the orders as you process them from the queue. You can reuse a class you have already created. In **Solution Explorer**, right-click the **OrderProcessingRole** class (right-click the class icon, not the role). Click **Add**, then click **Existing Item**.
+1. Create an **OnlineOrder** class to represent the orders as you process them from the queue. You can reuse a class you have already created. In **Solution Explorer**, right-click the **OrderProcessingRole** class (right-click the class icon, not the role). Select **Add**, then select **Existing Item**.
 1. Browse to the subfolder for **FrontendWebRole\Models**, and then double-click **OnlineOrder.cs** to add it to this project.
 1. Add the following `using` statement to the **WorkerRole.cs** file in the **OrderProcessingRole** project. 
 
@@ -455,16 +450,16 @@ submissions. This example uses the **Worker Role with Service Bus Queue** Visual
             }
         }
     ```
-14. You have completed the application. You can test the full
+14. You've completed the application. You can test the full
     application by right-clicking the MultiTierApp project in Solution Explorer,
-    selecting **Set as Startup Project**, and then pressing F5. Note that the
-    message count does not increment, because the worker role processes items
+    selecting **Set as Startup Project**, and then pressing F5. The
+    message count doesn't increment, because the worker role processes items
     from the queue and marks them as complete. You can see the trace output of
     your worker role by viewing the Azure Compute Emulator UI. You
     can do this by right-clicking the emulator icon in the notification
     area of your taskbar and selecting **Show Compute Emulator UI**.
 
-    :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-38.png" alt-text="Screenshot of what appears when you click the emulator icon. Show Compute Emulator UI is in the list of options.":::
+    :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-38.png" alt-text="Screenshot of what appears when you select the emulator icon. Show Compute Emulator UI is in the list of options.":::
 
     :::image type="content" source="./media/service-bus-dotnet-multi-tier-app-using-service-bus-queues/getting-started-multi-tier-39.png" alt-text="Screenshot of the Microsoft Azure Compute Emulator (Express) dialog box.":::
 

articles/service-bus-messaging/service-bus-tutorial-topics-subscriptions-portal.md

@@ -38,13 +38,16 @@ Each [subscription to a topic](service-bus-messaging-overview.md#topics) can rec
 
 [!INCLUDE [service-bus-create-namespace-portal](./includes/service-bus-create-namespace-portal.md)]
 
+
+[!INCLUDE [get-namespace-connection-string](./includes/get-namespace-connection-string.md)]
+
 [!INCLUDE [service-bus-create-topics-three-subscriptions-portal](./includes/service-bus-create-topics-three-subscriptions-portal.md)]
 
 
 
 ## Create filter rules on subscriptions
 
-After the namespace and topic/subscriptions are provisioned, and you have the necessary credentials, you're ready to create filter rules on the subscriptions, then send and receive messages. You can examine the code in [this GitHub sample folder](https://github.com/Azure/azure-service-bus/tree/master/samples/Java/azure-servicebus/TopicFilters).
+After the namespace and topic/subscriptions are provisioned, and you have the connection string to the namespace, you're ready to create filter rules on the subscriptions, then send and receive messages. You can examine the code in [this GitHub sample folder](https://github.com/Azure/azure-service-bus/tree/master/samples/Java/azure-servicebus/TopicFilters).
 
 ## Send and receive messages
 
@@ -58,7 +61,7 @@ To run the code, follow these steps:
 
 2. Navigate to the sample folder `azure-service-bus\samples\DotNet\Azure.Messaging.ServiceBus\BasicSendReceiveTutorialWithFilters`.
 
-3. Obtain the connection string you copied to Notepad in the Obtain the management credentials section of this tutorial. You also need the name of the topic you created in the previous section.
+3. Obtain the connection string you copied to Notepad earlier in this tutorial. You also need the name of the topic you created in the previous section.
 
 4. At the command prompt, type the following command: