Get started with Autoscale in Azure

This article describes how to set up your Autoscale settings for your resource in the Microsoft Azure portal.

Azure Monitor autoscale applies only to Virtual Machine scale sets, Cloud Services, App Service - Web Apps, and API Management services.

Discover the Autoscale settings in your subscription

You can discover all the resources for which Autoscale is applicable in Azure Monitor. Use the following steps for a step-by-step walkthrough:

  1. Open the Azure portal.
  2. Click the Azure Monitor icon on the top of the page. Screenshot on how to open Azure Monitor.
  3. Click Autoscale to view all the resources for which Autoscale is applicable, along with their current Autoscale status. Screenshot of Autoscale in Azure Monitor.

You can use the filter pane at the top to scope down the list to select resources in a specific resource group, specific resource types, or a specific resource.

Screenshot of View resource status.

For each resource, you will find the current instance count and the Autoscale status. The Autoscale status can be:

  • Not configured: You have not enabled Autoscale yet for this resource.
  • Enabled: You have enabled Autoscale for this resource.
  • Disabled: You have disabled Autoscale for this resource.

Additionally, you can reach the scaling page by clicking on All Resources on the home page and filter to the resource you're interested in scaling.

Screenshot of all resources.

Once you've selected the resource that you're interested in, select the Scaling tab to configure autoscaling rules.

Screenshot of scaling button.

Create your first Autoscale setting

Let's now go through a simple step-by-step walkthrough to create your first Autoscale setting.

  1. Open the Autoscale blade in Azure Monitor and select a resource that you want to scale. (The following steps use an App Service plan associated with a web app. You can create your first ASP.NET web app in Azure in 5 minutes.)

  2. Note that the current instance count is 1. Click Custom autoscale. Scale setting for new web app.

  3. Provide a name for the scale setting, and then click Add a rule. This opens as a context pane on the right side. By default, this sets the option to scale your instance count by 1 if the CPU percentage of the resource exceeds 70 percent. Leave it at its default values and click Add. Create scale setting for a web app.

  4. You've now created your first scale rule. Note that the UX recommends best practices and states that "It is recommended to have at least one scale in rule." To do so:

    a. Click Add a rule.

    b. Set Operator to Less than.

    c. Set Threshold to 20.

    d. Set Operation to Decrease count by.

    You should now have a scale setting that scales out/scales in based on CPU usage. Scale based on CPU

  5. Click Save.

Congratulations! You've now successfully created your first scale setting to autoscale your web app based on CPU usage.


The same steps are applicable to get started with a Virtual Machine Scale Set or cloud service role.

Other considerations

Scale based on a schedule

In addition to scale based on CPU, you can set your scale differently for specific days of the week.

  1. Click Add a scale condition.
  2. Setting the scale mode and the rules is the same as the default condition.
  3. Select Repeat specific days for the schedule.
  4. Select the days and the start/end time for when the scale condition should be applied.

Scale condition based on schedule

Scale differently on specific dates

In addition to scale based on CPU, you can set your scale differently for specific dates.

  1. Click Add a scale condition.
  2. Setting the scale mode and the rules is the same as the default condition.
  3. Select Specify start/end dates for the schedule.
  4. Select the start/end dates and the start/end time for when the scale condition should be applied.

Scale condition based on dates

View the scale history of your resource

Whenever your resource is scaled up or down, an event is logged in the activity log. You can view the scale history of your resource for the past 24 hours by switching to the Run history tab.

Run history

If you want to view the complete scale history (for up to 90 days), select Click here to see more details. The activity log opens, with Autoscale pre-selected for your resource and category.

View the scale definition of your resource

Autoscale is an Azure Resource Manager resource. You can view the scale definition in JSON by switching to the JSON tab.

Scale definition

You can make changes in JSON directly, if required. These changes will be reflected after you save them.

Cool-down period effects

Autoscale uses a cool-down period to prevent "flapping", which is the rapid, repetitive up and down scaling of instances. For more information, see Autoscale evaluation steps. Other valuable information on flapping and understanding how to monitor the autoscale engine can be found in Autoscale Best Practices and Troubleshooting autoscale respectively.

Route traffic to healthy instances (App Service)

When your Azure web app is scaled out to multiple instances, App Service can perform health checks on your instances to route traffic to the healthy instances. To learn more, see this article on App Service Health check.

Moving Autoscale to a different region

This section describes how to move Azure autoscale to another region under the same Subscription, and Resource Group. You can use REST API to move autoscale settings.


  1. Ensure that the subscription and Resource Group are available and the details in both the source and destination regions are identical.
  2. Ensure that Azure autoscale is available in the Azure region you want to move to.


Use REST API to create an autoscale setting in the new environment. The autoscale setting created in the destination region will be a copy of the autoscale setting in the source region.

Diagnostic settings that were created in association with the autoscale setting in the source region cannot be moved. You will need to recreate diagnostic settings in the destination region, after the creation of autosale settings is completed.

Learn more about moving resources across Azure regions

To learn more about moving resources between regions and disaster recovery in Azure, refer to Move resources to a new resource group or subscription

Next steps