This post is about configuring automatic scaling in Azure App Service. Automatic scaling is a new feature available in Azure App Service scale out configuration. The feature of automatic scaling is a novel way to expand the capacity of your web applications and App Service Plans without having to make scaling decisions yourself. It differs from the existing Azure autoscale, which allows you to specify scaling rules according to schedules and resources. With automatic scaling, you can modify scaling settings to enhance your application’s performance and prevent delays in starting up. This Automatic scaling feature is in preview. And it is available for Premium Pv2 and Pv3 pricing tiers, and supported for all app types: Windows, Linux, and Windows container.

We can access the configuration from the App Service, and select Scale out (App Service plan). And we can select the Automatic (preview) option.

Once you select the Automatic (preview) option, we will be able to configure different options, like Maximum burst, Always ready instances, Enforce scale out limit and Maximum scale limit.

There is one more configuration is available - Prewarmed instance - The prewarmed instance setting provides warmed instances as a buffer during HTTP scale and activation events. Prewarmed instances continue to buffer until the maximum scale-out limit is reached. The default prewarmed instance count is 1 and, for most scenarios, this value should remain as 1. - but this configuration we can’t change from Azure Portal. We can change it using Azure CLI.

Here is the command - az webapp update --resource-group myresourcegroup --name mywebapp --prewarmed-instance-count 2

We can find more details about the Automatic scaling in Azure App Service here

Happy Programming.