Service Bus Namespace Setup

A Namespace is the first resource created when working with Azure Service Bus. It acts as a container for all messaging entities — queues, topics, and subscriptions. Setting up the namespace correctly from the start lays the foundation for a reliable messaging system.

What Is a Namespace?

A namespace gives a unique endpoint URL for all messaging operations. Every queue and topic inside the namespace shares this URL. The URL format is:

https://<namespace-name>.servicebus.windows.net

For example, if the namespace name is myshopns, the endpoint becomes:

https://myshopns.servicebus.windows.net

Namespace Setup — Step by Step (Azure Portal)

Step 1: Open the Azure Portal

Navigate to portal.azure.com and sign in with an Azure account.

Step 2: Search for Service Bus

In the search bar at the top, type Service Bus and click on the Service Bus result under the Services category.

Step 3: Click Create

On the Service Bus page, click the + Create button to start the namespace creation wizard.

Step 4: Fill in the Basics Tab

Field	Description	Example Value
Subscription	Azure subscription to bill the resource under	My Azure Subscription
Resource Group	Logical group to organize Azure resources	rg-messaging-prod
Namespace Name	Globally unique name for the namespace	myshopns
Location	Azure region where the namespace is hosted	East US
Pricing Tier	Basic, Standard, or Premium	Standard

Step 5: Review and Create

Click Review + Create, verify all settings, and click Create. Azure takes 1–2 minutes to deploy the namespace.

Namespace Setup Using Azure CLI

Azure CLI provides a faster way to create a namespace without using the portal UI. Run the following commands in Azure Cloud Shell or a local terminal with the Azure CLI installed.

Login to Azure

az login

Create a Resource Group

az group create \
  --name rg-messaging-prod \
  --location eastus

Create a Service Bus Namespace

az servicebus namespace create \
  --resource-group rg-messaging-prod \
  --name myshopns \
  --location eastus \
  --sku Standard

Verify the Namespace

az servicebus namespace show \
  --resource-group rg-messaging-prod \
  --name myshopns

Namespace Setup Using Azure PowerShell

# Login
Connect-AzAccount

# Create Resource Group
New-AzResourceGroup -Name "rg-messaging-prod" -Location "EastUS"

# Create Namespace
New-AzServiceBusNamespace `
  -ResourceGroupName "rg-messaging-prod" `
  -Name "myshopns" `
  -Location "EastUS" `
  -SkuName "Standard"

Namespace Naming Rules

Rule	Detail
Length	6 to 50 characters
Allowed Characters	Letters, numbers, and hyphens only
Start Character	Must start with a letter
End Character	Must end with a letter or number (not a hyphen)
Uniqueness	Must be globally unique across all Azure customers

Namespace Structure After Creation

Namespace: myshopns.servicebus.windows.net
  |
  |-- [No queues yet]
  |-- [No topics yet]
  |-- Shared Access Policies:
        |-- RootManageSharedAccessKey (default — full access)

Connection Strings and Access Keys

After creating the namespace, Azure generates a connection string. Applications use this string to authenticate and connect to the namespace.

Get the Connection String from the Portal

Open the namespace in the Azure Portal
Click Shared access policies in the left menu
Click the RootManageSharedAccessKey policy
Copy the Primary Connection String

Connection String Format

Endpoint=sb://myshopns.servicebus.windows.net/;
SharedAccessKeyName=RootManageSharedAccessKey;
SharedAccessKey=<your-key-here>

Get the Connection String via CLI

az servicebus namespace authorization-rule keys list \
  --resource-group rg-messaging-prod \
  --namespace-name myshopns \
  --name RootManageSharedAccessKey \
  --query primaryConnectionString \
  --output tsv

Namespace Regions — Best Practices

Consideration	Recommendation
Latency	Choose the region closest to the application and its users
Compliance	Pick a region that meets data residency laws (e.g., EU data in West Europe)
Availability Zones	Premium tier namespaces support availability zones for high availability
Geo-DR Pairing	For Premium, pair with a secondary namespace in a different region for disaster recovery

Resource Group Best Practice

Always create the Service Bus namespace inside a dedicated resource group. Naming the resource group clearly — for example, rg-servicebus-prod or rg-messaging-dev — makes it easy to manage, monitor, and clean up resources later.

Resource Group: rg-messaging-prod
  |
  |-- Namespace: myshopns (Standard)
  |-- Namespace: myshopns-dr (Premium - Geo-DR secondary)

Tags for Cost Management

Apply Azure tags to the namespace to track costs by team, project, or environment.

az tag create \
  --resource-id /subscriptions/<sub-id>/resourceGroups/rg-messaging-prod/providers/Microsoft.ServiceBus/namespaces/myshopns \
  --tags Environment=Production Team=Backend Project=OrderSystem

Summary

Creating a Service Bus namespace is the first practical step in using Azure Service Bus. The namespace must have a globally unique name, sit in the right Azure region, and use the correct pricing tier. After creation, the connection string enables applications to connect and start sending or receiving messages. Proper naming, resource grouping, region selection, and tagging make the namespace easy to manage in the long run.

Previous lessons

Back to courses

Next lessons