Create a Service Jitney namespace using the Azure portal

  • Article
  • 2 minutes to read

A namespace is a scoping container for all messaging components. Multiple queues and topics tin reside inside a single namespace, and namespaces oftentimes serve as application containers. For more information about namespaces and other concepts of Azure Service Bus, see Service Coach - concepts.

This article provides instructions for creating a namespace in the Azure portal.

Create a namespace in the Azure portal

To begin using Service Bus messaging entities in Azure, yous must commencement create a namespace with a name that is unique beyond Azure. A namespace provides a scoping container for Service Bus resources within your application.

To create a namespace:

  1. Sign in to the Azure portal

  2. In the left navigation pane of the portal, select + Create a resource, select Integration, and so select Service Omnibus.

    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, cull an Azure subscription in which to create the namespace.

    2. For Resource group, cull an existing resource group in which the namespace will live, or create a new one.

    3. Enter a name for the namespace. The namespace proper name should adhere to the following naming conventions:

      • The name must be unique beyond Azure. The system immediately checks to see if the name is bachelor.
      • The proper name length is at to the lowest degree six and at most fifty characters.
      • The name can contain only letters, numbers, hyphens "-".
      • The proper name must start with a letter of the alphabet and end with a letter or number.
      • The name doesn't terminate with "-sb" or "-mgmt".

    4. For Location, choose the region in which your namespace should exist hosted.

    5. For Pricing tier, select the pricing tier (Basic, Standard, or Premium) for the namespace. For this quickstart, select Standard.

      Of import

      If y'all want to use 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 then that each workload runs in isolation. This resources container is called a messaging unit of measurement. A premium namespace has at least i messaging unit of measurement. You can select 1, 2, iv, eight or 16 messaging units for each Service Jitney Premium namespace. For more information, see Service Bus Premium Messaging.

    6. Select Review + create. The arrangement now creates your namespace and enables it. You lot might have to wait several minutes every bit the system provisions resources for your account.

      Image showing the Create a namespace page

    7. On the Create page, review settings, and select Create.

  4. Select Become to resource on the deployment page.

    Image showing the deployment succeeded page with the Go to resource link.

  5. You run into the home page for your service bus namespace.

    Image showing the home page of the Service Bus namespace created.

Get the connection cord

Creating a new namespace automatically generates an initial Shared Access Signature (SAS) policy with principal and secondary keys, and primary and secondary connectedness strings that each grant total control over all aspects of the namespace. See Service Bus authentication and authorization for information well-nigh how to create rules with more constrained rights for regular senders and receivers.

To copy the primary connexion cord for your namespace, follow these steps:

  1. On the Service Bus Namespace page, select Shared access policies on the left menu.

  2. On the Shared admission policies page, select RootManageSharedAccessKey.

  3. In the Policy: RootManageSharedAccessKey window, select the re-create button next to Primary Connectedness String, to re-create the connectedness cord to your clipboard for subsequently use. Paste this value into Notepad or some other temporary location.

    Screenshot shows an S A S policy called RootManageSharedAccessKey, which includes keys and connection strings.

    You can utilize this page to copy primary primal, secondary key, primary connection string, and secondary connection string.

Congratulations! Y'all have now created a Service Charabanc Messaging namespace.

Next steps

Check out Service Bus samples.