Skip to content

Commit 118f204

Browse files
authored
Update standby-pools-faq.md
1 parent e0011de commit 118f204

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

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

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,12 @@ Standby pools is a powerful feature for accelerating your time to scale-out and
2828
### Can I use standby pools on Virtual Machine Scale Sets with Uniform Orchestration?
2929
Standby pools is only supported on Virtual Machine Scale Sets with Flexible Orchestration.
3030

31+
### Does using a standby pool guarantee capacity?
32+
Using a standby pool with deallocated instances does not guarantee capacity. When starting the deallocated VM, there needs to be enough capacity in the region your instances are deployed in to start the machines. If using running VMs in your pool, those VMs are already allocated and consuming compute capacity. When the VM moves from the standby pool to the Virtual Machine Scale Set, it does not release the compute resources and does not require any additional allocation of resoures.
33+
34+
### How long can my standby pool name be?
35+
A standby pool can be anywhere between 3 and 24 characters. For more information, see [Resource naming restrictions for Azure resources](..//azure-resource-manager/management/resource-name-rules.md)
36+
3137
### Can I use standby pools for Virtual Machine Scale Sets if I'm already using Azure autoscale?
3238
Attaching a standby pool to a Virtual Machine Scale Set with Azure autoscale enabled isn't supported.
3339

0 commit comments

Comments
 (0)