Azure Service Bus Exporter

📘

Check out the official Azure Service Bus docs here

Set up

The connector authenticates using Shared Access Signature (SAS) tokens, which are generated from Shared Access Policies configured in Azure Service Bus. More info can be found here and here

To set up a connector Source for Azure Service Bus, you will need:

• Namespace: The Service Bus namespace hostname (e.g. example.servicebus.windows.net)
• Access Policy Name: The name of a Shared Access Policy with Send permissions
• Access Policy Key: The primary or secondary key associated with the policy

For each export configuration, you will need the Queue Path (this is the name of the Service Bus queue to export to)

Features

Reports detail

📘

Assumptions & constraints

• The queue must allow Send permission for the configured access policy
• Message ordering is not guaranteed

📘

Behaviour of exporter (and additional table for logging)

Whenever an export is executed, the connector stores request metadata in a table within the same schema as the destination table.

The table name follows the pattern:

<destination_table_name>_responses

For example, exporting little_pond.big_fish will create or append to:

little_pond.big_fish_responses

What is stored in the _responses table

Each row in the _responses table represents a single message publish attempt and contains:

• The first-level fields of the HTTP request metadata (e.g. URL, method, headers)
• The first-level fields of the exported payload
• A response column containing the Service Bus API response (if successful)
• An error column containing error details (if the request failed)

On subsequent export runs, new rows are appended to the same _responses table.

Important

The _responses table is intended for observability and troubleshooting purposes only. It should not be treated as a system of record or source of truth for the exported data.

Delivery confirmation should be handled by downstream consumers of the queue where required.