Sure, it’s fun to go into Azure and see all of the cool supported operating system images you can have running in mere minutes. But it is even cooler to take your own internal server or data image and upload that to Azure to use in your VMs. It is even cooler to do it all with PowerShell! If the demo gets a bit technical, be sure to skip to the end for my concluding notes.
If you don’t have your Azure account accessible from the command line, first of all you should install the Windows Azure PowerShell pack available http://www.windowsazure.com/en-us/downloads/. Launch an Azure PowerShell prompt and then run Add-AzureAccount and login
For this example, let’s pretend we have a VHD with important customer data we’ll need to access in our worker VMs from within Azure. Go to Disk management and get our VHD made. For the sake of data transit, we’ll make a small VHD and load it up with important customer data! Continue reading →
I was trying to make a new Linux VM using the Azure PowerShell commandlet New-AzureQuickVM, which basically makes a VM very quickly for you using one of the images available in the catalog. However, I kept running into this message:
New-AzureQuickVM : CurrentStorageAccountName is not accessible. Ensure the current storage account is accessible and in the same location or affinity group as your cloud service.
Now, when you first create a VM in the Azure Web Console, you’ll be prompted to create a Storage Account if you don’t already have one. Assuming you’ve done so, the first thing you should check is to see if the Storage Account is defined within your Azure Subscription. From Powershell, run the