---
title: "Set up Azure Service Bus namespace - Topic and subscriptions"
slug: "set-up-azure-service-bus-namespace-topic-and-subscriptions"
tags: ["Task topic"]
updated: 2026-03-20T07:42:46Z
published: 2026-03-20T17:44:19Z
canonical: "docs.staedean.com/set-up-azure-service-bus-namespace-topic-and-subscriptions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.staedean.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up Azure Service Bus namespace - Topic and subscriptions

You can use a connector of type **Service Bus queue** to exchange information via an Azure Service bus topic and subscriptions. A topic and subscriptions provide a one-to-many form of communication in a publish and subscribe pattern. It's useful for scaling to large numbers of recipients. Each published message is made available to each subscription registered with the topic. Publisher sends a message to a topic and one or more subscribers receive a copy of the message, depending on filter rules set on these subscriptions.

To set up an Azure Service Bus queue:

- [Create a namespace in the Azure portal](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-portal#create-a-namespace-in-the-azure-portal) You need the Service Bus namespace name to fill in the Service Bus namespace field of the connector.
- [Create a topic in the Azure portal](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal#create-a-topic-using-the-azure-portal) You need the Service Bus topic name to fill in the Entity name field of the connector.
- [Create subscriptions to the topic](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-topics-subscriptions-portal#create-subscriptions-to-the-topic) You need the Service Bus subscription name to fill in the Subscription field of the connector.
- Create Shared access signature (SAS) policy You can create and use a SAS policy on these levels: Service Bus queue or Service Bus namespace. You need the:
  - SAS policy name to fill in the Policy name field of the connector.
  - Primary key of the SAS policy to fill in the Policy key field of the connector.

For more information, refer to:

- [Service Bus queues, topics, and subscriptions](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#receive-modes)
- [Use Azure portal to create a Service Bus namespace and a queue](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-portal)
- [Service Bus access control with Shared Access Signatures](https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-sas)

## Related

- [Data export to Azure Service Bus queue or topic](/data-export-to-azure-service-bus-queue-or-topic.md)
- [Data import from Azure Service Bus queue or topic subscription](/data-import-from-azure-service-bus-queue-or-topic-subscription.md)