Difference between Spot and Low-priority nodes in Azure Batch – how to identify my pool type

Question

Difference between Spot and Low-priority nodes in Azure Batch – how to identify my pool type

Paolo Mantellini 30

I haven’t really understood whether the nodes in my pool are Spot or Low-priority. How can I check it?

Himanshu Shekhar 1,170 Reputation points Microsoft External Staff Moderator

2025-09-22T10:39:24.92+00:00

Hello Paolo Mantellini

Could you please provide an update on this post?

Kindly let us know if the suggested steps helps or you need further assistance on this issue.
Paolo Mantellini 30 Reputation points

2025-09-22T14:10:37.8733333+00:00

thanks, the answer was helpful
Paolo Mantellini 30 Reputation points

2025-09-23T07:50:57.6933333+00:00

I would like to ask if it is possible to configure Spot nodes on a Batch account with Batch service allocation mode, or if it must be created with User subscription mode
Himanshu Shekhar 1,170 Reputation points Microsoft External Staff Moderator

2025-09-23T10:58:07.27+00:00
Hi Paolo Mantellini

After the retirement of Low-priority VMs in Azure Batch on September 30, 2025, Batch-managed allocation mode accounts will not automatically support Spot VMs.

To use Spot VMs with Azure Batch, you must migrate to Batch accounts using "User subscription" allocation mode.

Batch-managed allocation mode (the default for older Batch accounts) only supports Low-priority VMs, which are being retired.

User subscription allocation mode supports Spot VMs.

After the retirement date, attempts to allocate low-priority compute nodes will fail, and existing pools depending on these will not function.

Spot VMs are a different Azure-wide implementation available under User subscription allocation mode, not under Batch-managed mode.

To continue leveraging discounted, preemptible compute for your batch jobs after low-priority VM retirement, you need to:

Migrate (or recreate) your Batch pools under a Batch account in User subscription allocation mode. Configure your pools to use Spot VMs, which are fully supported there.

Please check below:
Use Spot VMs with Batch workloads
Migrate Batch low-priority VMs to Spot VMs
Paolo Mantellini 30 Reputation points

2025-09-23T12:09:02.9566667+00:00

Could you tell me how migration would be possible? At the moment, I was only able to create a new account, without the option to move my existing Azure Batch managed account into user subscription mode. However, creating a new account requires submitting quota increase requests to support. Is there a faster way?

Also, when creating the pool, in the creation settings I cannot select a “Spot node” but only “Low-priority/Spot target.” Based on what does the system differentiate between the two? I’m attaching an image.

Screenshot 2025-09-23 140755.png
Himanshu Shekhar 1,170 Reputation points Microsoft External Staff Moderator

2025-09-24T14:45:56.5666667+00:00

Paolo Mantellini

Moving Batch accounts directly from one region to another isn't possible. You can use an Azure Resource Manager template (ARM template) to export the existing configuration of your Batch account instead. Then, stage the resource in another region.

First, export the Batch account to a template. Next, modify the parameters to match the destination region and then need to deploy the modified template to the new region.

Last, we need to recreate jobs and other features in the account - https://free.blessedness.top/en-us/azure/batch/account-move

Many limits are default quotas, which Azure applies at the subscription or account level - https://free.blessedness.top/en-us/azure/batch/batch-quota-limit

Spot nodes use Azure Spot VM capacity and require subscription mode - https://free.blessedness.top/en-us/azure/batch/batch-spot-vms

This explains more about nodes and pools, along with considerations when creating and using them in an Azure Batch workflow - https://free.blessedness.top/en-us/azure/batch/nodes-and-pools
Paolo Mantellini 30 Reputation points

2025-09-25T07:38:52.8666667+00:00

ok, it's clear. Thank you so much!
Himanshu Shekhar 1,170 Reputation points Microsoft External Staff Moderator

2025-09-25T08:52:32.0466667+00:00

Hello Paolo Mantellini

If the query has been resolved, please take a moment to accept answers and upvote it 👍 to make it helpful to the community.

Thank you for helping to improve Microsoft Q&A!

Answer accepted by question author

0 additional answers

Your answer

Himanshu Shekhar 1,170 Reputation points Microsoft External Staff Moderator

2025-09-22T10:39:24.92+00:00

Hello Paolo Mantellini

Could you please provide an update on this post?

Kindly let us know if the suggested steps helps or you need further assistance on this issue.
Paolo Mantellini 30 Reputation points

2025-09-22T14:10:37.8733333+00:00

thanks, the answer was helpful
Paolo Mantellini 30 Reputation points

2025-09-23T07:50:57.6933333+00:00

I would like to ask if it is possible to configure Spot nodes on a Batch account with Batch service allocation mode, or if it must be created with User subscription mode
Himanshu Shekhar 1,170 Reputation points Microsoft External Staff Moderator

