Powershell saying storage account doesn't exist

4
votes

In powershell I verify that it exists by calling the context.

New-AzureStorageContext -StorageAccountName "testdisks401" -StorageAccountKey "...."

Result

StorageAccountName : testdisks401
BlobEndPoint       : https://testdisks401.blob.core.windows.net/
TableEndPoint      : https://testdisks401.table.core.windows.net/
QueueEndPoint      : https://testdisks401.queue.core.windows.net/
FileEndPoint       : https://testdisks401.file.core.windows.net/
Context            : Microsoft.WindowsAzure.Commands.Common.Storage.AzureStorageContext
Name               :
StorageAccount     : BlobEndpoint=https://testdisks401.blob.core.windows.net/;QueueEndpoint=https://testdisks401.queue.core.windows.net/;TableEndpoint=https://testdi
                 sks401.table.core.windows.net/;FileEndpoint=https://testdisks401.file.core.windows.net/;AccountName=testdisks401;AccountKey=[key hidden]
EndPointSuffix     : core.windows.net/

When I try to set it here:

Set-AzureSubscription -SubscriptionName 'XXXX' -CurrentStorageAccount "testdisks401"

I get this

Set-AzureSubscription : ResourceNotFound: The storage account 'testdisks401' was not found.
At line:1 char:1
+ Set-AzureSubscription -SubscriptionName 'XXX
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : CloseError: (:) [Set-AzureSubscription], CloudException
+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.Profile.SetAzureSubscriptionCommand

Been stuck for quite a while. I basically want to write shellscript to create a VM from an existing OS disc. I managed to create a copy of an existing disc using powershell (used context from first command to make it work). But now that I am trying to create the VM configuration using this:

 $vmI1 = New-AzureVMConfig -Name "TestRecover" -InstanceSize Small -AvailabilitySetName 'RDGW' -DiskName 'MY-OS-Disk-Name'

I get this error:

New-AzureVMConfig : Must specify MediaLocation or set a current storage account using Set-AzureSubscription.
At line:1 char:9
+ $vmI1 = New-AzureVMConfig -Name "TestRecover" -InstanceSize Small -Av ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (:) [New-AzureVMConfig], ArgumentException
+ FullyQualifiedErrorId : System.ArgumentException,Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.NewAzureVMConfigCommand

A solution has already been provided for this which brought me here (stuck on missing storage account error).

3
powershellazureazure-storageazure-powershell
Please check if the storage account you're using is a Classic storage account or Azure Resource Manager storage account. My guess is that the cmdlet Set-AzureSubscription uses one of the type and your storage account is of another type. – Gaurav Mantri
@GauravMantri The storage account is Azure Resource Manager type. I do not believe the Set-AzureSubscription differentiates between the types. Its documentation does not mention such a case to my knowledge (msdn.microsoft.com/library/dn790376.aspx) – Moussa Khalil
Or not I think that's the case. I created a classic storage account to test and that was the case. This is very weird. @GauravMantri Please add it as an answer for me to accept – Moussa Khalil

3 Answers

8
votes

Set-AzureSubscription Cmdlet expects the storage account specified via -CurrentStorageAccount parameter to be a classic storage account.

Please make sure that you're specifying a classic storage account's name and not a resource manager storage account's name.

1
votes

If you need Storage Account created using ARM, then you can use these commands:

$SubscriptionName = "MySubscription"
$StorageAccountName = "MyStorage"
$ResourceGroup = "MyResourceGroup"
Get-AzureRmSubscription –SubscriptionName $SubscriptionName | Select-AzureRmSubscription
Get-AzureRmStorageAccount -AccountName $StorageAccountName -ResourceGroupName $ResourceGroup
$key = (Get-AzureRmStorageAccountKey -AccountName $StorageAccountName -ResourceGroupName $ResourceGroup).Key1
$Ctx = New-AzureStorageContext –StorageAccountName $StorageAccountName -StorageAccountKey $key
1
votes

How did you create that storage account?

If you created it as an RM Account that would explain the error you are getting. Antohter option is that testdisks401 is on the same subscription as you are trying to set.

Try to do the following:

Set-AzureSubscription -SubscriptionName 'XXXX'
Get-AzureStorageAccount | ft StorageAccountName

this will get you a list of classic storage accounts (non RM) in the XXXX subscription.

And then do the same for the RM accounts like this:

Login-AzureRmAccount -SubscriptionName 'XXXX'
Get-AzureRMStorageAccount | ft StorageAccountName

If the testdisks401 account is in the RM list, then you either need to switch to the RM model, or you need to create a new storage account with the classic model.

edit: forgot to mention that new-azurestoragecontext, does not validate anything. Try to run the following:

New-AzureStorageContext -StorageAccountName "bla" -StorageAccountKey "askjlksdfjldskgfjflkjdsflksj"

it will also give you a nice context object that leads nowhere:

StorageAccountName : bla
BlobEndPoint       : https://bla.blob.core.windows.net/
TableEndPoint      : https://bla.table.core.windows.net/
QueueEndPoint      : https://bla.queue.core.windows.net/
FileEndPoint       : https://bla.file.core.windows.net/
Context            : Microsoft.WindowsAzure.Commands.Common.Storage.AzureStorageC
Name               :
StorageAccount     : BlobEndpoint=https://bla.blob.core.windows.net/;QueueEndpoin
EndPointSuffix     : core.windows.net/