Deployment

Automated

Automated deployments allow you to automatically build, test and deploy new versions of your app by pushing code into a designated "production" branch. Azure App Services support automated deployments from the following sources:

• ADO
• GitHub
• BitBucket

Manual

You can also manually push code into your Azure App Service with varying levels of "automation" up to but not including full production branch push automation (which would be considered an automated deployment.

• Git - App Service web apps have their own Git URL which, if pushed to, will deploy your application
• CLI - az webapp up packages and deploys your app - it can also create a new App Service if you don't already have one
• Zip - you can use curl to send a zip file containing your application files to your App Service
• FTP/S - you can use traditional FTP or FTPS to push code to you App Service

Slots

App > Deployment > Deployment slots

Slots allow you to warm up instances of a new release to match your production scale, which can then be "swapped", eliminating downtime.

Continuous deployment

If you use a branch model which includes WIP versions at various stages pre-production, these can also be continuously deployed automatically to non-production slots, where they can be tested continuously. For basic web apps, this automation is simple, for containers it's a little more complex:

1. Build and tag new image
2. Push tagged image to ACR
3. Point deployment slot to new image tag

Sidecars

Sidecar containers allow you to extend your main application with additional functionality without tightly coupling them to your main container. Examples of sidecar containers:

• Monitoring
• Logging
• Configuration
• Networking services

See Sidecars for more information.