This tutorial shows you how easy it is to create an Azure virtual machine in just a few minutes in the Azure preview portal. We'll use a Windows Server 2012 R2 Datacenter image as an example to create the virtual machine, but that's just one of the many images Azure offers. Your image choices depend on your subscription. For example, desktop images may be available to MSDN subscribers.
Azure has two different deployment models for creating and working with resources: Resource Manager and classic. This article covers using the Resource Manager deployment model, which Microsoft recommends for most new deployments instead of the classic deployment model. For details about Resource Manager, see Azure Resource Manager Overview.
You can also create virtual machines using your own images, with Resource Manager templates, or with automation tools. To learn about the different methods, see Different Ways to Create a Windows Virtual Machine.
You can open an Azure account for free: You get credits you can use to try out paid Azure services, and even after they're used up you can keep the account and use free Azure services, such as Websites. Your credit card will never be charged, unless you explicitly change your settings and ask to be charged.
You can activate MSDN subscriber benefits: Your MSDN subscription gives you credits every month that you can use for paid Azure services.
Here's a walkthrough of this tutorial.
Sign in to the Azure preview portal.
On the Hub menu, click New > Compute > Windows Server 2012 R2 Datacenter.
On the Windows Server 2012 R2 Datacenter page, under Select a deployment model, select Resource Manager. Click Create.
After you select the image, you can use Azure's default settings for most of the configuration and quickly create the virtual machine.
On the Create virtual machine blade, click Basics. Enter a Name you want for the virtual machine, the administrative User name, and a strong Password. If you have more than one subscription, specify the one for the new virtual machine, as well as a new or existing Resource group and an Azure datacenter Location.
Click Size and select an appropriate virtual machine size for your needs. Each size specifies the number of compute cores, memory, and other features, such as support for Premium Storage, which will affect the price. Azure recommends certain sizes automatically depending on the image you choose.
Premium storage is available for DS-series virtual machines in certain regions. Premium storage is the best storage option for data intensive workloads such as a database. For details, see Premium Storage: High-Performance Storage for Azure Virtual Machine Workloads.
Click Settings to see storage and networking settings for the new virtual machine. For a first virtual machine you can generally accept the default settings. If you selected a virtual machine size that supports it, you can try out Premium Storage by selecting Premium (SSD) under Disk type.
Click Summary to review your configuration choices. When you're done reviewing or updating the settings, click Create.
While Azure creates the virtual machine, you can track the progress in Notifications, in the Hub menu. After Azure creates the virtual machine, you'll see it on your Startboard unless you cleared Pin to Startboard in the Create virtual machine blade.
After you create the virtual machine, you'll want to log on to it so you can manage its settings and the applications that you'll run on it.
For requirements and troubleshooting tips, see Connect to an Azure virtual machine with RDP or SSH.
If you haven't already done so, sign in to the Azure preview portal.
Click your virtual machine on the Startboard. If you need to find it, click Browse All > Recent or Browse All > Virtual machines. Then, select your virtual machine from the list.
On the virtual machine blade, click Connect.
Click Open to use the Remote Desktop Protocol file that's automatically created for the Windows Server virtual machine.
Type the user name and password you set when you created the virtual machine, and then click OK.
Click Yes to verify the identity of the virtual machine.
You can now work with the virtual machine just as you would with any other server.