Hence, cloning an Azure App Service deployment slot itself does not incur any additional cost, but the resources used by the cloned slot will still count towards the resource usage of the original App Service plan. So, it's important to monitor your resource usage and adjust your App Service plan accordingly to avoid unexpected charges. This means that if you have a limited amount of resources available in your App Service plan, creating multiple deployment slots could potentially impact the performance of your app.Īlso, note that if you configure the cloned deployment slot to use additional resources (such as a larger VM size or more instances), this could result in additional costs.

However, note that the resources used by the cloned deployment slot will still count towards the resource usage of the original App Service plan. To find out the number of slots your app's tier supports, see App Service limits. There's no additional charge for using deployment slots. Each App Service plan tier supports a different number of deployment slots.

Azure web app deployment slots pricing