Frequently asked questions about standby pools for Azure Container Instances

Important

For standby pools to successfully create and manage resources, it requires access to the associated resources in your subscription. Ensure the correct permissions are assigned to the standby pool resource provider in order for your standby pool to function properly. For detailed instructions, see configure role permissions for standby pools.

Get answers to frequently asked questions about standby pools for Azure Container Instances.

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

How many container groups can my standby pool have?

The maximum number of container groups in a standby pool is 2,000.

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 don't currently support move capabilities. 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 containers 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 containers in the standby pool fail after encountering a quota error. Check for multiple types of quotas such as Cores, Network Interfaces, IP Addresses, etc.

I requested a container from my pool but it created a new container instead.

Ensure that the container groups in your standby pool are in the running state before issuing a request. For example, if using a standby If containers are in any other states such as creating or deleting, the container request defaults to creating a new container group from scratch.

Next steps

Learn more about standby pools on Azure Container Instances.