Skip to content

Commit 0f23f56

Browse files
authored
Fix link
1 parent 460295d commit 0f23f56

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -237,7 +237,7 @@ When you deploy a scale set into one or more availability zones, you have the fo
237237
238238
- **Static fixed spreading (platformFaultDomainCount = 5)**. With static fixed spreading, the scale set spreads your VMs exactly across five fault domains per zone. If the scale set can't find five distinct fault domains per zone to satisfy the allocation request, the request fails.
239239

240-
- **Spreading aligned with managed disks fault domains (platformFaultDomainCount = 2 or 3)** You can consider aligning the number of scale set fault domains with the number of managed disks fault domains. This alignment can help prevent loss of quorum if an entire managed disks fault domain goes down. The fault domain count can be set to less than or equal to the number of managed disks fault domains available in each of the regions. To learn more, see [Best practices for achieving high availability with Azure virtual machines and managed disks](../virtual-machines/disks-high-availability.md).
240+
- **Spreading aligned with managed disks fault domains (platformFaultDomainCount = 2 or 3)** You can consider aligning the number of scale set fault domains with the number of managed disks fault domains. This alignment can help prevent loss of quorum if an entire managed disks fault domain goes down. The fault domain count can be set to less than or equal to the number of managed disks fault domains available in each of the regions. To learn more, see [Best practices for achieving high availability with Azure virtual machines and managed disks](/azure/virtual-machines/disks-high-availability).
241241

242242
#### Zone balancing
243243

0 commit comments

Comments
 (0)