A new way to deploy VSTS in the Azure portal

22 January 2016

Deploying an Azure website by using Visual Studio Team Services (VSTS) works differently than a deployment that uses Kudu. When you set up a deployment from source control in the Azure portal, you get a number of options:
  • Visual Studio Team Services
  • OneDrive
  • Local Git repository
  • GitHub
  • Bitbucket
  • Dropbox
  • External repository
All of these options use the Kudu deployment engine. For the Visual Studio Team Services option, Kudu only supports the Git repository. For more information, see Can I host my repo on VSTS and have Kudu build it? This article explains some of the differences you may encounter, and how to report and investigate them: VSTS vs Kudu deployments.

Free account

Learn and build with $200 in credit, and keep going for free

Start for free

Visual Studio

Subscribers get up to $1800 per year of Azure services

Activate now

Start-ups

Join the BizSpark programme and get free Azure services

Learn more