Merge pull request #2484 from tferdou1/patch-36

Delete a VMSS for capacity reservation

Author: prmerger-automator[bot]

articles/virtual-machines/capacity-reservation-remove-virtual-machine-scale-set.md

@@ -19,10 +19,11 @@ This article walks you through removing a virtual machine scale set association
 
 Because both the virtual machine (VM) and the underlying capacity reservation logically occupy capacity, Azure imposes some constraints on this process to avoid ambiguous allocation states and unexpected errors.
 
-There are two ways to change an association:
+There are three ways to change an association:
 
 - Deallocate the virtual machine scale set, change the capacity reservation group property at the scale set level, and then update the underlying VMs.
 - Update the reserved quantity to zero and then change the capacity reservation group property.
+- Delete the virtual machine scale set
 
 ## Deallocate the virtual machine scale set
 
@@ -241,6 +242,11 @@ To learn more, see the Azure PowerShell commands [New-AzCapacityReservation](/po
 --- 
 <!-- The three dashes above show that your section of tabbed content is complete. Don't remove them :) -->
 
+
+## Delete the virtual machine scale set
+
+Deletion process of a scale set remove its association from a capacity reservation. The delete request must complete before Azure removes it from the capacity reservation. Some latency can occur between the delete request and the corresponding change in capacity reservation allocation state. See [Delete a VM](/azure/virtual-machines/delete?tabs=portal2%2Ccli3%2Cportal4%2Cportal5) for more information. Use [Capacity Reservation Instance View](/azure/virtual-machines/capacity-reservation-associate-vm?tabs=api1%2Capi2%2Capi3#view-vm-allocation-with-the-instance-view) to check the allocation status as needed.
+
 ## Upgrade policies
 
 - **Automatic upgrade**: In this mode, the scale set VM instances are automatically dissociated from the capacity reservation group without any further action from you.