2025-09-23T10:58:07.27+00:00

Hi Paolo Mantellini

After the retirement of Low-priority VMs in Azure Batch on September 30, 2025, Batch-managed allocation mode accounts will not automatically support Spot VMs.

To use Spot VMs with Azure Batch, you must migrate to Batch accounts using "User subscription" allocation mode.

Batch-managed allocation mode (the default for older Batch accounts) only supports Low-priority VMs, which are being retired.

User subscription allocation mode supports Spot VMs.

After the retirement date, attempts to allocate low-priority compute nodes will fail, and existing pools depending on these will not function.

Spot VMs are a different Azure-wide implementation available under User subscription allocation mode, not under Batch-managed mode.

To continue leveraging discounted, preemptible compute for your batch jobs after low-priority VM retirement, you need to:

Migrate (or recreate) your Batch pools under a Batch account in User subscription allocation mode. Configure your pools to use Spot VMs, which are fully supported there.

Please check below:
Use Spot VMs with Batch workloads
Migrate Batch low-priority VMs to Spot VMs
Paolo Mantellini 30 Reputation points

2025-09-23T12:09:02.9566667+00:00

Could you tell me how migration would be possible? At the moment, I was only able to create a new account, without the option to move my existing Azure Batch managed account into user subscription mode. However, creating a new account requires submitting quota increase requests to support. Is there a faster way?

Also, when creating the pool, in the creation settings I cannot select a “Spot node” but only “Low-priority/Spot target.” Based on what does the system differentiate between the two? I’m attaching an image.

Screenshot 2025-09-23 140755.png
Himanshu Shekhar 1,170 Reputation points Microsoft External Staff Moderator

2025-09-24T14:45:56.5666667+00:00

Paolo Mantellini

Moving Batch accounts directly from one region to another isn't possible. You can use an Azure Resource Manager template (ARM template) to export the existing configuration of your Batch account instead. Then, stage the resource in another region.

First, export the Batch account to a template. Next, modify the parameters to match the destination region and then need to deploy the modified template to the new region.

Last, we need to recreate jobs and other features in the account - https://free.blessedness.top/en-us/azure/batch/account-move

Many limits are default quotas, which Azure applies at the subscription or account level - https://free.blessedness.top/en-us/azure/batch/batch-quota-limit

Spot nodes use Azure Spot VM capacity and require subscription mode - https://free.blessedness.top/en-us/azure/batch/batch-spot-vms

This explains more about nodes and pools, along with considerations when creating and using them in an Azure Batch workflow - https://free.blessedness.top/en-us/azure/batch/nodes-and-pools
Paolo Mantellini 30 Reputation points

2025-09-25T07:38:52.8666667+00:00

ok, it's clear. Thank you so much!
Himanshu Shekhar 1,170 Reputation points Microsoft External Staff Moderator

2025-09-25T08:52:32.0466667+00:00

Hello Paolo Mantellini

If the query has been resolved, please take a moment to accept answers and upvote it 👍 to make it helpful to the community.

Thank you for helping to improve Microsoft Q&A!

Answer 1

Hi Paolo Mantellini

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

Low-priority VMs are original discounted compute option in Azure Batch.

Spot VMs are newer option, offering deeper discounts and replacing low-priority VMs. They use Azure's Spot pricing model and are more integrated with Azure's broader infrastructure.

To determine whether your pool uses Spot or Low-priority nodes:

Check the pool configuration in the Azure portal or via the Batch API.

Look for the property:

"vmPriority": "Spot" > indicates Spot VMs.

"vmPriority": "LowPriority" > indicates Low-priority VMs.

Moving Batch accounts directly from one region to another isn't possible. You can use an Azure Resource Manager template (ARM template) to export the existing configuration of your Batch account instead. Then, stage the resource in another region.

First, export the Batch account to a template. Next, modify the parameters to match the destination region and then need to deploy the modified template to the new region.

Last, we need to recreate jobs and other features in the account - https://free.blessedness.top/en-us/azure/batch/account-move

Many limits are default quotas, which Azure applies at the subscription or account level - https://free.blessedness.top/en-us/azure/batch/batch-quota-limit

Spot nodes use Azure Spot VM capacity and require subscription mode - https://free.blessedness.top/en-us/azure/batch/batch-spot-vms

This explains more about nodes and pools, along with considerations when creating and using them in an Azure Batch workflow - https://free.blessedness.top/en-us/azure/batch/nodes-and-pools

Kindly let us know if the suggested steps helps or you need further assistance on this issue.

Regards

Himanshu

Share via

Difference between Spot and Low-priority nodes in Azure Batch – how to identify my pool type

0 additional answers

Your answer