A new way to deploy VSTS in the Azure portal
Share
Services
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](https://github.com/projectkudu/kudu/wiki/VSO-vs-Kudu-deployments#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](https://github.com/projectkudu/kudu/wiki/VSTS-vs-Kudu-deployments).
* App Service
* Application Insights
* Features
* Services
* [ App Service](https://azure.microsoft.com/en-gb/products/app-service/)
What else is happening at Microsoft Azure?
Read update
Services
Share
Generally Available: Storage account default maximum request rate limit increase to 40,000 requests per second
December 12th, 2024
Services
Share
Read update
Services
Share
Generally Available: Regional Disaster Recovery by Azure Backup for AKS
November 22nd, 2024
Services
Share
Generally Available: Enhancements on Azure Container Storage for performance, scalability, and operational insights
November 19th, 2024
Services
Share