Merge pull request #229137 from mimckitt/patch-83

Update availability-set-overview.md

Author: prmerger-automator[bot]

articles/virtual-machines/availability-set-overview.md

@@ -37,6 +37,13 @@ Only VMs with managed disks can be created in a managed availability set. The nu
 az vm list-skus --resource-type availabilitySets --query '[?name==`Aligned`].{Location:locationInfo[0].location, MaximumFaultDomainCount:capabilities[0].value}' -o Table
 ```
 
+Under certain circumstances, two VMs in the same availability set might share a fault domain. You can confirm a shared fault domain by going to your availability set and checking the Fault Domain column. A shared fault domain might be caused by the completing following sequence when you deployed the VMs:
+1. Deploy the first VM.
+2. Stop/deallocate the first VM.
+3. Deploy the second VM.
+
+Under these circumstances, the OS disk of the second VM might be created on the same fault domain as the first VM, so the two VMs will be on same fault domain. To avoid this issue, we recommend that you don't stop/deallocate VMs between deployments.
+
 :::image type="content" source="./media/virtual-machines-common-manage-availability/md-fd-updated.png" alt-text="Diagram showing how the fault domains for disks and VMs are aligned.":::
 
 ## Next steps