1-800-691-1991 | 9am - 8pm ET

No Azure storage accounts can be found

KB ID: 2247
Product: Veeam Backup & Replication
Version: 9.5
Published: 2017-02-16
Last Modified: 2020-08-13


When attempting a direct restore to Azure through the B&R console, or when using PowerShell scripting for the same purpose (Get-VBRAzureStorageAccount), no storage accounts can be found, or the specified storage account is not returned.


The storage account(s) specified are blob storage accounts, which are not usable for VM restores.


Specify or select a valid general purpose storage account. If none exist, one must be created within your Microsoft Azure subscription before you can perform restores to Azure.

More information

Microsoft Azure storage accounts come in two varieties. The first is “General purpose”, while the second is “Blob storage”. From the tooltip in Azure:
  • General purpose storage accounts provide storage for blobs, files, tables, and queues in a unified account. 
  • Blob storage accounts are specialized for storing blob data and support choosing an access tier, which allows you to specify how frequently data in the account is accessed. 
Blob storage is specifically for “unstructured data”, which ultimately means it’s a sort of file share, and much more massively scalable. This storage type, however, is not optimized for virtual machine disks and, contrasted with a general purpose storage account, cannot have SSD storage (“Premium performance”) selected.
Per the user guide, blob storage accounts will not be displayed in the list of subscriptions.
General purpose storage accounts, also referred to as “Disk storage”, are premium storage for high-I/O needs, which means these are more optimized for virtual machine disks. These should be created if your goal is to work with VMs in Azure.
KB ID: 2247
Product: Veeam Backup & Replication
Version: 9.5
Published: 2017-02-16
Last Modified: 2020-08-13

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.


error icon

Oops! Something went wrong.

Please go back try again later.