Deploy continuously to Azure

Last Update: 4/7/2017

Visual Studio 2015 | Team Services | TFS 2015 | Previous version

horizontal-line

information A newer version of Release Management is available

Release Management features have been integrated into the Build & Release hub in Team Foundation Server (TFS) and Visual Studio Team Services. For more information, see Continuous integration on any platform.

The newer web-based version is the recommended alternative to the server and client version described in this topic. If you do not already have Release Management installed, we encourage you to use the web-based version in TFS 2015 Update 2 and above or Visual Studio Team Services instead of the version described here. If you are already using an earlier server and client version, you should be aware that no new features will be added to these versions.

horizontal-line

With Visual Studio 2015 and Visual Studio Team Services you can easily set up continuous deployment to Azure VMs.

To automate your deployments, deploy the same way to multiple environments, and run deployment and validation scripts, follow these steps. For less complex scenarios, such as deploying to Azure websites or cloud services, follow steps to set up continuous deployment from TFVC or Git instead.

Before you start, you'll need:

  • A Visual Studio Team Services account. If you don't have one, sign up now.
  • A team project. If you haven't created it, find out how.
  • Azure VMs. If you need to create them, here's how.
  • An Azure storage account. Create one here.
  • Release Management for Visual Studio extension. To install in Visual Studio, go to Tools, Extensions and Updates, and search for Release Management for Visual Studio.
  • A deployment script. Find out how to set up and check-in this script here.

Create a release definition

Set up stages for each step you need in the release process of your app, along with the environments. You can add stages and environments, too.

  1. In Visual Studio Team Explorer, right-click a build definition and choose Create Release Definition.

    Create a release definition

  2. Set each stage and its environment. To skip a stage, do not set its environment. Dev, QA and Prod stages are created for you automatically.

    Set stages and environments

  3. If you don't see any environments:

    • Add an Azure subscription.

    Add Azure subscription

    • Provide Azure subcription details. If you have an Azure subscription file (.publishsettings file) on your computer, you can browse to that file. If you do not have a local copy of this file, you can download a subscription file. Once you select the file, the tool will detect all the Azure subscriptions available to you and show them in the Subscription ID dropdown list. For the subscription selected, you need to provide a storage account to Release Management tool where the deployment bits can be uploaded during actual deployment.

    Azure subscription details

    • You can update to the latest VSIX by selecting Tools and then Extensions and Updates and searching for Release Management.

    • Then set your environments.

    Set environments for Azure

  4. Provide the path name and file name of the deployment script that you want to run. Same for the configuration script, if your deployment script needs it. For each environment, provide the credentials for an account that has access to run the script. You can use the same credentials for all environments if you want.

    Deployment and configuration scripts

  5. After you create the release definition, launch the Release Management client (you'll be asked to install it if you don't have it already).

    Launch Release Management Client

  6. You can see your release definition in the Release Management client. If you don't see it automatically, go to Configure Apps, vNext Release Templates.

    Release template created from a release definition

    Each new build will trigger a release. You can also manually trigger a new release.

Q: How can I view and customize the deployment actions for each stage of my release?

A: In the Release Management client, go to Configure Apps, vNext Release Templates and open your release template. Learn more here.

Release Template Designer

Q: How can I use a different Visual Studio Team Services account for my releases?

A: In the Release Management client, go to Administration, Settings, and edit the URL.

Set Visual Studio Team Services URL

Go back Back to overview

Help and support

Send suggestions on UserVoice, follow us on Twitter @vsreleasemgmt

or send a smile from the Send-a-Smile link on the menu bar.