Skip to main content

Azure Blob Storage

This document outlines what is required to receive Unacast Data to your Azure Blob Storage container.

You need to provide your Unacast representative the following information, when the requirements below are met:

  1. The Blob SAS URL
  2. The file path (path) within your container where the data should be delivered

Creating a Container​

Creating an Azure Blob Storage container is the first step in setting up a space for data storage and exchange. You'll need access to your organization's Azure portal with privileges to create and manage storage containers.

Step by step guide to create a container

  1. Sign in to the Azure Portal
  2. Navigate to your Storage Account
  3. In the left menu, select Containers under Data storage
  4. Click + Container to create a new container
  5. Enter a container name (e.g., unacast-data)
  6. Set the Public access level to Private (recommended)
  7. Click Create

Creating a Shared Access Signature (SAS)​

It's important to set the correct permissions to ensure secure access to your container to allow a Unacast service to deliver data to your container.

  1. In the container page, go to Settings → Shared access tokens
  2. Add the required permissions: Read, List, Write
  3. Set the expiry date to at least 1 year ahead, or alternatively use a stored access policy for better management (preferred option)
  4. Click Generate SAS token and URL

Navigate to Storage Account

Creating a Stored Access Policy​

A stored access policy provides better control over SAS tokens by allowing you to revoke or modify access without regenerating the SAS URL.

Step by step guide to create a stored access policy

  1. In your container page, go to Settings → Access policy
  2. Click + Add policy
  3. Enter a policy identifier (e.g., unacast-policy)
  4. Set permissions: Read, List, Write
  5. Set start and expiry times (recommend at least 1 year ahead)
  6. Click OK to save the policy
  7. Click Save at the top of the Access policy page
  8. When creating your SAS token, select the stored access policy instead of setting individual permissions and expiry