> For the complete documentation index, see [llms.txt](https://docs.couchdrop.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.couchdrop.io/integrations/data-analytics-and-bi/azure-queue.md).
# Azure Queue
How to connect using the Azure Queue system integration
## Overview
Azure Queue Storage provides message queues for communication between applications and services. With Couchdrop, you can publish data to an Azure Queue from file actions and Automations, allowing file-based workflows to feed event-driven systems without requiring separate integration middleware.
Couchdrop can receive files or payloads from sources such as cloud storage, SFTP/FTP, APIs, and inbound webhooks, then use an Automation to publish that data as a message to an Azure Queue.
## How to connect Azure Queue
{% hint style="warning" %}
#### Before you start
To connect Azure Queue to Couchdrop, you will need:
* An Azure account
* An Azure Queue created within an Azure Storage account
* The **queue name**
* The **storage account name**
* An **access key** for the storage account
{% endhint %}
{% stepper %}
{% step %}
### Create a new system integration
Log in to Couchdrop and add a new **System Integration**.
{% endstep %}
{% step %}
### Select Azure Queue
Select **Azure Queue** from the list of available integrations.
{% endstep %}
{% step %}
### Configure the Azure Queue connection
Provide the Azure Queue configuration details listed above, including the queue name, storage account name, and storage account access key.
{% endstep %}
{% step %}
### Save the integration
Click **Add System Integration** to create the Azure Queue connection.
Once configured, the connection can be selected from supported file actions inside Couchdrop Automations.
{% endstep %}
{% endstepper %}
## Using Azure Queues in Couchdrop
Azure Queue is configured in Couchdrop as a **platform integration**. Unlike a storage connection, it does not appear as a virtual folder.
Instead, the Azure Queue connection becomes available for use in a file action inside an Automation. This allows a workflow to receive or process data in Couchdrop and publish it to the configured Azure Queue.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.couchdrop.io/integrations/data-analytics-and-bi/azure-queue.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
