Slots can reduce the overall downtime of web services by auto-swap capabilities and full integration in pipeline workflow to test and validate code changes before pushing them to production. Part 2: Continuous Deployment for Azure App Serviceĭeployment slots are live applications running with their unique hostname, however, connected to a particular app service plan. Part 1: Up and Running with Azure App Service If it's your first time here, please check out other articles in the series: Last week, we talked about how you can use CI-CD in App Service to enable DevOps capabilities for your web services. Deleting one of the cloud services (of the swappable pair) will result in the SwappableCloudService property of the remaining cloud service being cleared.This is the third article in the 'Getting Started with Azure App Service' Series where I publish in-depth tutorial and walkthrough on using Azure App Service and best practices every week. It cannot be deleted or changed to another value. Once set, the SwappableCloudService property is treated as readonly.

Any subsequent update to these cloud services will need to specify this property failing which an error will be returned indicating that the SwappableCloudService property cannot be deleted or updated. Upon deployment of the second cloud service, both the cloud services have their SwappableCloudService property set to point to each other. You can swap the deployments by using an Azure Resource Manager template (ARM template), the Azure portal, or the REST API. Once the second pair of cloud service is deployed, it can not be made swappable with an existing cloud service in subsequent updates. You must make a cloud service swappable with another cloud service when you deploy the second of a pair of cloud services for the first time. You can't swap between an Azure Cloud Services (classic) deployment and an Azure Cloud Services (extended support) deployment.

Azure web apps deployment slots swap