Infrastructure: Guidance for Running Workloads, Roles, and Technologies in Azure Virtual Machines
Updated: January 16, 2014
As a first step in moving to the cloud, you can run your on-premises software in Azure Virtual Machines. Why would you do this? First off, you don’t have to buy any hardware. Second, you can very quickly set up a VM in Azure using the gallery, or multiple virtual machines using Windows PowerShell. If you want to try something out, test a configuration or setup, or even run something in production, virtual machines in Azure provide a flexible environment in which you can use Azure Virtual Machines to quickly extend the capacity of your on-premises test or production environments.
Here, we’ve assembled a list of Microsoft content that provides you with the guidance you need to successfully extend or migrate your on-premises server applications (workloads) and Windows Server roles and technologies on virtual machines in the Azure cloud. We’ve also included guidance for setting up the gallery images for images that are available in the virtual machine gallery for some Microsoft partners.
These documentation sets are available to help you run Windows Server roles and technologies:
File and Storage Services - DFS Namespaces and DFS Replication
File and Storage Services - File Server
Message Queuing (MSMQ)
Remote Desktop Services
Windows Server Essentials Experience
If a role or technology is not listed here, no special documentation exists at this time to support running that role or technology in Azure VMs. To find out whether a role or technology is supported, review the Microsoft server software support for Azure Virtual Machines KB article. And, check the on-premises documentation for any additional pointers.