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
Once completed you will see along with the spot nodes
and from portal you already know where to check from as you have already highlighted in your screenshot-
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
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.
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.