Azure Batch
An Azure service that provides cloud-scale job scheduling and compute management.
358 questions
Migrate a Batch pool with low-priority compute nodes or create a Batch pool with Spot instances
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 89%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED4%3C/text%3E%3C/svg%3E)
Daniel-4204
45
Reputation points
I received the “Migrate a Batch pool with low-priority compute nodes or create a Batch pool with Spot instances” email, listing affected Azure Batch resources across multiple subscriptions. I have reviewed the support documentation and confirmed that all child link prerequisites are satisfied.
At this point, I believe I’m at the final step of the migration process. However, when examining the affected resource, I’m unclear on how changing the available settings satisfies the migration requirement.
Specifically, in the resource settings, I noticed that the field “Target Spot/low-priority nodes” combines both low-priority and Spot instances into a single line item. Given that they are merged into one field, I don’t see an explicit option to migrate low-priority nodes to Spot instances; only a numerical value representing the total number of nodes.
How should I proceed to ensure the migration is correctly applied? Has anyone encountered this issue before and can offer guidance?
Thanks in advance for any insights!
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 38%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Markapuram Sudheer Reddy 1,165 Reputation points Microsoft External Staff2025-03-07T20:17:21.8266667+00:00 Hi Daniel-4204,
Thank You for reaching out to Microsoft Q&A forum.
Ensure your Batch account uses the user subscription pool allocation mode to support Spot instances. Because of transition phase, the combined field "Target Spot/low-priority nodes" allows you to manage both types of nodes during this transition. So, migrate the workloads to be transitioned to Spot instances for continue operating.
https://learn.microsoft.com/en-us/azure/batch/batch-account-create-portal
https://learn.microsoft.com/en-us/azure/batch/low-priority-vms-retirement-migration-guide
If the information is helpful, please click on "Upvote"
If you have any queries, please do let us know, we will help you.
Sign in to comment
Sign in to answer