> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/integrations/azure.md).

# Azure

## What is Azure?

Azure Blob Storage is Microsoft's cloud object storage service for storing large amounts of data, such as flat files. It enables datasets to be uploaded directly to your cloud container rather than accessed via a download link. Coresignal offers this as one of its flat-file delivery options, alongside S3 and Google Cloud, where clients provide their storage credentials and Coresignal sends the data directly.

Azure delivery is ideal for teams that prefer to have Coresignal's data automatically delivered to their current cloud storage and pipelines, avoiding manual file downloads and uploads.

## Available formats and delivery schedule

Available formats include JSONL, Parquet, and CSV, and delivery frequency is based on your agreed schedule.

## How to connect Coresignal to Azure?

{% stepper %}
{% step %}
Create (or identify) the Azure Blob Storage container where you want data files to be delivered.
{% endstep %}

{% step %}
Generate a SAS token for that container, then share the following information with Coresignal:

* Container name
* Blob Shared Access Signature (SAS) Token
* Blob SAS Endpoint URL
  {% endstep %}

{% step %}
Check the destination path structure if you want the data organized in a particular way, and verify the format and delivery schedule for the agreed dataset(s).
{% endstep %}

{% step %}
Coresignal validates access using a test file before regular delivery begins. Regular deliveries begin on the next scheduled run once setup is confirmed.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The SAS token must be valid and have the necessary permissions for Coresignal to write files to the target container. Without proper permissions or if the token has expired, delivery will fail with an authorization error.
{% endhint %}

## Verifying delivery

Once the files land in your container, it's worth checking:

* **Location** – files appear in the agreed container and expected folder path.
* **Format** – the file type matches your subscription's specification (JSONL, Parquet, or CSV).
* **Integrity** – files open, decompress cleanly, and load into your pipeline without errors.
* **Completeness** – record counts appear consistent with what you'd expect for the dataset and time period.

## FAQ

<details>

<summary>We received a 403 (authorization) error. What does that mean?</summary>

Usually, this indicates that the SAS token has expired, is incorrect, is associated with the wrong endpoint, or is missing required upload permissions. This is a common Azure setup issue and should be checked first.

</details>

<details>

<summary>We don't see any files in Azure after setup. What should we check?</summary>

First, verify that the container name is correct, the SAS endpoint URL points to the container and path (not just the storage account root), and that setup was confirmed with a successful test file. After setup, deliveries typically begin on the next scheduled run.

</details>

<details>

<summary>Can I have separate buckets for different datasets?</summary>

Yes, provide the container name for each dataset and confirm access. We will then configure individual deliveries to each container.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coresignal.com/integrations/azure.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.