Merge pull request #48863 from spelluru/sbustraining0127

JamesJBarnett · web-flow · commit 4423f3aded9e · 2025-01-28T10:51:39.000-07:00
Freshness review of Service Bus training module
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/1-introduction.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/1-introduction.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Introduction
   description: Introduction.
-  ms.date: 10/25/2023
+  ms.date: 01/27/2025
   author: spelluru
   ms.author: spelluru
   ms.topic: unit
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/2-choose-a-messaging-platform.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/2-choose-a-messaging-platform.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Choose a messaging platform
   description: Understand how to choose a messaging platform.
-  ms.date: 10/25/2023
+  ms.date: 01/27/2025
   author: spelluru
   ms.author: spelluru
   ms.topic: unit
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/3-exercise-implement-a-service-bus-topic-and-queue.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/3-exercise-implement-a-service-bus-topic-and-queue.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Create Service Bus queue and topic
   description: Create Service Bus messaging components—a namespace that contains a queue, a topic, and subscriptions.
-  ms.date: 10/25/2023
+  ms.date: 01/27/2025
   author: spelluru
   ms.author: spelluru
   ms.topic: unit
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/4-write-code-that-uses-service-bus-queues.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/4-write-code-that-uses-service-bus-queues.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Write code to send and receive messages by using a queue
   description: Learn how to write code that sends messages to and receives messages from a Service Bus queue.
-  ms.date: 10/25/2023
+  ms.date: 01/27/2025
   author: spelluru
   ms.author: spelluru
   ms.topic: unit
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/5-exercise-write-code-that-uses-service-bus-queues.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/5-exercise-write-code-that-uses-service-bus-queues.yml
@@ -6,12 +6,11 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Send and receive messages by using a queue
   description: Write code that sends messages to and receives messages from a Service Bus queue.
-  ms.date: 10/25/2023
+  ms.date: 01/27/2025
   author: spelluru
   ms.author: spelluru
   ms.topic: unit
 interactive: bash
-azureSandbox: true
 durationInMinutes: 10
 content: |
   [!include[](includes/5-exercise-write-code-that-uses-service-bus-queues.md)]
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/6-write-code-that-uses-service-bus-topics.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/6-write-code-that-uses-service-bus-topics.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Write code to send and receive messages by using a topic
   description: Learn how to write code that sends messages to a topic and receives messages from a subscription to the topic.
-  ms.date: 10/25/2023
+  ms.date: 01/27/2025
   author: spelluru
   ms.author: spelluru
   ms.topic: unit
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/7-exercise-write-code-that-uses-service-bus-topics.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/7-exercise-write-code-that-uses-service-bus-topics.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Exercise - Send and receive messages by using a topic
   description: Write code that sends messages to a topic and receives messages from a subscription to the topic.
-  ms.date: 10/25/2023
+  ms.date: 01/27/2025
   author: spelluru
   ms.author: spelluru
   ms.topic: unit
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/8-summary.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/8-summary.yml
@@ -6,7 +6,7 @@ metadata:
   prefetch-feature-rollout: true
   title: Summary
   description: Summary.
-  ms.date: 10/25/2023
+  ms.date: 01/27/2025
   author: spelluru
   ms.author: spelluru
   ms.topic: unit
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/includes/1-introduction.md b/learn-pr/azure/implement-message-workflows-with-service-bus/includes/1-introduction.md
@@ -1,18 +1,23 @@
 Modern applications frequently consist of multiple parts running on separate computers and devices that are distributed in diverse locations around the world. Complex networks with varying reliability and speed exist among these components. A fundamental challenge with these distributed applications is how to communicate reliably among the components.
 
-Suppose you're a cloud developer for Contoso Bicycles, a global bicycle chain. Your employer is upgrading its technology so that customers can place orders from the web or from a mobile app. An order is sent to the customer's preferred storefront location, where store employees fill the order. As the order is filled from parts, packaged for shipping, and put on a delivery vehicle, updates are sent to the customer's mobile app. The customer even receives location updates as the delivery vehicle heads toward them.
+Suppose you're a cloud developer for Contoso Bicycles, a global bicycle chain. Your employer is upgrading its technology so that customers can place orders from the web or from a mobile app. An order is sent to the customer's preferred storefront location, where store employees fill the order. As the order is filled from parts, packaged for shipping, and placed on a delivery vehicle, updates are sent to the customer's mobile app. The customer even receives location updates as the delivery vehicle heads toward them.
 
