Guided Lab: Creating an Azure Service Bus Namespace
Description
Azure Service Bus is a fully managed enterprise message broker that enables reliable, asynchronous communication between decoupled applications using queues and topics. It is commonly used to smooth traffic spikes, buffer workloads, and integrate distributed services without tight coupling
In this guided lab, a new Service Bus namespace will be created and configured under a constrained lab environment. Because this environment allows only the Basic SKU, the focus will be on creating a queue (topics and advanced features are unavailable in Basic).
Objectives
In this lab, you will:
- Create an Azure Service Bus namespace in the allowed region and resource group.
- Configure a Basic SKU and understand its limitations (queues only; no topics).
- Create a queue within the namespace and review key settings.
- Set up and verify shared access policies (SAS) for the namespace.
Subscribe to access Azure PlayCloud LabsLab Steps
Creating an Azure Service Bus Namespace
1. In the Azure portal, navigate to the Azure Service Bus service by clicking the service on the homepage or via the search bar.
2. From the results, click the Create button in the center of the Create or on the top left corner of the portal.
.png)
3. On the Basics tab, provide the following configuration:
- Subscription: Azure Labs Subscription
- Resource group:
azure-lab-rg-9jdvDNHrzgv9 - Namespace name: Enter sampaguita-namespace. If the name is already taken, add numbers or characters to make it globally unique (for example, sampaguita-namespace123).
- Location: Select Central US.
- Pricing tier: Choose Basic (required for this lab).
 Image 2.png)
Leave the other tabs at their default settings. Once complete, click Review + create, and then Create.
 .jpg)
Selecting the Basic SKU enforces a simplified configuration where only queues can be created. Advanced messaging features such as topics, sessions, or transactions are not available, which makes this SKU ideal for entry-level scenarios, lightweight message queuing, and learning environments like this lab.
Verifying the Namespace
1. Once deployment is complete, click Go to resource.
 .jpg)
2. On the namespace overview page, check the following details:
- The Host name should be in the format sampaguita-namespace.servicebus.windows.net
- The Location must show Central US.
- The Pricing tier must display Basic.
.png)
If you accidentally chose the wrong region or SKU, delete the namespace and repeat the previous step to redeploy correctly.
Creating a Queue
1. In the namespace blade, under Entities, select Queues, then click + Queue.
2. Enter the name sampaguita-queue.
3. Leave the default settings for Max size and Message TTL. Do not enable features that are unavailable in the Basic SKU.
4. Click Create.
 .png)
Queues provide a reliable way for producers to send messages that consumers later retrieve. In the Basic SKU, queues are the only supported entity, making them a great starting point to understand message queuing fundamentals in Azure Service Bus.
Configuring Shared Access Policies (SAS)
1. In the namespace blade, under Settings, select Shared access policies.
2. You can click the default RootManageSharedAccessKey to review the existing connection keys. For this lab, create a new scoped policy by clicking + Add.
3. Enter the policy name as queue-send-listen.
.jpg)
4. For claims, select Send and Listen. Avoid using Manage to align with least-privilege principles.
4. Click Create.
Once created, open the new policy and copy the Primary connection string. This string is used by client applications to authenticate with the namespace and send/receive messages. For security reasons, keep it private and secure.
.png)
Tips: Add to your habit of cleaning up the resources after your labs. In this case, delete the Service Bus namespace and its associated resources once you are finished. This is not only a good habit but also gives you practice in taking responsibility for your resources and avoiding unnecessary usage costs.
✅ Congratulations! You have successfully created and configured an Azure Service Bus Namespace using the Basic SKU. You learned how to create the namespace, set up a queue, configure shared access policies, and validate the environment. Happy Learning!