Edit

Share via

Standby pools FAQ (Preview)

  • Article

Important

Standby pools for Virtual Machine Scale Sets are currently in preview. Previews are made available to you on the condition that you agree to the supplemental terms of use. Some aspects of this feature may change prior to general availability (GA).

Get answers to frequently asked questions about standby pools for Virtual Machine Scale Sets in Azure.

What are standby pools for Virtual Machine Scale Sets?

Azure standby pools for Virtual Machine Scale Sets with Flexible Orchestration enables faster scaling out of resources by creating a pool of pre-provisioned virtual machines ready to service your workload.

When should I use standby pools for Virtual Machine Scale Sets?

Using a standby pool with your Virtual Machine Scale Set can help improve scale-out performance by completing various pre and post provisioning steps in the pool before the instances are placed into the scale set.

What are the benefits of using Azure standby pools for Virtual Machine Scale Sets?

Standby pools is a powerful feature for accelerating your time to scale out and reducing the management needed for provisioning virtual machine resources and getting them ready to service your workload. If your applications are latency sensitive or have long initialization steps, standby pools can help with reducing that time and managing the steps to make your virtual machines ready on your behalf.

Can I use standby pools on Virtual Machine Scale Sets with Uniform Orchestration?

Standby pools are only supported on Virtual Machine Scale Sets with Flexible Orchestration.

Does using a standby pool guarantee capacity?

Using a standby pool with deallocated instances doesn't guarantee capacity. When starting the deallocated virtual machine, there needs to be enough capacity in the region your instances are deployed in to start the machines. If using running virtual machines in your pool, those virtual machines are already allocated and consuming compute capacity. When the virtual machine moves from the standby pool to the Virtual Machine Scale Set, it doesn't release the compute resources and doesn't require any additional allocation of resources.

How long can my standby pool name be?

A standby pool can be anywhere between 3 and 24 characters. For more information, see Resource naming restrictions for Azure resources

Can I use standby pools for Virtual Machine Scale Sets if I'm already using Azure autoscale?

Attaching a standby pool to a Virtual Machine Scale Set with Azure autoscale enabled isn't supported.

How many virtual machines can my standby pool for Virtual Machine Scale Sets have?

The maximum number of virtual machines between a scale set and a standby pool is 1,000.

Can my standby pool span multiple Virtual Machine Scale Sets?

A standby pool resource can't span multiple scale sets. Each scale set has its own standby pool attached to it. A standby pool inherits the unique properties of the scale set such as networking, virtual machine profile, extensions, and more.

How is the configuration of my virtual machines in the standby pool for Virtual Machine Scale Sets determined?

Virtual machines in the standby pool inherit the same virtual machine profile as the virtual machines in the scale set. Some examples are:

  • Virtual machine size
  • Storage Profile
  • Image Reference
  • OS Profile
  • Network Profile
  • Extensions Profile
  • Zones

Can I change the size of my standby pool without needing to recreate it?

Yes. To change the size of your standby pool update the max ready capacity setting.

Can a standby pool resource be moved?

No. Standby Pools doesn't currently support that capability. If you need to move a standby pool, you can consider deleting it recreating it in another location.

I created a standby pool and I noticed that some virtual machines are coming up in a failed state.

Ensure you have enough quota to complete the standby pool creation. Insufficient quota results in the platform attempting to create the virtual machines in the standby pool but unable to successfully complete the create operation. Check for multiple types of quotas such as Cores, Network Interfaces, IP Addresses, etc.

I increased my scale set instance count but the virtual machines in my standby pool weren't used.

Ensure that the virtual machines in your standby pool are in the desired state prior to attempting a scale-out event. For example, if using a standby pool with the virtual machine states set to deallocated, the standby pool will only give out instances that are in the deallocated state. If instances are in any other states such as creating, running, updating, etc., the scale set will default to creating a new instance directly in the scale set.

Next steps

Learn more about standby pools on Virtual Machine Scale Sets.