Create SharePoint 2013 development environments quickly on Azure

In this blog post we will walk you through creating a SharePoint 2013 development environment on Windows Azure using the Visual Studio Ultimate 2013 RC image.

Have you ever been in a situation where you need to create a SharePoint 2013 development environment quickly? Are you still working on SharePoint Solutions or are you building apps for SharePoint and you need a machine with SharePoint 2013 and Visual Studio 2013 on it? Do you just want to try out SharePoint 2013 development?

If you answered ‘yes’ to one or all of the questions mentioned above, and you have an MSDN subscription, we have good news for you.

We have released an Azure developer image that comes with SharePoint 2013 and Visual Studio 2013 Ultimate RC pre-installed. The image also contains scripts to provision and configure SharePoint 2013 with or without an Active directory running on a different machine.

Be aware that, if you don’t have an Azure subscription, you can activate your Azure benefit that comes with your MSDN subscription. As part of your subscription, you have free Windows Azure credits - up to US$150 per month! You can use them to build SharePoint development & test environments on demand with virtual machines and more. See Windows Azure Benefit for MSDN Subscribers for more information. In addition we have optimized Windows Azure billing—meaning you only pay for the virtual machines as long as you are working on them. When you are finished working, just shut down the virtual machine and you will no longer be billed for it.

Let’s have a brief look at the image and how to provision it. There are two ways to provision a virtual machine of that image. You can either use the portal or use PowerShell.

Use the Windows Azure management portal:

To create a new virtual machine from the Azure Management Portal, go to and follow the steps below:

  1. Sign in to the Windows Azure Portal
  2. Choose the plus sign (+) at the bottom of the Portal page
  3. Choose Compute>Virtual Machine>From Gallery
  4. Scroll down the image list and choose Visual Studio 2013 Ultimate RC and choose the arrow on the lower right corner
Figure 1. Virtual Machine image selection dialog boxFigure 1. Virtual Machine image selection dialog box

The virtual machine creation wizard guides you through the process. We recommend an X-Large VM Size for SharePoint development.

The virtual machine provisioning takes about 5-10 minutes. Once the machine has been provisioned you can use remote desktop to connect to the machine. The next step is to provision SharePoint 2013. As mentioned the image is pre-loaded with software and scripts. The configuration scripts and software can be accessed by choosing the “Configure Developer Desktop” shortcut icon on your desktop. The scripts folder contains two scripts relevant for SharePoint 2013 provisioning and configuration and allow you to provision SharePoint as Stand Alone or SharePoint with Active Directory (the script assumes that the Active Directory is hosted on another Virtual Machine).

Both scripts will configure a basic SharePoint environment, meaning they create a Central Administration site and a Web Application with a Root Site collection. The Figure 2 shows the provisioned virtual machine with SharePoint Central Administration and sign in screen to use Visual Studio for the first time.

Figure 2. Visual Studio sign inFigure 2. Visual Studio sign in

Please see Visual Studio Ultimate 2013 RC Gallery image for MSDN subscribers for a detailed walkthrough of how to provision and configure a virtual machine for SharePoint development as well as documentation for the included PowerShell scripts.

Use Windows PowerShell:

As mentioned in the beginning we also released scripts that allow you to provision a SharePoint 2013 development environment using PowerShell. In addition, the scripts also allow you to provision a Windows Server 2012 virtual machine with an Active Directory and join SharePoint to that domain. This opens up the full scale of SharePoint development. Full documentation for the scripts can be found here: All the scripts can be downloaded from here:

Once your development environment is set up you can even access your on-premises source control from Visual Studio on the virtual machine by using an Azure Point to Site connection. Be aware that when setting up an Azure point to site connection, you must first provision the virtual machine into a virtual network. For more information about Azure Point to site connections see


Boris Scholl

Sr. Program Manager, Cloud Platform Tools

Comments (12)
  1. Boris – Thank you for sharing this information!

  2. Mike Walsh says:

    It would be useful to have a time-restricted SP 2013 image that didn't insist on the user having an MSDN subscription!

  3. Suresh says:


    I have a question, Can I create SharePoint 2013 image for free If I have a MSDN subscription?

  4. Boris Scholl says:

    Hi Suresh,

    you can find a detailed description of the Windows Azure Benefits for MSDN Subscribers here:…/msdn-benefits-details

    Here is an excerpt of that page:

    No additional charge for MSDN software

    Get access to preconfigured virtual machine images with SQL Server, BizTalk Server and other software over time that comes with your MSDN subscription. Alternatively, upload your own virtual machine with your MSDN software. Your Windows Azure credits last longer because there is no additional charge for the MSDN software that runs on top of Windows Server such as SQL Server.



  5. Boris Scholl says:

    Hi Mike,

    there is a SharePoint 2013 trial image in the public Azure gallery. The image has only SharePoint 2013 on it but not Visual Studio though.



  6. Manjeera says:

    I've created a BDC model through visual studio 2012, deployed it and crawled successfully. I'm able to get the search results as well. But the problem is search results are coming without security trimming. My table is having a column 'ACL' with security information in varbinary format. I've added <Property Name="WindowsSecurityDescriptorField" Type="System.String">ACL</Property> in Specificfinder MethodInstance as well.

    Please help me on this.

  7. Andrew Allison says:

    This saved me a lot of hair pulling and tantrums.  Thanks a lot..

  8. Gamil Silvergeek says:

    Many thanks

  9. Tim Jones says:

    I would think one of the primary use cases for setting up these VMs would be for creating SharePoint 2013 app model apps.  I tried a very simplistic SharePoint-hosted app from Visual Studio, and quickly realized you still need to run through several configuration steps after running the supplied powershell provisioning scripts.  Since I don't have a lot of experience using Azure VMs, I'm currently stuck trying to figure out how to create the required forward lookup zone for my custom app domain in DNS.

Comments are closed.

Skip to main content