Unify Logo Footer.svg
Unify Integrations
Logo
Azure Service Bus

Azure Service Bus

Logo

4 mins READ

Use the Azure Service Bus connector to enable enterprise messaging and integration.

Integrating your application with Azure Service Bus lets you use these operations in an automation. It exposes 6 actions and 2 triggers, listed below. Add the connector from the Connections area, authenticate, then select its operations in the automation builder. Capabilities: actions, triggers.

Authentication

Before you begin, make sure you have the following information:

Connection Name: Choose a meaningful name for your connection. This name helps you identify the connection within your application or integration settings.

Authentication Type: Azure Service Bus supports the following authentication methods:

  • Credentials

  • Credentials without client configuration

Authentication & setup

Azure Service Bus supports OAuth 2.0 with Microsoft Entra ID (recommended) and Shared Access Signatures (SAS).

How It Works: Microsoft Entra ID provides superior security and ease of use compared to shared access signatures.

Authentication Flow:

  1. The security principal's identity is authenticated

  2. An OAuth 2.0 token is returned for the resource

  3. The resource name is: https://servicebus.azure.net

  4. Token is passed in requests to authorize access to specified resources

Benefits:

  • No need to store tokens in your code

  • Eliminates potential security vulnerabilities

  • Role-based access control integration

Authorization with Azure RBAC

Microsoft Entra integration provides role-based access control. Built-in roles include:

  • Azure Service Bus Data Owner: Full access to all operations

  • Azure Service Bus Data Sender: Permission to send messages

  • Azure Service Bus Data Receiver: Permission to receive messages

Shared Access Signatures (SAS)

Alternative authentication method using access authorization rules.

How to Use SAS:

  • Create a shared access authorization rule

  • Clients receive a SAS token generated from the rule

  • Token includes an HMAC-SHA256 signature of a resource string

  • Use SharedAccessKeyName and SharedAccessKey in your connection string

Actions

Action Name

Description

Delete message

Deletes a message from a queue or topic in Azure Service Bus.

List topics

Retrieves topics in Azure Service Bus

Peek-Lock message

Retrieves and locks a message from a queue or topic in Azure Service Bus

Receive and delete message

Retrieves and deletes a message from a queue or topic in Azure Service Bus.

Send message

Sends a message to Azure Service Bus

Send multiple messages

Sends multiple messages to Azure Service Bus.

Triggers

Trigger Name

Description

New message

New message in Azure Service Bus

New message (Streaming)

New message in Azure Service Bus (Streaming)

About the API

Azure Service Bus is a cloud-based messaging service providing:

  • Message Queues: Asynchronous message communication

  • Topics and Subscriptions: Publish-subscribe messaging patterns

  • Dead Letter Queues: Handling failed messages

  • Sessions: Message ordering and grouping

  • Transactions: ACID-compliant message operations

  • Scheduled Messages: Deferred message delivery

  • Enterprise Integration: Large-scale message processing

Official documentation

https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-authentication-and-authorization