Use PowerShell to Create a New Virtual Machine in Windows Azure Running Server 2012 R2
In this Ask the Admin, I’ll show you how to connect to your Azure subscription using PowerShell and create a new virtual machine (VM) using the New-AzureQuickVM command.
Before you can use PowerShell to remotely manage Windows Azure, you will need to set up remote PowerShell management for Windows Azure.
Let’s start by setting the Azure subscription in PowerShell. Open a PowerShell prompt with elevated privileges:
- In the PowerShell console, type Get-AzureSubscription, and make a note of the SubscriptionName in the output. In my case, Pay-As-You-Go.
- Type Get-AzureStorageAccount, and make a note of Label in the output. My storage account is labelled portalvhdsxgwgzn2ml54p5.
- Now set the Azure subscription in PowerShell as follows using the SubscriptionName and Label parameters from the commands above: Set-AzureSubscription “Pay-As-You-Go” -CurrentStorageAccount portalvhdsxgwgzn2ml54p5
Now that the subscription is set, chose an image from the gallery to use as the basis for the new VM.
Say Goodbye to Traditional PC Lifecycle Management
Traditional IT tools, including Microsoft SCCM, Ghost Solution Suite, and KACE, often require considerable custom configurations by T3 technicians (an expensive and often elusive IT resource) to enable management of a hybrid onsite + remote workforce. In many cases, even with the best resources, organizations are finding that these on-premise tools simply cannot support remote endpoints consistently and reliably due to infrastructure limitations.
- Type Get-AzureVMImage to get a list of the available images. I’m going to use the latest image of Windows Server 2012 R2 for my VM, and the Image name is a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-R2-201311.01-en.us-127GB.vhd
Finally, create the VM. Run the command shown below, replacing the –AdminUsername and –Password parameters with any username and password that you choose. The –ServiceName and –Name parameters can be the same.
Each VM should run in its own cloud service, unless you plan to load balance one or more VMs. You might need to experiment with the –ServiceName parameter to successfully create a new VM, as it should be globally unique. It’s often the case that you will specify an already existing cloud service name.
The –location parameter can be set to East Asia, Southeast Asia, North Europe, West Europe, Central US, East US, East US 2, or West US.
https://petri.com/create-virtual-machine-in-windows-azure-powershell New-AzureQuickVM -Windows -ServiceName mysrv1 -Name mysrv1 -ImageName a699494373c04fc0bc8f2bb1389d6106__Windows-Server-2012-R2-201311.01-en.us-127GB.vhd -AdminUsername mysrv1admin –Password ********* -location “North Europe”
If you look in the Azure management portal window under virtual machines, you should now see an entry for the new VM. It can take up to five minutes for the provisioning process to complete.