Setting up Azure Blob Storage with the Data Plane
Last updated: April 29, 2025
This guide explains how to configure and test Azure Blob Storage integration with your data plane deployment.
Configuration Steps
Set the following environment variables in your `.env.local` file:
AZURE_STORAGE_ACCOUNT_NAME
AZURE_STORAGE_ACCOUNT_KEY
AZURE_STORAGE_CONNECTION_STRING
ATTACHMENT_BUCKET_NAME
The connection string should follow this format:
DefaultEndpointsProtocol=https;EndpointSuffix=core.windows.net;AccountName=YOUR_ACCOUNT_NAME;AccountKey=YOUR_ACCOUNT_KEY;BlobEndpoint=https://your-account.blob.core.windows.net/;FileEndpoint=https://your-account.file.core.windows.net/;QueueEndpoint=https://your-account.queue.core.windows.net/;TableEndpoint=https://your-account.table.core.windows.net/
Testing the Connection
To test if blob storage is working correctly:
Make sure you're running the latest version of the data plane Docker containers
In the Playground, create a new Message Part of type "File"
Select a model that supports multi-modal inputs
Click the paperclip icon on the right side of the screen to upload a file
If you don't see the paperclip icon for file uploads, verify that you're using the latest API version and that your data plane deployment is up to date.
Common Issues
If you receive an "ATTACHMENT_BUCKET_NAME is not set" error, ensure this environment variable is set both in your dashboard configuration and in your data plane container
Large JSON files uploaded to datasets may be split and stored in Postgres rather than blob storage
The data plane must be running the latest version to support file attachments