Merge pull request #120165 from NehaMicroSoft/patch-1

Update virtual-machine-scale-sets-scale-in-policy.md

Author: Jak-MS

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-scale-in-policy.md

@@ -26,8 +26,13 @@ The scale-in policy feature provides users a way to configure the order in which
 ### Default scale-in policy
 
 #### Flexible orchestration 
-With this policy, virtual machines are scaled-in after balancing across availability zones (if the scale set is in zonal configuration), and the oldest virtual machine as per `createdTime` is scaled-in first. 
-Balancing across fault domain isn't available in Default policy with flexible orchestration mode. 
+By default, Virtual Machine Scale Set applies this policy to determine which instance(s) will be scaled in. With the *Default* policy, VMs are selected for scale-in in the following order:
+
+1. Balance virtual machines across availability zones (if the scale set is deployed in zonal configuration)
+2. Balance virtual machines across fault domains (best effort)
+3. Delete virtual machine with the highest instance ID
+
+Users don't need to specify a scale-in policy if they just want the default ordering to be followed.
 
 #### Uniform orchestration 
 By default, Virtual Machine Scale Set applies this policy to determine which instance(s) will be scaled in. With the *Default* policy, VMs are selected for scale-in in the following order: