# Export to Azure Blob Storage

**ROIVENUE Data Exporting into Azure Blob Storage** is a helpful tool for dealing with files with **greater data size** and can be a valuable part of your arsenal for further data processing or analysis.

## Step 1: Go to the Last Step of the Export

It doesn't matter if you want to export data from connector or from data exports from ROIVENUE.

&#x20;

<figure><img src="/files/y0ulMCKNriSYocLwrSrI" alt=""><figcaption><p>ROIVENUE Data Exports wizard</p></figcaption></figure>

There is a lot of input fields that need to be filled, in order to successfully export to Azure Blob Storage. Let's get slowly through them one by one.

### **Account Name:**

Account name is the name of the Storage Account that can be seen in the interface of Azure Explorer.

![](/files/-MiHtqSTyr9NmY2A9MLk)

### **Access Key:**

Access key is "Primary Key" from the Azure Explorer UI.

![](/files/-M_k8OH6QEXgIuMk2D9y)

### **Container Name:**

Every storage account **can have many individual containers for effective sorting of your data**. During setup of the connector, w**rite the name of the container to which you want to export your data.**

![](/files/-MiHtEtIDRnkfOZ8hZX3)

### **Path including the file name:**

Due to Blob Storage working differently than other storage solutions, the last remaining step of our wizard is to write the path of the file in the selected container with your desired file name. **Check the example below.**

![](/files/-M_kToX4Jyz20vZLwSlA)

**The path to this file is** "*test/testteam-direct-export/connector/" .* That means that our exports will save the file in this exact folder. But, to name the exported file, you also need to include the file name in the input field. The outcome should look like this:

![](/files/-M_kUrBM3vbf9b47Jauk)

**And this is the whole setup all together:**

<figure><img src="/files/FHbFnUnoVEHHB2JLRJAA" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/qh9moj5UyIi0lUC05kCc" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.roivenue.com/roivenue-resources/roivenue-training/data-exports/export-to-azure-blob-storage.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
