Skip to content

Commit 14320b2

Browse files
committed
Update standby-pools-overview.md
1 parent 5741b80 commit 14320b2

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/virtual-machine-scale-sets/standby-pools-overview.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,9 @@ When your scale set requires more instances, rather than creating new instances
4141

4242
When your scale set scales back down, the instances are deleted from your scale set based on the [scale-in policy](virtual-machine-scale-sets-scale-in-policy.md) and your standby pool will refill to meet the max ready capacity configured. If at any point in time your scale set needs to scale beyond the number of instances you have in your standby pool, the scale set defaults to standard scale-out methods and creates new instances directly in the Scale Set
4343

44-
Standby pools will only give out virtual machines from the pool that match the desired power state configured. For example, if your desired power state is set as deallocated, the standby pool will only give the Virtual Machine Scale Set instances matching that current power state. If virtual machines are in a creating, failed or any other state than the expected state, the scale set defaults to new virtual machine creation instead
44+
Standby pools will only give out virtual machines from the pool that match the desired power state configured. For example, if your desired power state is set as deallocated, the standby pool will only give the Virtual Machine Scale Set instances matching that current power state. If virtual machines are in a creating, failed or any other state than the expected state, the scale set defaults to new virtual machine creation instead.
45+
46+
When using a standby pool with a Virtual Machine Scale Set spread across multiple availability zones, the instances in the pool will also be spread across zones. When a scale out is triggered in one of the zones, a virtual machine in the pool in that same zone will be used. If a virtual machine is needed in a zone where you no longer have any pooled virtual machines left, the scale set will create a new virtual machine directly in the scale set.
4547

4648
## Virtual machine states
4749

@@ -70,7 +72,7 @@ There's no direct cost associated with using standby pools. Users are charged ba
7072
- Creating or attaching a standby pool to a Virtual Machine Scale Set with a fault domain greater than 1.
7173
- Creating or attaching a standby pool to a Virtual Machine Scale Set in a different region.
7274
- Creating or attaching a standby pool to a Virtual Machine Scale Set in a different subscription.
73-
- Creating or attaching a standby pool to a Virtual Machine Scale Set that already has a standby pool attached.
75+
- Creating or attaching a standby pool to a Virtual Machine Scale Set that already has a standby pool.
7476
- Creating or attaching a standby pool to a Virtual Machine Scale Set using Uniform Orchestration.
7577

7678
## Next steps

0 commit comments

Comments
 (0)