-Contoso Bicycles previously created an online ordering system that immediately stored order data in a SQL Server database. Each store had to manually refresh the company's web orders intranet page to check for new orders for their store. In addition, during peak usage, such as bicycle orders during tourist season or sporting events, the system frequently experienced deadlock exceptions and timeouts. Finally, the system lacked central payment processing and any kind of order-status tracking for the customer.
+Contoso Bicycles previously created an online ordering system that immediately stored order data in a SQL Server database. Each store had to manually refresh the company's web orders intranet page to check for new orders for their store. In addition, during peak usage, such as bicycle orders during tourist season or sporting events, the system frequently experienced deadlock exceptions and time-outs. Finally, the system lacked central payment processing and any kind of order-status tracking for the customer.
 
 For the new, more ambitious project, Contoso Bicycles hired a cloud architect. The company plans to begin using a distributed architecture for order communications.
 
-In this module, you'll learn how Azure Service Bus can help build an application that is reliable, even during peak demand. You'll also learn how Azure Service Bus makes it easy to add functionality to applications. You'll be writing the C# code that's necessary to put these lessons to work. Here, you'll see how to use Service Bus queues and topics in a distributed architecture to ensure reliable communications, even at times of high demand.
+In this module, you learn how Azure Service Bus can help build an application that is reliable, even during peak demand. You also learn how Azure Service Bus makes it easy to add functionality to applications. You write the C# code that's necessary to put these lessons to work. Here, you see how to use Service Bus queues and topics in a distributed architecture to ensure reliable communications, even at times of high demand.
 
 ## Learning objectives
 
-In this module, you'll learn how to:
+In this module, you learn how to:
 
 - Choose whether to use Service Bus queues or topics to communicate in a distributed application.
 - Configure an Azure Service Bus namespace in an Azure subscription.
 - Create a Service Bus topic and use it to send and receive messages.
 - Create a Service Bus queue and use it to send and receive messages.
