Merge pull request #42050 from iainfoulds/vmssautoscalebehavior

[VMSS] Add additional autoscale details

Author: PRMerger18

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-faq.md

@@ -25,9 +25,10 @@ ms.custom: na
 Get answers to frequently asked questions about virtual machine scale sets in Azure.
 
 ## Top frequently asked questions for scale sets
+
 **Q.** How many VMs can I have in a scale set?
 
-**A.** A scale set can have 0 to 1,000 VMs based on platform images, or 0 to 300 VMs based on custom images. 
+**A.** A scale set can have 0 to 1,000 VMs based on platform images, or 0 to 300 VMs based on custom images.
 
 **Q.** Are data disks supported within scale sets?
 
@@ -45,7 +46,7 @@ Get answers to frequently asked questions about virtual machine scale sets in Az
 
 **Q.** How do I create a scale set by using a custom image?
 
-**A.** Create a managed disk based on your custom image VHD and reference it in your scale set template. [Here's an example](https://github.com/chagarw/MDPP/tree/master/101-vmss-custom-os).
+**A.** Create and capture a VM image, then use that as the source for your scale set. For a tutorial on how to create and use a custom VM image, you can use the [Azure CLI 2.0](tutorial-use-custom-image-cli.md) or [Azure PowerShell](tutorial-use-custom-image-powershell.md)
 
 **Q.** If I reduce my scale set capacity from 20 to 15, which VMs are removed?
 
@@ -117,16 +118,20 @@ The sample uses the host-level CPU metric and a message count metric.
 
 You can create alerts on metrics for virtual machine scale sets via PowerShell or Azure CLI. For more information, see [Azure Monitor PowerShell quickstart samples](https://azure.microsoft.com/documentation/articles/insights-powershell-samples/#create-alert-rules) and [Azure Monitor cross-platform CLI quickstart samples](https://azure.microsoft.com/documentation/articles/insights-cli-samples/#work-with-alerts).
 
-The TargetResourceId of the virtual machine scale set looks like this: 
+The TargetResourceId of the virtual machine scale set looks like this:
 
 /subscriptions/yoursubscriptionid/resourceGroups/yourresourcegroup/providers/Microsoft.Compute/virtualMachineScaleSets/yourvmssname
 
 You can choose any VM performance counter as the metric to set an alert for. For more information, see [Guest OS metrics for Resource Manager-based Windows VMs](https://azure.microsoft.com/documentation/articles/insights-autoscale-common-metrics/#guest-os-metrics-resource-manager-based-windows-vms) and [Guest OS metrics for Linux VMs](https://azure.microsoft.com/documentation/articles/insights-autoscale-common-metrics/#guest-os-metrics-linux-vms) in the [Azure Monitor autoscaling common metrics](https://azure.microsoft.com/documentation/articles/insights-autoscale-common-metrics/) article.
 
 ### How do I set up autoscale on a virtual machine scale set by using PowerShell?
 
-To set up autoscale on a virtual machine scale set by using PowerShell, see the blog post [How to add autoscale to an Azure virtual machine scale set](https://msftstack.wordpress.com/2017/03/05/how-to-add-autoscale-to-an-azure-vm-scale-set/).
+To set up autoscale on a virtual machine scale set by using PowerShell, see [automatically scale a virtual machine scale set](tutorial-autoscale-powershell.md). You can also configure autoscale with the [Azure CLI 2.0](tutorial-autoscale-cli.md) and [Azure templates](tutorial-autoscale-template.md)
+
+
+### If I have stopped (deallocated) a VM, is that VM started as part of an autoscale operation?
 
+No. If autoscale rules require additional VM instances as part of a scale set, a new VM instance is created. VM instances that are stopped (deallocated) are not started as part of an autoscale event. However, those stopped (deallocated) VMs may be deleted as part of an autoscale event that scales in the number of instances, the same way that any VM instance may be deleted based on the order of VM instance ID.