Skip to main content
Configure Microsoft Azure Blob Storage as the storage provider for your Maverics deployment. The Console publishes signed config bundles to your Azure Storage container, and Orchestrator instances poll the container for updates.

Prerequisites

  • An active Azure account — with permissions to create and manage storage accounts, containers, and SAS tokens
  • A Maverics Console account — with access to create or edit deployments

Azure Setup

1

Create a Storage Account

In the Azure portal, search for Storage accounts and select Create.Choose your subscription and resource group, enter a unique storage account name, and select a region. Use default settings for the remaining options and click Review + Create.
2

Create a Container

Navigate to your storage account and select Containers under Data storage.Click + Container, enter a name (e.g., maverics-config), and click Create.
3

Generate a SAS Token

On the container, click the three-dot menu (or right-click) and select Generate SAS.Set Signing method to Account key and Signing key to Key 1.Under Permissions, select Create, Add, and Write (these are the minimum permissions the Console needs to publish bundles).Set an appropriate expiry date.Click Generate SAS token and URL.Copy the Blob SAS token value (starts with sv=) — you will paste this into the Console’s SAS Token field.

Storage Configuration

Configure these fields in the Console when creating or editing a deployment with the Microsoft Azure Blob Storage provider.
FieldRequiredDescription
Storage Account NameYesThe unique name of the storage account in Azure
Container NameYesThe name of the container in your storage account
SAS TokenYesThe shared access signature URI granting access to the container
Configuration File PathNoThe path within the container where the bundle is stored
EndpointNoOverride the default Azure API endpoint (e.g., blob.core.usgovcloudapi.net for Azure Government)
The Orchestrator uses the corresponding config source type to retrieve bundles from the deployment provider. If the Console deploys to Azure Blob Storage, the Orchestrator uses the Azure Blob config source to poll for updates.

Common Errors

Azure deployment 403 error

Failed to deploy: error deploying bundle unexpected Azure response: 403
The SAS token used for Azure Blob Storage deployment does not have sufficient permissions. Regenerate the SAS token with Create, Add, and Write permissions on the target container.