We recently built an infrastructure for deploying infrastructure and applications using Azure Resource Manager and templates. To deploy the cloud service, you must first configure your Azure Storage account. Recently, this has been achieved by running:
Switch-AzureMode AzureResourceManager New-AzureStorageAccount -ResourceGroupName $resourceGroupName -StorageAccountName $storageAccountName -Location $locationName -Type Standard_LRS
This will create a storage account that the New-AzureDeployment cmdlet can use to deploy. As far as I remember, the created vault account would be the one that is now designated as "classic" in the user interface. However, with the latest changes, the storage account created using the script above is non-classic (V2). This V2 account is not recognized by New-AzureDeployment, and it throws it into a Powershell script:
New-AzureDeployment: ResourceNotFound: account "teststorage" not found.
If I manually create a classic vault account in the user interface, I can use it for my deployment and it works fine.
So, you can do one of the following:
- Use a vault account that will be created as classic using Powershell?
- Have the New-AzureDeployment cmdlet use a V2 storage account through Powershell?
source share