--- title: "Azure Blob Storage" slug: "azure-blob-storage" updated: 2024-09-17T10:48:47Z published: 2024-09-17T10:48:47Z canonical: "help.hyperscience.ai/azure-blob-storage" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt > Use this file to discover all available pages before exploring further. # Azure Blob Storage ## Azure Blob Storage setup To set up Azure Blob Storage as a file store, include the following in the ".env" file: ```bash FORMS_STORAGE_MODE= IMAGE_STORAGE_AZURE_CONTAINER_NAME= IMAGE_STORAGE_AZURE_ACCOUNT_NAME= IMAGE_STORAGE_AZURE_ACCOUNT_KEY= ``` > [!NOTE] > In v32 and later, you can choose to store your system-level credentials in a secrets manager. To learn more about our secrets-management integration, see [Secrets Management](/deployment/docs/secrets-management). ### Value of *FORMS_STORAGE_MODE* In v36.0.6+ and v37 and later, file stores have a six-level directory structure. This structure minimizes the number of files in each directory, allowing for faster data retrieval and improving performance in high-volume instances.The value of *FORMS_STORAGE_MODE* depends on the version of Hyperscience you're running: - v36.0.6 + or v37 or later: *AZURE_BB_EX* - v36.0.5 or earlier: *AZURE_BB* If you are upgrading to v36.0.6+ or v37 or later, your file store will use the optimized directory structure by default. If you want to continue using the older directory structure, set *FORMS_STORAGE_MODE* to *AZURE_BB_LEGACY*. ### Optional *IMAGE_STORAGE_AZURE_CUSTOM_DOMAIN* variable If you have set up a custom, private domain for your Azure file store, our default *blob.core.windows.net* domain won't work for your instance. Instead, in v37.0.4 and later, you can add your custom domain to your Hyperscience configuration by adding the following to your ".env" file: ```bash IMAGE_STORAGE_AZURE_CUSTOM_DOMAIN= ``` For example, if your custom domain is *xyz.example.com*, you would add: ```plaintext IMAGE_STORAGE_AZURE_CUSTOM_DOMAIN=xyz.example.com ```