Azure BLOB storage
Configure your application to be able to upload recording files to your organizations Azure BLOB Cloud Storage.
Container Name
Azure Blob storage is Microsoft's object storage solution for the cloud. Blob storage is optimized to deal with large amounts of unstructured data, such as audio and video media files.
Storage Account
A container organizes a set of blobs, similar to a directory in a file system. A storage account provides a unique namespace in Azure where your data can be stored. A storage account can include an unlimited number of containers, and a container can store an unlimited number of blobs. For more information see Storage Account Overview .
Permissions and connection requirements
- Use a connection string that contains a storage account access key (Shared Key authorization). This is the only supported option.
- Connection strings that contain only a shared access signature (SAS) are not supported. Auvious creates short-lived, read-only signed URLs so that agents can play and download recordings directly from your storage, and Azure signs these URLs with the account key. A SAS can't be used to create another SAS, so with a SAS-only connection string, playback, downloads and the storage verification fail.
- Shared Key access must be allowed on the storage account (the Allow storage account key access setting).
- An access key grants access to all data in the storage account, not only to one container. We recommend a storage account dedicated to Auvious recordings. Azure provides two access keys per account, so you can rotate them without breaking existing links: switch the Auvious connection string to the second key, wait at least 24 hours (longer than any playback or download link stays valid), then regenerate the first key. Regenerating a key immediately invalidates every link signed with it, so never regenerate the key Auvious is currently using.
During verification, Auvious reads the container properties, uploads, downloads, copies and deletes a test blob, and generates a short-lived signed URL, so missing permissions or network access will cause test failures.
Requests from agents' and customers' browsers through signed URLs must also be allowed by the storage account's network rules. See Storage Network Access.
Troubleshooting
| Error/message | Likely cause | Fix |
|---|---|---|
| AuthenticationFailed / AccountIsDisabled / "not a valid base64" | Bad/expired connection string or disabled account | Replace storageProviderConnectionString with a valid account-key connection string; ensure account enabled |
| 403 AuthorizationFailure | Public network access is disabled on the storage account, or the storage account firewall blocks the source IP address | If public network access is disabled, allowlisting IP addresses has no effect: enable it for selected networks. Then allow the Auvious server IP addresses and the agent and customer networks that open signed URLs (see Storage Network Access) |
| 403 KeyBasedAuthenticationNotPermitted | Shared Key access is disabled on the storage account | Enable Allow storage account key access on the storage account |
| Signed URL generation fails, or 403 AuthorizationPermissionMismatch | Possibly a connection string that contains a SAS instead of an account key | Replace storageProviderConnectionString with an account-key connection string. If it already contains an account key, check the underlying error |
| 404 ContainerNotFound / BlobNotFound | Wrong container name or blob deleted | Correct storageProviderBucket; rerun verification after object exists |
| DNS/UnknownHost | Typo or private endpoint not reachable | Fix account endpoint in connection string; ensure network path to endpoint |
| Copy timeout during verify | Cross-region latency or large blob copy | Increase availability near the storage account; reduce object size used for verification |
For Auvious to be able to access your Azure Storage account your Azure administrator will first need to configure and create a new storage account. For information on creating a new storage account see Create an Azure Storage Account .
Container
From within the new storage account your Azure administrator must now create a new container where your recording data will be stored, as depicted below.
Once your blob container has been successfully created and configured the name of the container must be entered in
the Container Name property under the Auvious Storage Provider configuration page, as depicted below.
Connection String
The newly created storage account also contains Access Keys. These access keys are used to authenticate applications when making requests to this Azure storage account.
As depicted above each Access Key contains a Connection String. The Connection String includes the authorization information required for your application to access data in an Azure Storage account at runtime using Shared Key authorization.
For help on how to view your account's access keys and copy a connection string, see Manage storage account access keys .
For Auvious to remotely access you Azure storage account your Azure administrator will need to copy a ** Connection String** specifically for this purpose.
Please enter the relevant Connection String property under the Auvious Storage Provider configuration page, as depicted below.
Review & Test
In the final step you can review and go back to make any necessary corrections.
When you are ready, you can test your configuration to ensure that Auvious can successfully access your storage provider.
