---
title: "About Azure Storage prerequisites"
slug: "about-azure-storage-prerequisites"
description: "Learn the prerequisites for using Azure Storage as a Supermetrics destination, including permissions, access keys, and IP allowlisting requirements."
updated: 2025-11-19T18:19:58Z
published: 2025-11-19T18:19:58Z
canonical: "docs.supermetrics.com/about-azure-storage-prerequisites"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.supermetrics.com/llms.txt
> Use this file to discover all available pages before exploring further.

# About Azure Storage prerequisites

Some requirements need to be met to start using Azure Storage as a Supermetrics destination. These prerequisites ensure that a working connection can be set up to successfully transfer data to your Azure Storage container.

> [!NOTE]
> About permissions
> 
> You may need specific permissions to verify these prerequisites are met. If you're unable to access some information, please get in touch with your Azure admin.

## Prerequisites

### Storage account with container support

Your destination should be an Azure Storage account that supports containers, such as BlobStorage, Storage, or StorageV2. See Azure documentation to learn more about [storage accounts](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-overview).

### Authentication and Permissions

You can authenticate using either your account’s main **Access Key** or the more granular **SAS Token**.

****Method 1: Access Key (Gives full account access)****

This method uses your **Access key** for authentication. This key grants Supermetrics broad access to your entire storage account. See [Azure’s documentation](https://docs.microsoft.com/en-us/azure/storage/common/storage-account-keys-manage) to learn more about Access Keys.

- **Required Role:** At a minimum, the role **Reader & Data Access** is required for the storage account.

****Method 2: SAS Token (Recommended - limited access)****

A Shared Access Signature (SAS) token allows you to grant limited, container-specific access without sharing your main account keys. This is the most secure method.

When you select this method, you will need to provide:

- **Storage account:** The name of your storage account.
- **SAS Token:** The SAS Token string you generated.

**How to create a SAS Token**

1. You must generate a SAS token in your Azure Portal. See Azure’s documentation for instructions on [how to create a SAS token](https://docs.microsoft.com/en-us/azure/storage/common/storage-sas-overview).
2. **Required permissions**: When generating the token, you must grant the following permissions.
  1. Read
  2. Write
  3. List
  4. Delete
  5. Create
3. You must also go to the **Allowed resource types** section and enable the following:
  1. Object
  2. Container
  3. Blob
4. Expiry date: Ensure you set an expiry date that’s far enough in the future. If the SAS token expires, your Supermetrics transfers will fail until you generate and provide a new token.

### IP allowlisting

If your storage account only allows access from selected networks, IP allowlisting is needed. At the minimum, the role of the [Storage Account Contributor](https://docs.microsoft.com/en-us/azure/role-based-access-control/built-in-roles#storage-account-contributor) is required to modify the firewall settings of a storage account. See Azure documentation for instructions on [managing IP network rules](https://docs.microsoft.com/en-us/azure/storage/common/storage-network-security?tabs=azure-portal#managing-ip-network-rules).

[Grant access to these Supermetrics IP addresses](/v1/docs/about-ip-address-allowlisting-for-data-warehouse-destinations). Don't forget to add your own IP address to avoid losing access to your storage account.

## More resources

- [How to configure an Azure Storage destination](/v1/docs/how-to-configure-an-azure-storage-destination)
- [How to create a destination](/v1/docs/how-to-connect-to-a-data-warehouse-destination)
- [How to create a transfer](/v1/docs/how-to-create-a-transfer)