freshness review & updates

Author: spelluru

articles/service-bus-messaging/includes/media/service-bus-create-namespace-portal/create-namespace.png

@@ -5,7 +5,7 @@
  author: spelluru
  ms.service: service-bus-messaging
  ms.topic: include
- ms.date: 04/26/2022
+ ms.date: 10/20/2022
  ms.author: spelluru
  ms.custom: include file
 ---
@@ -16,8 +16,8 @@ To begin using Service Bus messaging entities in Azure, you must first create a
 To create a namespace:
 
 1. Sign in to the [Azure portal](https://portal.azure.com)
-2. In the left navigation pane of the portal, select **+ Create a resource**, select **Integration**, and then select **Service Bus**.
-
+2. In the left navigation pane of the portal, select **All services**, select **Integration** from the list of categories, hover the mouse over **Service Bus**, and then select **Create** on the Service Bus tile. 
+    
     :::image type="content" source="./media/service-bus-create-namespace-portal/create-resource-service-bus-menu.png" alt-text="Image showing selection of Create a resource, Integration, and then Service Bus in the menu.":::
 3. In the **Basics** tag of the **Create namespace** page, follow these steps: 
     1. For **Subscription**, choose an Azure subscription in which to create the namespace.
@@ -35,21 +35,21 @@ To create a namespace:
         > If you want to use [topics and subscriptions](../service-bus-queues-topics-subscriptions.md#topics-and-subscriptions), choose either Standard or Premium. Topics/subscriptions aren't supported in the Basic pricing tier. 
 
         If you selected the **Premium** pricing tier, specify the number of **messaging units**. The premium tier provides resource isolation at the CPU and memory level so that each workload runs in isolation. This resource container is called a messaging unit. A premium namespace has at least one messaging unit. You can select 1, 2, 4, 8 or 16 messaging units for each Service Bus Premium namespace. For more information, see [Service Bus Premium Messaging](../service-bus-premium-messaging.md).
-    1. Select **Review + create**. The system now creates your namespace and enables it. You might have to wait several minutes as the system provisions resources for your account.
+    1. Select **Review + create** at the bottom of the page. 
 
         :::image type="content" source="./media/service-bus-create-namespace-portal/create-namespace.png" alt-text="Image showing the Create a namespace page":::
-    1. On the **Create** page, review settings, and select **Create**. 
-4. Select **Go to resource** on the deployment page. 
+    1. On the **Review + create** page, review settings, and select **Create**. 
+4. Once the deployment of the resource is successful, select **Go to resource** on the deployment page. 
 
     :::image type="content" source="./media/service-bus-create-namespace-portal/deployment-alert.png" alt-text="Image showing the deployment succeeded page with the Go to resource link.":::
 6. You see the home page for your service bus namespace. 
 
-    :::image type="content" source="./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." :::
+    :::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." :::
 
 ## Get the connection string 
 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. 
 
-To copy the primary connection string for your namespace, follow these steps: 
+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**.

articles/service-bus-messaging/includes/media/service-bus-create-namespace-portal/create-resource-service-bus-menu.png

@@ -5,7 +5,7 @@
  author: spelluru
  ms.service: service-bus-messaging
  ms.topic: include
- ms.date: 10/08/2021
+ ms.date: 10/20/2022
  ms.author: spelluru
  ms.custom: include file
 ---

articles/service-bus-messaging/includes/media/service-bus-create-namespace-portal/deployment-alert.png

@@ -3,7 +3,7 @@ title: Use the Azure portal to create a Service Bus queue
 description: In this quickstart, you learn how to create a Service Bus namespace and a queue in the namespace by using the Azure portal.
 author: spelluru
 ms.author: spelluru
-ms.date: 09/10/2021
+ms.date: 10/20/2022
 ms.topic: quickstart
 ms.custom: mode-ui
 ---