• HashiCorp Developer

  • HashiCorp Cloud Platform
  • Terraform
  • Packer
  • Consul
  • Vault
  • Boundary
  • Nomad
  • Waypoint
  • Vagrant
Vault
  • Install
  • Tutorials
  • Documentation
  • API
  • Integrations
  • Try Cloud(opens in new tab)
  • Sign up
Vault Home

Documentation

Skip to main content
  • Documentation
  • What is Vault?
  • Use Cases

  • Browser Support
  • Installing Vault
    • Overview
    • replication
    • sentinel
      • Overview
      • Aerospike
      • Alicloud OSS
      • Azure
      • Cassandra
      • CockroachDB
      • Consul
      • CouchDB
      • DynamoDB
      • Etcd
      • Filesystem
      • FoundationDB
      • Google Cloud Spanner
      • Google Cloud Storage
      • In-Memory
      • Manta
      • MSSQL
      • MySQL
      • OCI Object Storage
      • PostgreSQL
      • Integrated Storage (Raft)
      • S3
      • Swift
      • Zookeeper
    • telemetry
    • ui
    • Log Completed Requests
    • Entropy Augmentation
      ENTENT
    • kms_library
      ENTENT

  • Vault Integration Program
  • Vault Interoperability Matrix
  • Troubleshoot






  • Glossary


  • Resources

  • Tutorial Library
  • Certifications
  • Community Forum
    (opens in new tab)
  • Support
    (opens in new tab)
  • GitHub
    (opens in new tab)
  1. Developer
  2. Vault
  3. Documentation
  4. Configuration
  5. storage
  6. Azure
  • Vault
  • v1.11.x
  • v1.10.x
  • v1.9.x
  • v1.8.x
  • v1.7.x
  • v1.6.x
  • v1.5.x
  • v1.4.x

»Azure Storage Backend

The Azure storage backend is used to persist Vault's data in an Azure Storage Container. The storage container must already exist and the provided account credentials must have read and write permissions to the storage container. The storage account type must support block blobs. This currently includes the general purpose "Storage V2" type with Standard performance (Premium will not work), as well as Premium "Block Blob Storage" (limited region availability).

  • No High Availability – the Azure storage backend does not support high availability.

  • Community Supported – the Azure storage backend is supported by the community. While it has undergone review by HashiCorp employees, they may not be as knowledgeable about the technology. If you encounter problems with them, you may be referred to the original author.

storage "azure" {
  accountName = "my-storage-account"
  accountKey  = "abcd1234"
  container   = "container-efgh5678"
  environment = "AzurePublicCloud"
}

The current implementation is limited to a maximum of 4 megabytes per blob.

azure Parameters

  • accountName (string: <required>) – Specifies the Azure Storage account name.

  • accountKey (string: <optional>) – Specifies the Azure Storage account key, if left empty, uses managed identity auth.

  • container (string: <required>) – Specifies the Azure Storage Blob container name.

  • environment (string: "AzurePublicCloud") - Specifies the cloud environment the storage account belongs to by way of the case-insensitive name defined in the Azure Go SDK.

  • arm_endpoint (string: "") - Specifies the cloud environment the storage account belongs to by way of the Azure Resource Manager endpoint URL.

  • max_parallel (string: "128") – Specifies The maximum number of concurrent requests to Azure.

azure Examples

This example shows configuring the Azure storage backend with a custom number of maximum parallel connections.

storage "azure" {
  accountName  = "my-storage-account"
  accountKey   = "abcd1234"
  container    = "container-efgh5678"
  max_parallel = 512
}
Edit this page on GitHub

On this page

  1. Azure Storage Backend
  2. azure Parameters
  3. azure Examples
Give Feedback(opens in new tab)
  • Certifications
  • System Status
  • Terms of Use
  • Security
  • Privacy
  • Trademark Policy
  • Trade Controls
  • Give Feedback(opens in new tab)