+
+## Prerequisites
+
+- Experience using [Visual Studio Code](https://code.visualstudio.com/download) to develop, build, and run C# console applications.
+- Experience using Git repositories and Git Bash. Download [Git for Windows](https://git-scm.com/downloads/win) if you don't have it already on your computer.
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/includes/2-choose-a-messaging-platform.md b/learn-pr/azure/implement-message-workflows-with-service-bus/includes/2-choose-a-messaging-platform.md
@@ -14,7 +14,7 @@ In the terminology of distributed applications, the defining characteristic of a
 
 A message generally contains the actual data, not just a reference (like an ID or a URL) to data. Sending data as part of a datagram is less brittle than sending a reference. The messaging architecture guarantees message delivery, and because no extra lookups are required, the message is reliably handled. However, the sending application needs to know exactly what data to include to avoid sending too much data, which would require the receiving component to do unnecessary work. In this sense, the message sender and receiver are often coupled by a strict data contract.
 
-In the new architecture for Contoso Bicycles, when an order is placed, the company likely will use messages. The web front end or mobile app will send a message to the back-end processing components. On the back end, steps like routing to the store nearest the customer and charging a credit card will take place.
+In the new architecture for Contoso Bicycles, when an order is placed, the company likely uses messages. The web front end or mobile app sends a message to the back-end processing components. On the back end, steps like routing to the store nearest the customer and charging a credit card takes place.
 
 ### Events
 
@@ -44,16 +44,16 @@ A Service Bus _queue_ is a simple temporary storage location for messages. A sen
 
 Queues decouple the source and destination components to insulate destination components from high demand.
 
-During peak times, messages might come in faster than destination components can handle them. Because source components have no direct connection to the destination, the source is unaffected, and the queue will grow. Destination components will remove messages from the queue as they're able to handle them. When demand drops, destination components can catch up, and the queue shortens.
+During peak times, messages might come in faster than destination components can handle them. Because source components have no direct connection to the destination, the source is unaffected, and the queue grows. Destination components remove messages from the queue as they're able to handle them. When demand drops, destination components can catch up, and the queue shortens.
 
-A queue responds to high demand without needing to add resources to the system. However, for messages that need to be handled quickly, creating more instances of your destination component can allow them to share the load. Each message is handled by only one instance. This is an effective way to scale your entire application by only adding resources to the components that actually need it.
+A queue responds to high demand without needing to add resources to the system. However, for messages that need to be handled quickly, creating more instances of your destination component can allow them to share the load. Each message is handled by only one instance. This method is an effective way to scale your entire application by only adding resources to the components that actually need it.
 
 ### What is a topic?
 
-A Service Bus _topic_ is similar to a queue, but a topic can have multiple subscriptions. This means that multiple destination components can subscribe to a specific topic, so each message is delivered to multiple receivers. Subscriptions can also filter the messages in the topic to receive only messages that are relevant. Subscriptions provide the same decoupled communications as queues and respond to high demand in the same way. Use a topic if you want each message to be delivered to more than one destination component.
+A Service Bus _topic_ is similar to a queue, but a topic can have multiple subscriptions, which means that multiple destination components can subscribe to a specific topic, so each message is delivered to multiple receivers. Subscriptions can also filter the messages in the topic to receive only messages that are relevant. Subscriptions provide the same decoupled communications as queues and respond to high demand in the same way. Use a topic if you want each message to be delivered to more than one destination component.
 
 > [!NOTE]
-> Topics are not supported in the Basic pricing tier.
+> Topics aren't supported in the Basic pricing tier.
 
 :::image type="content" source="../media/2-service-bus-topic.png" alt-text="Diagram that shows one sender sending messages to multiple receivers through a topic that contains three subscriptions. These subscriptions are used by three receivers to retrieve the relevant messages.":::
 
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/includes/3-exercise-implement-a-service-bus-topic-and-queue.md b/learn-pr/azure/implement-message-workflows-with-service-bus/includes/3-exercise-implement-a-service-bus-topic-and-queue.md
@@ -1,13 +1,13 @@
 You have an application for the sales team in your global company. Each team member has your app installed on a mobile device to use for sales. An Azure web service hosts the business logic implemented for your application and stores information in Azure SQL Database. Each geographical region has its own instance of the web service.
 
-You've identified the following scenarios for message exchange between the mobile app and the web service:
+You identified the following scenarios for message exchange between the mobile app and the web service:
 
 - Messages that relate to individual sales must be sent to the web service instance in the user's region.
 - Messages that relate to sales performance must be sent to all instances of the web service.
 
-You've decided to implement a Service Bus queue for the first use case and a Service Bus topic for the second use case.
+You decided to implement a Service Bus queue for the first use case and a Service Bus topic for the second use case.
 
-In this exercise, you'll create a Service Bus namespace that contains a queue, a topic, and subscriptions in the Azure portal.
+In this exercise, you create a Service Bus namespace that contains a queue, a topic, and subscriptions in the Azure portal.
 
 ## Create a Service Bus namespace
 
@@ -24,8 +24,8 @@ Start by creating the namespace. In Azure Service Bus, a namespace is a containe
     | Setting | Value | Description |
     | ------- | --- | ---- |
     | **Project Details** |
-    | Subscription | Concierge subscription | The subscription in which this new app is created. |
-    | Resource group | <rgn>[Sandbox resource group name]</rgn> | The name of the resource group in which to create your Service Bus namespace. In this exercise, you'll create the namespace in the resource group that was assigned when you activated the sandbox. |
+    | Subscription | Concierge subscription | The subscription where you want the app to be created.  |
+    | Resource group | <rgn>[Sandbox resource group name]</rgn> | The name of the resource group in which to create your Service Bus namespace. In this exercise, you create the namespace in the resource group that was assigned when you activated the sandbox. |
     | **Instance Details** |
     | Namespace name | [Globally unique name] | Enter a name that is unique in Azure.<br />If you want to use the format _salesteamapp_<_Company_><_year_>, your namespace name would look like the example _salesteamappContoso2022_. |
     | Location | Select from the dropdown | Choose from the free *sandbox regions* listed following this table. |
@@ -53,13 +53,13 @@ Next, add a queue for messages about individual sales to your namespace:
   
     :::image type="content" source="../media/3-create-queue.png" alt-text="Screenshot of Service Bus namespace and Create queue panes with Queue and Create highlighted.":::
 
-1. In the **Create queue** pane, for **Name**, enter **salesmessages**, then select **Create**.  
+1. In the **Create queue** pane, for **Name**, enter `salesmessages`, then select **Create**.  
   
-When the message queue has been created, **salesmessages** is listed under **Queues** at the bottom of the Service Bus namespace pane.
+When the message queue is created, `salesmessages` is listed under **Queues** at the bottom of the Service Bus namespace pane.
 
 ## Create a Service Bus topic and subscriptions
 
-You also want to create a topic that will be used for messages that relate to sales performance. Each instance of the business logic web service subscribes to this topic, and each sales performance message will be delivered to all web service subscriptions.
+You also want to create a topic that's used for messages that relate to sales performance. Each instance of the business logic web service subscribes to this topic, and each sales performance message is delivered to all web service subscriptions.
 
 Add a Service Bus topic and subscriptions:
 
@@ -69,7 +69,7 @@ Add a Service Bus topic and subscriptions:
 
 1. In the **Create topic** pane, for **Name**, enter *salesperformancemessages*, then select **Create**.
 
-   When the topic has been created, **salesperformancemessages** is listed under **Topics** at the bottom of the Service Bus namespace pane.
+   When the topic is created, **salesperformancemessages** is listed under **Topics** at the bottom of the Service Bus namespace pane.
 
 1. You can add or remove subscriptions in queues and topics by using the tabs in the Service Bus namespace, or you can use the Azure portal resource menu. To use the menu option, in the left menu, under **Entities**, select **Topics**, and then select **salesperformancemessages** in the list of topics.
 
@@ -85,4 +85,13 @@ Add a Service Bus topic and subscriptions:
 
 The **Subscriptions** section of the **salesperformancemessages** Service Bus topic for your sales team app now lists two subscriptions.
   
-You've built the infrastructure to use Service Bus to increase the resilience of your distributed application. You've created a queue for messages about individual sales, and a topic for messages about sales performance. You've added multiple subscriptions to the topic, so topic messages can be delivered to multiple web services around the world.
+You built the infrastructure to use Service Bus to increase the resilience of your distributed application. You created a queue for messages about individual sales, and a topic for messages about sales performance. You added multiple subscriptions to the topic, so topic messages can be delivered to multiple web services around the world.
+
+## Get connnection string
+
+1. On the **Service Bus Namespace** page, select **Shared access policies** on the left menu. 
+1. Select **RoothManageSharedAccessKey** in the middle pane.
+1. In the **SAS Policy: RootManageSharedAccessKey** pane, select the copy button next to the **Primary connection string** field. 
+1. Paste the primary connection string into an editor of your choice. You use this connection string later in this training. 
+
+    :::image type="content" source="../media/3-connection-string.png" alt-text="Screenshot of the Shared access policies page." lightbox="../media/3-connection-string.png":::
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/includes/5-exercise-write-code-that-uses-service-bus-queues.md b/learn-pr/azure/implement-message-workflows-with-service-bus/includes/5-exercise-write-code-that-uses-service-bus-queues.md
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/includes/6-write-code-that-uses-service-bus-topics.md b/learn-pr/azure/implement-message-workflows-with-service-bus/includes/6-write-code-that-uses-service-bus-topics.md
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/includes/7-exercise-write-code-that-uses-service-bus-topics.md b/learn-pr/azure/implement-message-workflows-with-service-bus/includes/7-exercise-write-code-that-uses-service-bus-topics.md
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/index.yml b/learn-pr/azure/implement-message-workflows-with-service-bus/index.yml
diff --git a/learn-pr/azure/implement-message-workflows-with-service-bus/media/3-connection-string.png b/learn-pr/azure/implement-message-workflows-with-service-bus/media/3-connection-string.png
