# Azure Service Bus integrations: messages

> Send a message, create a queue and create a topic in Azure Service Bus. Connect Azure Service Bus to the rest of your developer tools stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/azure-service-bus-integrations/
**Categories:** Developer tools
**Connects through:** HTTP Connector

## Overview

Azure Service Bus is Microsoft's managed message broker, passing messages between applications through queues, and topics with subscriptions. Tray.ai connects to Azure Service Bus through the HTTP Connector, so your workflows can call the Azure Service Bus API alongside the rest of your stack.

## Use cases

### Messages

Create and delete messages in Azure Service Bus from any Tray.ai workflow. The Azure Service Bus API covers calls such as send a message and send a message batch.

- Send a message
- Send a message batch
- Receive and delete a message

### Queues

Read, create, update, and delete queues in Azure Service Bus from any Tray.ai workflow. The Azure Service Bus API covers calls such as create a queue and update a queue.

- Create a queue
- Update a queue
- Delete a queue

### Topics

Read, create, update, and delete topics in Azure Service Bus from any Tray.ai workflow. The Azure Service Bus API covers calls such as create a topic and update a topic.

- Create a topic
- Update a topic
- Delete a topic

### Subscriptions

Read, create, and delete subscriptions in Azure Service Bus from any Tray.ai workflow. The Azure Service Bus API covers calls such as create a subscription and delete a subscription.

- Create a subscription
- Delete a subscription
- List subscriptions

## Challenges Tray.ai solves

### Keeping Azure Service Bus credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Azure Service Bus credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Azure Service Bus API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Azure Service Bus API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Azure Service Bus?

Yes. Tray.ai connects to Azure Service Bus through the HTTP Connector, which calls the Azure Service Bus API directly. Any call the Azure Service Bus API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Azure Service Bus?

The Azure Service Bus API uses OAuth 2.0 and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Azure Service Bus connector?

Azure Service Bus runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Azure Service Bus connector from the Azure Service Bus API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/