Migrate a Batch pool with low-priority compute nodes or create a Batch pool with Spot instances

Daniel-4204 65 Reputation points
2025-03-07T16:29:30.51+00:00

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!

User's image

Azure Batch
Azure Batch
An Azure service that provides cloud-scale job scheduling and compute management.
368 questions
{count} votes

Accepted answer
  1. Arko 2,130 Reputation points Microsoft External Staff
    2025-03-19T09:58:04.15+00:00

    Hello Daniel-4204, there are two ways to ensure the migration from Low-Priority nodes to Spot instances is correctly applied and visually confirm the migration in Azure.

    As you rightly pointed out that Azure Batch now treats Spot and Low-Priority nodes as the same field, the verification can be done either from CLI or Portal.

    Your first question- How Should I Proceed to Ensure the Migration is Correctly Applied?

    Answer- If you are trying this from CLI the run the below command

    
    az batch pool show \
    
        --account-name <your-batch-account-name> \
    
        --account-endpoint "https://<your-batch-account-name>.<region>.batch.azure.com" \
    
        --pool-id <your-pool-id> \
    
        --query "{PoolID:id, VMSize:vmSize, SpotNodes:scaleSettings.targetLowPriorityNodes}"
    
    

    If the migration is in progress you should see

    enter image description here

    Once completed you will see along with the spot nodes

    enter image description here

    and from portal you already know where to check from as you have already highlighted in your screenshot-

    enter image description here

    Second question- How to Visually Confirm the Migration from Low-Priority to Spot Instances?

    Answer- Again this can be verified from CLI

    
    az batch node list \
    
        --account-name <your-batch-account-name> \
    
        --account-endpoint "https://<your-batch-account-name>.<region>.batch.azure.com" \
    
        --pool-id <your-pool-id> \
    
        --query "[].{ID:id, State:state, SchedulingState:schedulingState}"
    
    

    or from portal

    enter image description here

    If nodes exist in "idle" or "running", the migration was successful.

    Therefore, to understand if things are working as intended, confirm that the pool is using Spot instances using az batch pool show then you can check spot quotas using az vm list-usage and request an increase if needed and finally visually verify migration in Portal under Pools > Scale > Target Spot/Low-Priority Nodes.

    enter image description here

    Microsoft document

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.           

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.