How do auto-scale formulas work?

Auto-scale formulas are evaluated every 15 minutes (configurable from 5 to 60 minutes) and return a target number of dedicated and/or low-priority nodes. Formulas can reference built-in variables like $PendingTasks (tasks waiting for a node), $RunningTasks, $ActiveTasks, and time-based functions. A common formula sets the target to the number of pending tasks divided by the tasks-per-node capacity: $TargetDedicatedNodes = min(maxNodes, $PendingTasks / tasksPerNode). You can combine multiple variables with conditional logic for sophisticated scaling behavior.

What is the difference between dedicated and low-priority nodes?

Dedicated nodes are allocated from Azure's regular capacity and are guaranteed to remain available for the lifetime of the pool. Low-priority nodes are provisioned from Azure's surplus capacity at up to 80% discount but can be preempted at any time when Azure needs the capacity back. When a low-priority node is preempted, running tasks are requeued. Use low-priority nodes for fault-tolerant, checkpointable workloads. Many batch workloads mix dedicated nodes (for steady baseline) with low-priority nodes (for burst capacity).

Azure Batch Pool Builder

ComputeAzure

Build Azure Batch pool configurations with auto-scale and container support.

Azure Batch Configuration

Build Azure Batch pool configs with auto-scale formulas, container support, and networking.

Required Fields

poolIdbatchAccountNamevmSizedeploymentConfigurationscaleSettings

{
  "poolId": "render-pool-linux",
  "batchAccountName": "batchcontosoprod",
  "resourceGroup": "rg-batch",
  "location": "eastus2",
  "vmSize": "Standard_HB120rs_v3",
  "deploymentConfiguration": {
    "virtualMachineConfiguration": {
      "imageReference": {
        "publisher": "microsoft-azure-batch",
        "offer": "ubuntu-server-container",
        "sku": "20-04-lts",
        "version": "latest"
      },
      "nodeAgentSkuId": "batch.node.ubuntu 20.04",
      "containerConfiguration": {
        "type": "DockerCompatible",
        "containerImageNames": [
          "myregistry.azurecr.io/render-engine:latest"
        ],
        "containerRegistries": [
          {
            "registryServer": "myregistry.azurecr.io",
            "identityReference": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-batch/providers/Microsoft.ManagedIdentity/userAssignedIdentities/id-batch-acr"
          }
        ]
      }
    }
  },
  "scaleSettings": {
    "autoScale": {
      "evaluationInterval": "PT5M",
      "formula": "startingNumberOfVMs = 0; maxNumberOfVMs = 50; pendingTaskSamplePercent = $PendingTasks.GetSamplePercent(180 * TimeInterval_Second); pendingTaskSamples = pendingTaskSamplePercent < 70 ? startingNumberOfVMs : avg($PendingTasks.GetSample(180 * TimeInterval_Second)); $TargetDedicatedNodes = min(maxNumberOfVMs, pendingTaskSamples);"
    }
  },
  "taskSlotsPerNode": 4,
  "taskSchedulingPolicy": {
    "nodeFillType": "Pack"
  },
  "interNodeCommunication": "Enabled",
  "networkConfiguration": {
    "subnetId": "/subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg-networking/providers/Microsoft.Network/virtualNetworks/vnet-batch/subnets/snet-pool",
    "publicIPAddressConfiguration": {
      "provision": "NoPublicIPAddresses"
    }
  },
  "startTask": {
    "commandLine": "/bin/bash -c 'apt-get update && apt-get install -y libgl1-mesa-glx'",
    "waitForSuccess": true,
    "userIdentity": {
      "autoUser": {
        "scope": "Pool",
        "elevationLevel": "Admin"
      }
    },
    "maxTaskRetryCount": 2
  },
  "metadata": [
    { "name": "environment", "value": "production" },
    { "name": "workload", "value": "rendering" }
  ]
}

Generated Output

Output will appear here...

About This Tool

Azure Batch provides cloud-scale job scheduling and compute management, letting you run large-scale parallel and HPC workloads without managing infrastructure. A Batch pool defines the compute nodes — VM size, image, scaling mode (fixed or auto-scale), container support, start tasks, and networking configuration. Auto-scale formulas use a rich expression language to dynamically adjust pool size based on pending tasks, time of day, or custom metrics. The Batch Pool Builder helps you configure pool specifications with proper auto-scale formulas, container settings, and node communication options.

When to Use This Tool

•Creating auto-scale pools that grow based on pending task count and shrink to zero during idle periods
•Configuring container-enabled pools with pre-fetched Docker images for fast job startup
•Building pool specifications with start tasks that install dependencies and mount Azure file shares
•Defining low-priority (Spot) node pools for cost-effective batch processing with preemption handling

Frequently Asked Questions

How do auto-scale formulas work?: Auto-scale formulas are evaluated every 15 minutes (configurable from 5 to 60 minutes) and return a target number of dedicated and/or low-priority nodes. Formulas can reference built-in variables like $PendingTasks (tasks waiting for a node), $RunningTasks, $ActiveTasks, and time-based functions. A common formula sets the target to the number of pending tasks divided by the tasks-per-node capacity: $TargetDedicatedNodes = min(maxNodes, $PendingTasks / tasksPerNode). You can combine multiple variables with conditional logic for sophisticated scaling behavior.
What is the difference between dedicated and low-priority nodes?: Dedicated nodes are allocated from Azure's regular capacity and are guaranteed to remain available for the lifetime of the pool. Low-priority nodes are provisioned from Azure's surplus capacity at up to 80% discount but can be preempted at any time when Azure needs the capacity back. When a low-priority node is preempted, running tasks are requeued. Use low-priority nodes for fault-tolerant, checkpointable workloads. Many batch workloads mix dedicated nodes (for steady baseline) with low-priority nodes (for burst capacity).

Related Learning Guides

Azure VM Series Guide22 min read

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.