Windows Azure New Feature–The VM Role

Windows Azure Virtual Machine (VM) Roles allow you to run a customized instance of Windows Server 2008 R2 in Windows Azure, making it easier to move applications to the cloud.


A VM Role differs from a Web Role and a Worker Role, because with these roles, you focus on creating and running your code in an operating system that is managed by Windows Azure; for the VM role, you provide a preconfigured operating system image. Developers have full control of the operating system image.

Administrators can remote into the virtual machine of all roles to perform maintenance and troubleshooting tasks. Just as with the other roles in Windows Azure, you can perform orchestrated operating system updates by using an “update domains,” and you can allocate virtual machine instances across fault domains.

For more information see the MSDN documentation on the VM Role and this hands-on-Lab in the new Windows Azure Training kit.


Comments (2)

  1. Christian Weyer says:

    Hey Bill,

    maybe you want to mention that – although having the opportunity to upload a VM – this is still not IaaS. All the Azure-ness, like Fabric Controller being the master of desaster, still counts.

    I.e. the apps you want to move into Azure and you want to migrate already have to play the 'Azure rules'. Essentially, being stateless.



  2. Wzack says:

    Christian: You are absolutely correct. I did mention that in my recent Azure Design Patterns post:…/design-patterns-anti-patterns-and-windows-azure.aspx.

    State is the big issue (for now).