Merge pull request #113375 from BhawanaRaj-21/BhawanaRaj-21-scale-in-policy-1-2

Bhawana raj 21 scale in policy 1 2

Author: Court72

articles/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes.md

@@ -160,7 +160,7 @@ The following table compares the Flexible orchestration mode, Uniform orchestrat
 | Monitor Application Health | Application health extension | Application health extension or Azure load balancer probe | Application health extension |
 | Instance Repair (Virtual Machine Scale Set) | Yes, read [Instance Repair documentation](../virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs.md) | Yes, read [Instance Repair documentation](../virtual-machine-scale-sets/virtual-machine-scale-sets-automatic-instance-repairs.md) | N/A |
 | Instance Protection | No, use [Azure resource lock](../azure-resource-manager/management/lock-resources.md) | Yes | No |
-| Scale In Policy | No | Yes | No |
+| Scale In Policy | Yes | Yes | No |
 | VMSS Get Instance View | No | Yes | N/A |
 | VM Batch Operations (Start all, Stop all, delete subset, etc.) | Yes | Yes | No |
 
@@ -212,7 +212,6 @@ The following Virtual Machine Scale Set parameters aren't currently supported wi
 - Application health via SLB health probe - use Application Health Extension on instances
 - Virtual Machine Scale Set upgrade policy - must be null or empty
 - Unmanaged disks
-- Virtual Machine Scale Set Scale in Policy
 - Virtual Machine Scale Set Instance Protection
 - Basic Load Balancer
 - Port Forwarding via Standard Load Balancer NAT Pool - you can configure NAT rules

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

@@ -23,11 +23,13 @@ The scale-in policy feature provides users a way to configure the order in which
 2. NewestVM
 3. OldestVM
 
-> [!IMPORTANT]
-> Flexible orchestration for Virtual Machine Scale Sets does not currently support scale-in policy.
-
 ### 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. 
+Note that balancing across fault domain is not available in Default policy with flexible orchestration mode. 
+
+#### 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:
 
 1. Balance virtual machines across availability zones (if the scale set is deployed in zonal configuration)