Windows Azure – Create Virtual Machine


In previous posts, we were talking about :

  • How adding your account and work with it: – First steps
  • How handle the missing New-AzureVNetwork cmdlet in the Azure PowerShell module: – Network
  • How create an affinity group and optimize your Azure storage: – Storage

Now it’s time to build our first virtual machine. At first let’s see chat we can deploy in our network.


Has you see, we have a “correct” choice for our VM. Let’s start with a Windows 2012 R2 deployment.

Ok, for creating a service we have two cmdlets

  • New-AzureQuickVM
  • New-AzureVM

I read both descriptions, and i can’t find real difference…. so let’s use AzureQuickVM for our needs first.

Like you see it’s possible to deploy a linux VM if you use -Linux switch 😉

This will deploy a VM from a VHD in no time. Keep in mind that you’ll have to specify a new ServiceName each time !



Ok, we have now our VM, but i’m disapointed. No vm configuration.. the cmdlet is well named, it’s a quick configuration :). We’ll have to use more cmdlets to deploy a VM configured like we want:

  • New-AzureVMConfig
  • Add-AzureProvisioningConfig
  • Set-AzureSubnet

How it works… First how to create a configuration object

Ok, once the configuration is created, let’s use the Add-AzureProvisioningConfig cmdlet to add the login/password for the Administrator and specify if it’s a Windows or Linux VM in the configuration object. With this cmdlet you can join and Active Directory and create the Server into a specific OU, you can disable RDP or WinRM. I suggest you to read the man, this is a very powerfull cmdlet. Also, we’ll take a look in a futur post about create/configure an domain and automaticly join a new VM in the domain.

We have prepared our configuration, let’s specify the subnet of our VM.

And now, how to use it together 🙂

We have now our VM in our network 😀


That’s all for today, let’s see again in a futur post to explore the manipulation of your new VM.