Merge pull request #113309 from mayanknayar/master

Updating VMSS scale-in FAQ

Author: PRMerger14

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

@@ -40,11 +40,13 @@ Create and capture a VM image, then use that as the source for your scale set. F
 
 ### If I reduce my scale set capacity from 20 to 15, which VMs are removed?
 
-Virtual machines are removed from the scale set evenly across update domains and fault domains to maximize availability. VMs with the highest IDs are removed first.
+By default, virtual machines are removed from the scale set evenly across availability zones (if the scale set is deployed in zonal configuration) and fault domains to maximize availability. VMs with the highest IDs are removed first.
+
+You can change the order of virtual machine removal by specifying a [scale-in policy](virtual-machine-scale-sets-scale-in-policy.md) for the scale set.
 
 ### What if I then increase the capacity from 15 to 18?
 
-If you increase capacity to 18, then 3 new VMs are created. Each time, the VM instance ID is incremented from the previous highest value (for example, 20, 21, 22). VMs are balanced across fault domains and update domains.
+If you increase capacity to 18, then 3 new VMs are created. Each time, the VM instance ID is incremented from the previous highest value (for example, 20, 21, 22). VMs are balanced across fault domains.
 
 ### When I'm using multiple extensions in a scale set, can I enforce an execution sequence?
 
@@ -330,13 +332,13 @@ For more information, see [the Microsoft Trust Center](https://www.microsoft.com
 
 Yes. You can see some example MSI templates in Azure Quickstart templates for [Linux](https://github.com/Azure/azure-quickstart-templates/tree/master/201-vmss-msi) and [Windows](https://github.com/Azure/azure-quickstart-templates/tree/master/201-vmss-msi).
 
-## Deleting 
+## Deleting
 
 ### Will the locks I set in place on virtual machine scale set instances be respected when deleting instances?
 
-In the Azure Portal, you have the ability to delete an individual instance or bulk delete by selecting multiple instances. If you attempt to delete a single instance that has a lock in place, the lock is respected and you will not be able to delete the instance. However, if you bulk select multiple instances and any of those instances have a lock in place, the lock(s) will not be respected and all of the selected instances will be deleted. 
- 
-In Azure CLI, you only have the ability to delete an individual instance. If you attempt to delete a single instance that has a lock in place, the lock is respected and you will not be able to delete that instance. 
+In the Azure Portal, you have the ability to delete an individual instance or bulk delete by selecting multiple instances. If you attempt to delete a single instance that has a lock in place, the lock is respected and you will not be able to delete the instance. However, if you bulk select multiple instances and any of those instances have a lock in place, the lock(s) will not be respected and all of the selected instances will be deleted.
+
+In Azure CLI, you only have the ability to delete an individual instance. If you attempt to delete a single instance that has a lock in place, the lock is respected and you will not be able to delete that instance.
 
 ## Extensions