Kudu endpoints: Kudu is the open-source developer productivity tool that runs as a separate process in Windows App Service, and as a second container in Linux App Service.

App Service supports the following deployment mechanisms: The deployment mechanism is the action used to put your built application into the /home/site/When the deployment mechanism puts your application in this directory, your instances receive a notification to sync the new files. These operations can be executed on a build server such as Azure Pipelines, or executed locally.

The specific commands executed by the build pipeline depend on your language stack. A build pipeline reads your source code from the deployment source and executes a series of steps (such as compiling code, minifying HTML and JavaScript, running tests, and packaging components) to get the application in a runnable state. Once you decide on a deployment source, your next step is to choose a build pipeline. While cloud folders can make it easy to get started with App Service, it's not typically recommended to use this source for enterprise-level production applications. App Service also supports OneDrive and Dropbox folders as deployment sources. For development and test scenarios, the deployment source may be a project on your local machine. For production apps, the deployment source is usually a repository hosted by version control software such as GitHub, BitBucket, or Azure Repos. Deployment Components Deployment SourceĪ deployment source is the location of your application code. This article also covers some best practices and tips for specific language stacks. This article introduces the three main components of deploying to App Service: deployment sources, build pipelines, and deployment mechanisms.

Every development team has unique requirements that can make implementing an efficient deployment pipeline difficult on any cloud service.

Azure web apps deployment slots swap