edit pass: four-autoscale-articles

paulth1 · paulth1 · commit d7197a5bd187 · 2022-07-27T14:03:15.000-07:00
diff --git a/articles/azure-monitor/autoscale/autoscale-common-metrics.md b/articles/azure-monitor/autoscale/autoscale-common-metrics.md
@@ -13,32 +13,32 @@ ms.reviewer: riroloff
 
 [!INCLUDE [updated-for-az](../../../includes/updated-for-az.md)]
 
-Azure Monitor autoscaling allows you to scale the number of running instances up or down, based on telemetry data (metrics). This article describes common metrics that you might want to use. In the Azure portal, you can choose the metric of the resource to scale by. You can also choose any metric from a different resource to scale by.
+Azure Monitor autoscaling allows you to scale the number of running instances up or down, based on telemetry data, also known as metrics. This article describes common metrics that you might want to use. In the Azure portal, you can choose the metric of the resource to scale by. You can also choose any metric from a different resource to scale by.
 
-Azure Monitor autoscale applies only to [Azure Virtual Machine Scale Sets](https://azure.microsoft.com/services/virtual-machine-scale-sets/), [Azure Cloud Services](https://azure.microsoft.com/services/cloud-services/), [Azure App Service - Web Apps](https://azure.microsoft.com/services/app-service/web/), and [Azure API Management services](../../api-management/api-management-key-concepts.md). Other Azure services use different scaling methods.
+Azure Monitor autoscale applies only to [Azure Virtual Machine Scale Sets](https://azure.microsoft.com/services/virtual-machine-scale-sets/), [Azure Cloud Services](https://azure.microsoft.com/services/cloud-services/), [Azure App Service - Web Apps](https://azure.microsoft.com/services/app-service/web/), and [Azure API Management](../../api-management/api-management-key-concepts.md). Other Azure services use different scaling methods.
 
 ## Compute metrics for Resource Manager-based VMs
 
-By default, Azure Resource Manager-based virtual machines and Virtual Machine Scale Sets emit basic (host-level) metrics. In addition, when you configure diagnostics data collection for an Azure VM and Virtual Machine Scale Sets, the Azure diagnostic extension also emits guest-OS performance counters (commonly known as "guest-OS metrics"). You use all these metrics in autoscale rules.
+By default, Azure Resource Manager-based virtual machines and virtual machine scale sets emit basic (host-level) metrics. In addition, when you configure diagnostics data collection for an Azure VM and virtual machine scale sets, the Azure Diagnostics extension also emits guest-OS performance counters. These counters are commonly known as "guest-OS metrics." You use all these metrics in autoscale rules.
 
 You can use the `Get MetricDefinitions` API/PoSH/CLI to view the metrics available for your Virtual Machine Scale Sets resource.
 
-If you're using virtual machine scale sets and you don't see a particular metric listed, it's likely *disabled* in your diagnostics extension.
+If you're using virtual machine scale sets and you don't see a particular metric listed, it's likely *disabled* in your Diagnostics extension.
 
 If a particular metric isn't being sampled or transferred at the frequency you want, you can update the diagnostics configuration.
 
 If either preceding case is true, see [Use PowerShell to enable Azure Diagnostics in a virtual machine running Windows](../../virtual-machines/extensions/diagnostics-windows.md) to configure and update your Azure VM Diagnostics extension to enable the metric. The article also includes a sample diagnostics configuration file.
 
 ### Host metrics for Resource Manager-based Windows and Linux VMs
 
-The following host-level metrics are emitted by default for Azure VM and Virtual Machine Scale Sets in both Windows and Linux instances. These metrics describe your Azure VM, but are collected from the Azure VM host rather than via agent installed on the guest VM. You may use these metrics in autoscaling rules.
+The following host-level metrics are emitted by default for Azure VM and virtual machine scale sets in both Windows and Linux instances. These metrics describe your Azure VM but are collected from the Azure VM host rather than via agent installed on the guest VM. You can use these metrics in autoscaling rules.
 
 - [Host metrics for Resource Manager-based Windows and Linux VMs](../essentials/metrics-supported.md#microsoftcomputevirtualmachines)
-- [Host metrics for Resource Manager-based Windows and Linux Virtual Machine Scale Sets](../essentials/metrics-supported.md#microsoftcomputevirtualmachinescalesets)
+- [Host metrics for Resource Manager-based Windows and Linux virtual machine scale sets](../essentials/metrics-supported.md#microsoftcomputevirtualmachinescalesets)
 
 ### Guest OS metrics for Resource Manager-based Windows VMs
 
-When you create a VM in Azure, diagnostics is enabled by using the Diagnostics extension. The diagnostics extension emits a set of metrics taken from inside of the VM. This means you can autoscale off of metrics that aren't emitted by default.
+When you create a VM in Azure, diagnostics is enabled by using the Diagnostics extension. The Diagnostics extension emits a set of metrics taken from inside of the VM. This means you can autoscale off of metrics that aren't emitted by default.
 
 You can generate a list of the metrics by using the following command in PowerShell.
 
@@ -80,7 +80,7 @@ You can create an alert for the following metrics:
 
 ### Guest OS metrics Linux VMs
 
-When you create a VM in Azure, diagnostics is enabled by default by using Diagnostics extension.
+When you create a VM in Azure, diagnostics is enabled by default by using the Diagnostics extension.
 
 You can generate a list of the metrics by using the following command in PowerShell.
 
@@ -137,7 +137,7 @@ You can also perform autoscale based on common web server metrics such as the HT
 
 ### Web Apps metrics
 
-You can generate a list of the Web Apps metrics by using the following command in PowerShell.
+You can generate a list of the Web Apps metrics by using the following command in PowerShell:
 
 ```
 Get-AzMetricDefinition -ResourceId <resource_id> | Format-Table -Property Name,Unit
@@ -156,9 +156,9 @@ You can alert on or scale by these metrics.
 
 ## Commonly used Storage metrics
 
-You can scale by Storage queue length, which is the number of messages in the Storage queue. Storage queue length is a special metric and the threshold is the number of messages per instance. For example, if there are two instances and if the threshold is set to 100, scaling occurs when the total number of messages in the queue is 200. That amount can be 100 messages per instance, 120 and 80, or any other combination that adds up to 200 or more.
+You can scale by Azure Storage queue length, which is the number of messages in the Storage queue. Storage queue length is a special metric, and the threshold is the number of messages per instance. For example, if there are two instances and if the threshold is set to 100, scaling occurs when the total number of messages in the queue is 200. That amount can be 100 messages per instance, 120 plus 80, or any other combination that adds up to 200 or more.
 
-Configure this setting in the Azure portal in the **Settings** pane. For virtual machine scale sets, you can update the Autoscale setting in the Resource Manager template to use *metricName* as *ApproximateMessageCount* and pass the ID of the storage queue as *metricResourceUri*.
+Configure this setting in the Azure portal in the **Settings** pane. For virtual machine scale sets, you can update the autoscale setting in the Resource Manager template to use `metricName` as `ApproximateMessageCount` and pass the ID of the storage queue as `metricResourceUri`.
 
 For example, with a Classic Storage account, the autoscale setting `metricTrigger` would include:
 
@@ -178,9 +178,9 @@ For a (non-classic) Storage account, the `metricTrigger` setting would include:
 
 ## Commonly used Service Bus metrics
 
-You can scale by Service Bus queue length, which is the number of messages in the Service Bus queue. Service Bus queue length is a special metric, and the threshold is the number of messages per instance. For example, if there are two instances and if the threshold is set to 100, scaling occurs when the total number of messages in the queue is 200. That amount can be 100 messages per instance, 120 plus 80, or any other combination that adds up to 200 or more.
+You can scale by Azure Service Bus queue length, which is the number of messages in the Service Bus queue. Service Bus queue length is a special metric, and the threshold is the number of messages per instance. For example, if there are two instances and if the threshold is set to 100, scaling occurs when the total number of messages in the queue is 200. That amount can be 100 messages per instance, 120 plus 80, or any other combination that adds up to 200 or more.
 
-For Virtual Machine Scale Sets, you can update the Autoscale setting in the Resource Manager template to use *metricName* as *ApproximateMessageCount* and pass the ID of the storage queue as *metricResourceUri*.
+For virtual machine scale sets, you can update the autoscale setting in the Resource Manager template to use `metricName` as `ApproximateMessageCount` and pass the ID of the storage queue as `metricResourceUri`.
 
 ```
 "metricName": "ApproximateMessageCount",
@@ -189,4 +189,4 @@ For Virtual Machine Scale Sets, you can update the Autoscale setting in the Reso
 ```
 
 > [!NOTE]
-> For Service Bus, the resource group concept doesn't exist but Azure Resource Manager creates a default resource group per region. The resource group is usually in the 'Default-ServiceBus-[region]' format, for example, 'Default-ServiceBus-EastUS', 'Default-ServiceBus-WestUS', and 'Default-ServiceBus-AustraliaEast'.
+> For Service Bus, the resource group concept doesn't exist, but Azure Resource Manager creates a default resource group per region. The resource group is usually in the Default-ServiceBus-[region] format. Examples are Default-ServiceBus-EastUS, Default-ServiceBus-WestUS, and Default-ServiceBus-AustraliaEast.
diff --git a/articles/azure-monitor/autoscale/autoscale-custom-metric.md b/articles/azure-monitor/autoscale/autoscale-custom-metric.md
@@ -24,7 +24,7 @@ Azure Monitor autoscale applies to:
 + [Azure Cloud Services](https://azure.microsoft.com/services/cloud-services/)
 + [Azure App Service - Web Apps](https://azure.microsoft.com/services/app-service/web/)
 + [Azure Data Explorer cluster](https://azure.microsoft.com/services/data-explorer/) 
-+ Integration service environment and [Azure API Management services](../../api-management/api-management-key-concepts.md)
++ Integration service environment and [Azure API Management](../../api-management/api-management-key-concepts.md)
 
 ## Prerequisite
 
diff --git a/articles/azure-monitor/autoscale/autoscale-get-started.md b/articles/azure-monitor/autoscale/autoscale-get-started.md
@@ -6,36 +6,36 @@ ms.date: 04/05/2022
 ms.subservice: autoscale
 ms.reviewer: riroloff
 ---
-# Get started with Autoscale in Azure
+# Get started with autoscale in Azure
 
-This article describes how to set up your Autoscale settings for your resource in the Azure portal.
+This article describes how to set up your autoscale settings for your resource in the Azure portal.
 
-Azure Monitor autoscale applies only to [Azure Virtual Machine Scale Sets](https://azure.microsoft.com/services/virtual-machine-scale-sets/), [Cloud Services](https://azure.microsoft.com/services/cloud-services/), [Azure App Service - Web Apps](https://azure.microsoft.com/services/app-service/web/), and [API Management services](../../api-management/api-management-key-concepts.md).
+Azure Monitor autoscale applies only to [Azure Virtual Machine Scale Sets](https://azure.microsoft.com/services/virtual-machine-scale-sets/), [Azure Cloud Services](https://azure.microsoft.com/services/cloud-services/), [Azure App Service - Web Apps](https://azure.microsoft.com/services/app-service/web/), and [Azure API Management](../../api-management/api-management-key-concepts.md).
 
-## Discover the Autoscale settings in your subscription
+## Discover the autoscale settings in your subscription
 
 > [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4u7ts]
 
-You can discover all the resources for which Autoscale is applicable in Azure Monitor. Use the following steps for a step-by-step walkthrough:
+To discover all the resources for which autoscale is applicable in Azure Monitor, follow these steps.
 
 1. Open the [Azure portal.][1]
 1. Select the Azure Monitor icon at the top of the page.
 
    [![Screenshot that shows how to open Azure Monitor.](./media/autoscale-get-started/click-on-monitor-1.png)](./media/autoscale-get-started/click-on-monitor-1.png#lightbox)
 
-1. Select **Autoscale** to view all the resources for which Autoscale is applicable, along with their current Autoscale status.
+1. Select **Autoscale** to view all the resources for which autoscale is applicable, along with their current autoscale status.
 
    [![Screenshot that shows autoscale in Azure Monitor.](./media/autoscale-get-started/click-on-autoscale-2.png)](./media/autoscale-get-started/click-on-autoscale-2.png#lightbox)
   
 1. 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 that shows viewing resource status.](./media/autoscale-get-started/view-all-resources-3.png)](./media/autoscale-get-started/view-all-resources-3.png#lightbox)
 
-   For each resource, you'll find the current instance count and the Autoscale status. The Autoscale status can be:
+   For each resource, you'll find the current instance count and the autoscale status. The autoscale status can be:
 
-   - **Not configured**: You haven't enabled Autoscale yet for this resource.
-   - **Enabled**: You've enabled Autoscale for this resource.
-   - **Disabled**: You've disabled Autoscale for this resource.
+   - **Not configured**: You haven't enabled autoscale yet for this resource.
+   - **Enabled**: You've enabled autoscale for this resource.
+   - **Disabled**: You've disabled autoscale for this resource.
 
    You can also reach the scaling page by selecting **All Resources** on the home page and filter to the resource you're interested in scaling.
 
@@ -45,11 +45,11 @@ You can discover all the resources for which Autoscale is applicable in Azure Mo
 
     [![Screenshot that shows the scaling button.](./media/autoscale-get-started/scaling-page.png)](./media/autoscale-get-started/scaling-page.png#lightbox)
 
-## Create your first Autoscale setting
+## Create your first autoscale setting
 
-Let's now go through a simple step-by-step walkthrough to create your first Autoscale setting.
+Let's now go through a step-by-step walkthrough to create your first autoscale setting.
 
-1. Open the **Autoscale** pane 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.][5])
+1. Open the **Autoscale** pane 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.][5]
 1. The current instance count is 1. Select **Custom autoscale**.
 
    [![Screenshot that shows scale setting for a new web app.](./media/autoscale-get-started/manual-scale-04.png)](./media/autoscale-get-started/manual-scale-04.png#lightbox)
@@ -78,6 +78,8 @@ Congratulations! You've now successfully created your first scale setting to aut
 
 ## Other considerations
 
+The following sections introduce other considerations for autoscaling.
+
 ### Scale based on a schedule
 
 You can set your scale differently for specific days of the week.
@@ -106,7 +108,7 @@ Whenever your resource is scaled up or down, an event is logged in the activity
 
 ![Screenshot that shows a Run history screen.][12]
 
-To view the complete scale history for up to 90 days, select **Click here to see more details**. The activity log opens, with Autoscale preselected for your resource and category.
+To view the complete scale history for up to 90 days, select **Click here to see more details**. The activity log opens, with autoscale preselected for your resource and category.
 
 ### View the scale definition of your resource
 
@@ -124,16 +126,16 @@ Autoscale uses a cool-down period to prevent "flapping," which is the rapid, rep
 
 <a id="health-check-path"></a>
 
-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 [Monitor App Service instances using Health check.](../../app-service/monitor-instances-health-check.md).
+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 [Monitor App Service instances using Health check](../../app-service/monitor-instances-health-check.md).
 
-## Move Autoscale to a different region
+## Move 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.
 
 ### Prerequisites
 
-1. Ensure that the subscription and resource group are available and the details in both the source and destination regions are identical.
-1. Ensure that Azure autoscale is available in the [Azure region you want to move to](https://azure.microsoft.com/global-infrastructure/services/?products=monitor&regions=all).
+- Ensure that the subscription and resource group are available and the details in both the source and destination regions are identical.
+- Ensure that Azure autoscale is available in the [Azure region you want to move to](https://azure.microsoft.com/global-infrastructure/services/?products=monitor&regions=all).
 
 ### Move
 
@@ -147,8 +149,8 @@ To learn more about moving resources between regions and disaster recovery in Az
 
 ## Next steps
 
-- [Create an Activity Log Alert to monitor all Autoscale engine operations on your subscription](https://github.com/Azure/azure-quickstart-templates/tree/master/demos/monitor-autoscale-alert)
-- [Create an Activity Log Alert to monitor all failed Autoscale scale-in/scale-out operations on your subscription](https://github.com/Azure/azure-quickstart-templates/tree/master/demos/monitor-autoscale-failed-alert)
+- [Create an activity log alert to monitor all autoscale engine operations on your subscription](https://github.com/Azure/azure-quickstart-templates/tree/master/demos/monitor-autoscale-alert)
+- [Create an activity log alert to monitor all failed autoscale scale-in/scale-out operations on your subscription](https://github.com/Azure/azure-quickstart-templates/tree/master/demos/monitor-autoscale-failed-alert)
 
 
 <!--Reference-->
diff --git a/articles/azure-monitor/autoscale/autoscale-predictive.md b/articles/azure-monitor/autoscale/autoscale-predictive.md
