Microsoft.Batch (stable:2024-07-01.20.0)

2025/02/20 • 14 updated methods

Pool_ListUsageMetrics (updated)
Description :  Warning: This operation has been deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-pool-list-usage-metrics-api-will-be-retired-on-30-september-2024 for more information.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Pool_ListUsageMetrics",
  "Description": {
    "new": "Warning: This operation has been deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-pool-list-usage-metrics-api-will-be-retired-on-30-september-2024 for more information.",
    "old": "If you do not specify a $filter clause including a poolId, the response includes all Pools that existed in the Account in the time range of the returned aggregation intervals. If you do not specify a $filter clause including a startTime or endTime these filters default to the start and end times of the last aggregation interval currently available; that is, only the last aggregation interval is returned."
  }
}

⚼ Request

GET:  /poolusagemetrics
{
starttime:
{
Description: The earliest time from which to include metrics. This must be at least two and a half hours before the current time. If not specified this defaults to the start time of the last aggregation interval currently available. ,
Format: date-time ,
Required: False ,
}
string ,
endtime:
{
Description: The latest time from which to include metrics. This must be at least two hours before the current time. If not specified this defaults to the end time of the last aggregation interval currently available. ,
Format: date-time ,
Required: False ,
}
string ,
$filter:
{
Description: An OData $filter clause. For more information on constructing this filter, see https://learn.microsoft.com/rest/api/batchservice/odata-filters-in-batch#list-account-usage-metrics. ,
Required: False ,
}
string ,
maxresults:
{
Description: The maximum number of items to return in the response. A maximum of 1000 results will be returned. ,
Format: int32 ,
Required: False ,
}
integer ,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
}
,
$schema:
{
value:
{
Required: False ,
}
[
{
poolId:
{
Required: True ,
}
string ,
startTime:
{
Format: date-time ,
Required: True ,
}
string ,
endTime:
{
Format: date-time ,
Required: True ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
totalCoreHours:
{
Format: double ,
Required: True ,
}
number ,
}
,
]
,
odata.nextLink:
{
Required: False ,
}
string ,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
JobSchedule_Get (updated)
Description :  Gets information about the specified Job Schedule.
Reference :  Link ¶

⚶ Changes

{
  "#id": "JobSchedule_Get",
  "$responses": {
    "200": {
      "$properties": {
        "jobSpecification": [
          {
            "jobManagerTask": [
              {
                "#name": "authenticationTokenSettings",
                "Description": {
                  "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                  "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
                }
              }
            ]
          }
        ]
      }
    }
  }
}

⚼ Request

GET:  /jobschedules/{jobScheduleId}
{
jobScheduleId:
{
Description: The ID of the Job Schedule to get. ,
Required: True ,
}
string ,
$select:
{
Description: An OData $select clause. ,
Required: False ,
}
string ,
$expand:
{
Description: An OData $expand clause. ,
Required: False ,
}
string ,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service exactly matches the value specified by the client. ,
Required: False ,
}
string ,
If-None-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service does not match the value specified by the client. ,
Required: False ,
}
string ,
If-Modified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Unmodified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has not been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
}
,
$schema:
{
id:
{
Required: False ,
}
string ,
displayName:
{
Required: False ,
}
string ,
url:
{
Required: False ,
}
string ,
eTag:
{
Description: This is an opaque string. You can use it to detect whether the Job Schedule has changed between requests. In particular, you can be pass the ETag with an Update Job Schedule request to specify that your changes should take effect only if nobody else has modified the schedule in the meantime. ,
Required: False ,
}
string ,
lastModified:
{
Description: This is the last time at which the schedule level data, such as the Job specification or recurrence information, changed. It does not factor in job-level changes such as new Jobs being created or Jobs changing state. ,
Format: date-time ,
Required: False ,
}
string ,
creationTime:
{
Format: date-time ,
Required: False ,
}
string ,
state:
{
Enum:
{
active: The Job Schedule is active and will create Jobs as per its schedule. ,
completed: The Job Schedule has terminated, either by reaching its end time or by the user terminating it explicitly. ,
disabled: The user has disabled the Job Schedule. The scheduler will not initiate any new Jobs will on this schedule, but any existing active Job will continue to run. ,
terminating: The Job Schedule has no more work to do, or has been explicitly terminated by the user, but the termination operation is still in progress. The scheduler will not initiate any new Jobs for this Job Schedule, nor is any existing Job active. ,
deleting: The user has requested that the Job Schedule be deleted, but the delete operation is still in progress. The scheduler will not initiate any new Jobs for this Job Schedule, and will delete any existing Jobs and Tasks under the Job Schedule, including any active Job. The Job Schedule will be deleted when all Jobs and Tasks under the Job Schedule have been deleted. ,
}
,
Required: False ,
}
enum ,
stateTransitionTime:
{
Format: date-time ,
Required: False ,
}
string ,
previousState:
{
Description: This property is not present if the Job Schedule is in its initial active state. ,
Enum:
{
active: The Job Schedule is active and will create Jobs as per its schedule. ,
completed: The Job Schedule has terminated, either by reaching its end time or by the user terminating it explicitly. ,
disabled: The user has disabled the Job Schedule. The scheduler will not initiate any new Jobs will on this schedule, but any existing active Job will continue to run. ,
terminating: The Job Schedule has no more work to do, or has been explicitly terminated by the user, but the termination operation is still in progress. The scheduler will not initiate any new Jobs for this Job Schedule, nor is any existing Job active. ,
deleting: The user has requested that the Job Schedule be deleted, but the delete operation is still in progress. The scheduler will not initiate any new Jobs for this Job Schedule, and will delete any existing Jobs and Tasks under the Job Schedule, including any active Job. The Job Schedule will be deleted when all Jobs and Tasks under the Job Schedule have been deleted. ,
}
,
Required: False ,
}
enum ,
previousStateTransitionTime:
{
Description: This property is not present if the Job Schedule is in its initial active state. ,
Format: date-time ,
Required: False ,
}
string ,
schedule:
{
Description: All times are fixed respective to UTC and are not impacted by daylight saving time. ,
Required: False ,
}
{
doNotRunUntil:
{
Description: If you do not specify a doNotRunUntil time, the schedule becomes ready to create Jobs immediately. ,
Format: date-time ,
Required: False ,
}
string ,
doNotRunAfter:
{
Description: If you do not specify a doNotRunAfter time, and you are creating a recurring Job Schedule, the Job Schedule will remain active until you explicitly terminate it. ,
Format: date-time ,
Required: False ,
}
string ,
startWindow:
{
Description: If a Job is not created within the startWindow interval, then the 'opportunity' is lost; no Job will be created until the next recurrence of the schedule. If the schedule is recurring, and the startWindow is longer than the recurrence interval, then this is equivalent to an infinite startWindow, because the Job that is 'due' in one recurrenceInterval is not carried forward into the next recurrence interval. The default is infinite. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
recurrenceInterval:
{
Description: Because a Job Schedule can have at most one active Job under it at any given time, if it is time to create a new Job under a Job Schedule, but the previous Job is still running, the Batch service will not create the new Job until the previous Job finishes. If the previous Job does not finish within the startWindow period of the new recurrenceInterval, then no new Job will be scheduled for that interval. For recurring Jobs, you should normally specify a jobManagerTask in the jobSpecification. If you do not use jobManagerTask, you will need an external process to monitor when Jobs are created, add Tasks to the Jobs and terminate the Jobs ready for the next recurrence. The default is that the schedule does not recur: one Job is created, within the startWindow after the doNotRunUntil time, and the schedule is complete as soon as that Job finishes. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
}
,
jobSpecification:
{
Required: False ,
}
{
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. This priority is used as the default for all Jobs under the Job Schedule. You can update a Job's priority after it has been created using by using the update Job API. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
displayName:
{
Description: The name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
onAllTasksComplete:
{
Description: Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job using the Task API. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: The primary purpose of the Job Release Task is to undo changes to Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Compute Nodes that have run the Job Preparation Task. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: True ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
}
,
executionInfo:
{
Required: False ,
}
{
nextRunTime:
{
Description: This property is meaningful only if the schedule is in the active state when the time comes around. For example, if the schedule is disabled, no Job will be created at nextRunTime unless the Job is enabled before then. ,
Format: date-time ,
Required: False ,
}
string ,
recentJob:
{
Description: This property is present only if the at least one Job has run under the schedule. ,
Required: False ,
}
{
id:
{
Required: False ,
}
string ,
url:
{
Required: False ,
}
string ,
}
,
endTime:
{
Description: This property is set only if the Job Schedule is in the completed state. ,
Format: date-time ,
Required: False ,
}
string ,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
stats:
{
Required: False ,
}
{
url:
{
Required: True ,
}
string ,
startTime:
{
Format: date-time ,
Required: True ,
}
string ,
lastUpdateTime:
{
Format: date-time ,
Required: True ,
}
string ,
userCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
kernelCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
wallClockTime:
{
Description: The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. ,
Format: duration ,
Required: True ,
}
string ,
readIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
writeIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
readIOGiB:
{
Format: double ,
Required: True ,
}
number ,
writeIOGiB:
{
Format: double ,
Required: True ,
}
number ,
numSucceededTasks:
{
Format: int64 ,
Required: True ,
}
integer ,
numFailedTasks:
{
Format: int64 ,
Required: True ,
}
integer ,
numTaskRetries:
{
Format: int64 ,
Required: True ,
}
integer ,
waitTime:
{
Description: This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. ,
Format: duration ,
Required: True ,
}
string ,
}
,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
JobSchedule_Patch (updated)
Description :  This replaces only the Job Schedule properties specified in the request. For example, if the schedule property is not specified with this request, then the Batch service will keep the existing schedule. Changes to a Job Schedule only impact Jobs created by the schedule after the update has taken place; currently running Jobs are unaffected.
Reference :  Link ¶

⚶ Changes

{
  "#id": "JobSchedule_Patch",
  "$parameters": {
    "jobSchedulePatchParameter": {
      "$properties": {
        "jobSpecification": [
          {
            "jobManagerTask": [
              {
                "#name": "authenticationTokenSettings",
                "Description": {
                  "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                  "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
                }
              }
            ]
          }
        ]
      }
    }
  }
}

⚼ Request

PATCH:  /jobschedules/{jobScheduleId}
{
jobScheduleId:
{
Description: The ID of the Job Schedule to update. ,
Required: True ,
}
string ,
jobSchedulePatchParameter:
{
Description: The parameters for the request. ,
Required: True ,
}
{
schedule:
{
Description: All times are fixed respective to UTC and are not impacted by daylight saving time. If you do not specify this element, the existing schedule is left unchanged. ,
Required: False ,
}
{
doNotRunUntil:
{
Description: If you do not specify a doNotRunUntil time, the schedule becomes ready to create Jobs immediately. ,
Format: date-time ,
Required: False ,
}
string ,
doNotRunAfter:
{
Description: If you do not specify a doNotRunAfter time, and you are creating a recurring Job Schedule, the Job Schedule will remain active until you explicitly terminate it. ,
Format: date-time ,
Required: False ,
}
string ,
startWindow:
{
Description: If a Job is not created within the startWindow interval, then the 'opportunity' is lost; no Job will be created until the next recurrence of the schedule. If the schedule is recurring, and the startWindow is longer than the recurrence interval, then this is equivalent to an infinite startWindow, because the Job that is 'due' in one recurrenceInterval is not carried forward into the next recurrence interval. The default is infinite. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
recurrenceInterval:
{
Description: Because a Job Schedule can have at most one active Job under it at any given time, if it is time to create a new Job under a Job Schedule, but the previous Job is still running, the Batch service will not create the new Job until the previous Job finishes. If the previous Job does not finish within the startWindow period of the new recurrenceInterval, then no new Job will be scheduled for that interval. For recurring Jobs, you should normally specify a jobManagerTask in the jobSpecification. If you do not use jobManagerTask, you will need an external process to monitor when Jobs are created, add Tasks to the Jobs and terminate the Jobs ready for the next recurrence. The default is that the schedule does not recur: one Job is created, within the startWindow after the doNotRunUntil time, and the schedule is complete as soon as that Job finishes. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
}
,
jobSpecification:
{
Description: Updates affect only Jobs that are started after the update has taken place. Any currently active Job continues with the older specification. ,
Required: False ,
}
{
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. This priority is used as the default for all Jobs under the Job Schedule. You can update a Job's priority after it has been created using by using the update Job API. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
displayName:
{
Description: The name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
onAllTasksComplete:
{
Description: Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job using the Task API. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: The primary purpose of the Job Release Task is to undo changes to Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Compute Nodes that have run the Job Preparation Task. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: True ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
}
,
metadata:
{
Description: If you do not specify this element, existing metadata is left unchanged. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
}
,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service exactly matches the value specified by the client. ,
Required: False ,
}
string ,
If-None-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service does not match the value specified by the client. ,
Required: False ,
}
string ,
If-Modified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Unmodified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has not been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
dataserviceid:
{
Description: The OData ID of the resource to which the request applied. ,
}
string ,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
JobSchedule_Update (updated)
Description :  This fully replaces all the updatable properties of the Job Schedule. For example, if the schedule property is not specified with this request, then the Batch service will remove the existing schedule. Changes to a Job Schedule only impact Jobs created by the schedule after the update has taken place; currently running Jobs are unaffected.
Reference :  Link ¶

⚶ Changes

{
  "#id": "JobSchedule_Update",
  "$parameters": {
    "jobScheduleUpdateParameter": {
      "$properties": {
        "jobSpecification": [
          {
            "jobManagerTask": [
              {
                "#name": "authenticationTokenSettings",
                "Description": {
                  "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                  "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
                }
              }
            ]
          }
        ]
      }
    }
  }
}

⚼ Request

PUT:  /jobschedules/{jobScheduleId}
{
jobScheduleId:
{
Description: The ID of the Job Schedule to update. ,
Required: True ,
}
string ,
jobScheduleUpdateParameter:
{
Description: The parameters for the request. ,
Required: True ,
}
{
schedule:
{
Description: All times are fixed respective to UTC and are not impacted by daylight saving time. If you do not specify this element, it is equivalent to passing the default schedule: that is, a single Job scheduled to run immediately. ,
Required: True ,
}
{
doNotRunUntil:
{
Description: If you do not specify a doNotRunUntil time, the schedule becomes ready to create Jobs immediately. ,
Format: date-time ,
Required: False ,
}
string ,
doNotRunAfter:
{
Description: If you do not specify a doNotRunAfter time, and you are creating a recurring Job Schedule, the Job Schedule will remain active until you explicitly terminate it. ,
Format: date-time ,
Required: False ,
}
string ,
startWindow:
{
Description: If a Job is not created within the startWindow interval, then the 'opportunity' is lost; no Job will be created until the next recurrence of the schedule. If the schedule is recurring, and the startWindow is longer than the recurrence interval, then this is equivalent to an infinite startWindow, because the Job that is 'due' in one recurrenceInterval is not carried forward into the next recurrence interval. The default is infinite. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
recurrenceInterval:
{
Description: Because a Job Schedule can have at most one active Job under it at any given time, if it is time to create a new Job under a Job Schedule, but the previous Job is still running, the Batch service will not create the new Job until the previous Job finishes. If the previous Job does not finish within the startWindow period of the new recurrenceInterval, then no new Job will be scheduled for that interval. For recurring Jobs, you should normally specify a jobManagerTask in the jobSpecification. If you do not use jobManagerTask, you will need an external process to monitor when Jobs are created, add Tasks to the Jobs and terminate the Jobs ready for the next recurrence. The default is that the schedule does not recur: one Job is created, within the startWindow after the doNotRunUntil time, and the schedule is complete as soon as that Job finishes. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
}
,
jobSpecification:
{
Description: Updates affect only Jobs that are started after the update has taken place. Any currently active Job continues with the older specification. ,
Required: True ,
}
{
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. This priority is used as the default for all Jobs under the Job Schedule. You can update a Job's priority after it has been created using by using the update Job API. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
displayName:
{
Description: The name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
onAllTasksComplete:
{
Description: Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job using the Task API. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: The primary purpose of the Job Release Task is to undo changes to Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Compute Nodes that have run the Job Preparation Task. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: True ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
}
,
metadata:
{
Description: If you do not specify this element, it takes the default value of an empty list; in effect, any existing metadata is deleted. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
}
,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service exactly matches the value specified by the client. ,
Required: False ,
}
string ,
If-None-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service does not match the value specified by the client. ,
Required: False ,
}
string ,
If-Modified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Unmodified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has not been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
dataserviceid:
{
Description: The OData ID of the resource to which the request applied. ,
}
string ,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
JobSchedule_Add (updated)
Description :  Adds a Job Schedule to the specified Account.
Reference :  Link ¶

⚶ Changes

{
  "#id": "JobSchedule_Add",
  "$parameters": {
    "cloudJobSchedule": {
      "$properties": {
        "jobSpecification": [
          {
            "jobManagerTask": [
              {
                "#name": "authenticationTokenSettings",
                "Description": {
                  "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                  "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
                }
              }
            ]
          }
        ]
      }
    }
  }
}

⚼ Request

POST:  /jobschedules
{
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
cloudJobSchedule:
{
Description: The Job Schedule to be added. ,
Required: True ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). ,
Required: True ,
}
string ,
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
schedule:
{
Description: All times are fixed respective to UTC and are not impacted by daylight saving time. ,
Required: True ,
}
{
doNotRunUntil:
{
Description: If you do not specify a doNotRunUntil time, the schedule becomes ready to create Jobs immediately. ,
Format: date-time ,
Required: False ,
}
string ,
doNotRunAfter:
{
Description: If you do not specify a doNotRunAfter time, and you are creating a recurring Job Schedule, the Job Schedule will remain active until you explicitly terminate it. ,
Format: date-time ,
Required: False ,
}
string ,
startWindow:
{
Description: If a Job is not created within the startWindow interval, then the 'opportunity' is lost; no Job will be created until the next recurrence of the schedule. If the schedule is recurring, and the startWindow is longer than the recurrence interval, then this is equivalent to an infinite startWindow, because the Job that is 'due' in one recurrenceInterval is not carried forward into the next recurrence interval. The default is infinite. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
recurrenceInterval:
{
Description: Because a Job Schedule can have at most one active Job under it at any given time, if it is time to create a new Job under a Job Schedule, but the previous Job is still running, the Batch service will not create the new Job until the previous Job finishes. If the previous Job does not finish within the startWindow period of the new recurrenceInterval, then no new Job will be scheduled for that interval. For recurring Jobs, you should normally specify a jobManagerTask in the jobSpecification. If you do not use jobManagerTask, you will need an external process to monitor when Jobs are created, add Tasks to the Jobs and terminate the Jobs ready for the next recurrence. The default is that the schedule does not recur: one Job is created, within the startWindow after the doNotRunUntil time, and the schedule is complete as soon as that Job finishes. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
}
,
jobSpecification:
{
Required: True ,
}
{
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. This priority is used as the default for all Jobs under the Job Schedule. You can update a Job's priority after it has been created using by using the update Job API. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
displayName:
{
Description: The name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
onAllTasksComplete:
{
Description: Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job using the Task API. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: The primary purpose of the Job Release Task is to undo changes to Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Compute Nodes that have run the Job Preparation Task. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: True ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
}
,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (201)

{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
dataserviceid:
{
Description: The OData ID of the resource to which the request applied. ,
}
string ,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
JobSchedule_List (updated)
Description :  Lists all of the Job Schedules in the specified Account.
Reference :  Link ¶

⚶ Changes

{
  "#id": "JobSchedule_List",
  "$responses": {
    "200": {
      "$properties": {
        "value": {
          "$properties": {
            "jobSpecification": [
              {
                "jobManagerTask": [
                  {
                    "#name": "authenticationTokenSettings",
                    "Description": {
                      "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                      "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
                    }
                  }
                ]
              }
            ]
          }
        }
      }
    }
  }
}

⚼ Request

GET:  /jobschedules
{
$filter:
{
Description: An OData $filter clause. For more information on constructing this filter, see https://learn.microsoft.com/rest/api/batchservice/odata-filters-in-batch#list-job-schedules. ,
Required: False ,
}
string ,
$select:
{
Description: An OData $select clause. ,
Required: False ,
}
string ,
$expand:
{
Description: An OData $expand clause. ,
Required: False ,
}
string ,
maxresults:
{
Description: The maximum number of items to return in the response. A maximum of 1000 Job Schedules can be returned. ,
Format: int32 ,
Required: False ,
}
integer ,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
}
,
$schema:
{
value:
{
Required: False ,
}
[
{
id:
{
Required: False ,
}
string ,
displayName:
{
Required: False ,
}
string ,
url:
{
Required: False ,
}
string ,
eTag:
{
Description: This is an opaque string. You can use it to detect whether the Job Schedule has changed between requests. In particular, you can be pass the ETag with an Update Job Schedule request to specify that your changes should take effect only if nobody else has modified the schedule in the meantime. ,
Required: False ,
}
string ,
lastModified:
{
Description: This is the last time at which the schedule level data, such as the Job specification or recurrence information, changed. It does not factor in job-level changes such as new Jobs being created or Jobs changing state. ,
Format: date-time ,
Required: False ,
}
string ,
creationTime:
{
Format: date-time ,
Required: False ,
}
string ,
state:
{
Enum:
{
active: The Job Schedule is active and will create Jobs as per its schedule. ,
completed: The Job Schedule has terminated, either by reaching its end time or by the user terminating it explicitly. ,
disabled: The user has disabled the Job Schedule. The scheduler will not initiate any new Jobs will on this schedule, but any existing active Job will continue to run. ,
terminating: The Job Schedule has no more work to do, or has been explicitly terminated by the user, but the termination operation is still in progress. The scheduler will not initiate any new Jobs for this Job Schedule, nor is any existing Job active. ,
deleting: The user has requested that the Job Schedule be deleted, but the delete operation is still in progress. The scheduler will not initiate any new Jobs for this Job Schedule, and will delete any existing Jobs and Tasks under the Job Schedule, including any active Job. The Job Schedule will be deleted when all Jobs and Tasks under the Job Schedule have been deleted. ,
}
,
Required: False ,
}
enum ,
stateTransitionTime:
{
Format: date-time ,
Required: False ,
}
string ,
previousState:
{
Description: This property is not present if the Job Schedule is in its initial active state. ,
Enum:
{
active: The Job Schedule is active and will create Jobs as per its schedule. ,
completed: The Job Schedule has terminated, either by reaching its end time or by the user terminating it explicitly. ,
disabled: The user has disabled the Job Schedule. The scheduler will not initiate any new Jobs will on this schedule, but any existing active Job will continue to run. ,
terminating: The Job Schedule has no more work to do, or has been explicitly terminated by the user, but the termination operation is still in progress. The scheduler will not initiate any new Jobs for this Job Schedule, nor is any existing Job active. ,
deleting: The user has requested that the Job Schedule be deleted, but the delete operation is still in progress. The scheduler will not initiate any new Jobs for this Job Schedule, and will delete any existing Jobs and Tasks under the Job Schedule, including any active Job. The Job Schedule will be deleted when all Jobs and Tasks under the Job Schedule have been deleted. ,
}
,
Required: False ,
}
enum ,
previousStateTransitionTime:
{
Description: This property is not present if the Job Schedule is in its initial active state. ,
Format: date-time ,
Required: False ,
}
string ,
schedule:
{
Description: All times are fixed respective to UTC and are not impacted by daylight saving time. ,
Required: False ,
}
{
doNotRunUntil:
{
Description: If you do not specify a doNotRunUntil time, the schedule becomes ready to create Jobs immediately. ,
Format: date-time ,
Required: False ,
}
string ,
doNotRunAfter:
{
Description: If you do not specify a doNotRunAfter time, and you are creating a recurring Job Schedule, the Job Schedule will remain active until you explicitly terminate it. ,
Format: date-time ,
Required: False ,
}
string ,
startWindow:
{
Description: If a Job is not created within the startWindow interval, then the 'opportunity' is lost; no Job will be created until the next recurrence of the schedule. If the schedule is recurring, and the startWindow is longer than the recurrence interval, then this is equivalent to an infinite startWindow, because the Job that is 'due' in one recurrenceInterval is not carried forward into the next recurrence interval. The default is infinite. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
recurrenceInterval:
{
Description: Because a Job Schedule can have at most one active Job under it at any given time, if it is time to create a new Job under a Job Schedule, but the previous Job is still running, the Batch service will not create the new Job until the previous Job finishes. If the previous Job does not finish within the startWindow period of the new recurrenceInterval, then no new Job will be scheduled for that interval. For recurring Jobs, you should normally specify a jobManagerTask in the jobSpecification. If you do not use jobManagerTask, you will need an external process to monitor when Jobs are created, add Tasks to the Jobs and terminate the Jobs ready for the next recurrence. The default is that the schedule does not recur: one Job is created, within the startWindow after the doNotRunUntil time, and the schedule is complete as soon as that Job finishes. The minimum value is 1 minute. If you specify a lower value, the Batch service rejects the schedule with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
}
,
jobSpecification:
{
Required: False ,
}
{
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. This priority is used as the default for all Jobs under the Job Schedule. You can update a Job's priority after it has been created using by using the update Job API. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
displayName:
{
Description: The name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
onAllTasksComplete:
{
Description: Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job using the Task API. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: The primary purpose of the Job Release Task is to undo changes to Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Compute Nodes that have run the Job Preparation Task. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: True ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
}
,
executionInfo:
{
Required: False ,
}
{
nextRunTime:
{
Description: This property is meaningful only if the schedule is in the active state when the time comes around. For example, if the schedule is disabled, no Job will be created at nextRunTime unless the Job is enabled before then. ,
Format: date-time ,
Required: False ,
}
string ,
recentJob:
{
Description: This property is present only if the at least one Job has run under the schedule. ,
Required: False ,
}
{
id:
{
Required: False ,
}
string ,
url:
{
Required: False ,
}
string ,
}
,
endTime:
{
Description: This property is set only if the Job Schedule is in the completed state. ,
Format: date-time ,
Required: False ,
}
string ,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
stats:
{
Required: False ,
}
{
url:
{
Required: True ,
}
string ,
startTime:
{
Format: date-time ,
Required: True ,
}
string ,
lastUpdateTime:
{
Format: date-time ,
Required: True ,
}
string ,
userCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
kernelCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
wallClockTime:
{
Description: The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. ,
Format: duration ,
Required: True ,
}
string ,
readIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
writeIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
readIOGiB:
{
Format: double ,
Required: True ,
}
number ,
writeIOGiB:
{
Format: double ,
Required: True ,
}
number ,
numSucceededTasks:
{
Format: int64 ,
Required: True ,
}
integer ,
numFailedTasks:
{
Format: int64 ,
Required: True ,
}
integer ,
numTaskRetries:
{
Format: int64 ,
Required: True ,
}
integer ,
waitTime:
{
Description: This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. ,
Format: duration ,
Required: True ,
}
string ,
}
,
}
,
]
,
odata.nextLink:
{
Required: False ,
}
string ,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
Job_Get (updated)
Description :  Gets information about the specified Job.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Job_Get",
  "$responses": {
    "200": {
      "$properties": {
        "jobManagerTask": [
          {
            "#name": "authenticationTokenSettings",
            "Description": {
              "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
              "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
            }
          }
        ]
      }
    }
  }
}

⚼ Request

GET:  /jobs/{jobId}
{
jobId:
{
Description: The ID of the Job. ,
Required: True ,
}
string ,
$select:
{
Description: An OData $select clause. ,
Required: False ,
}
string ,
$expand:
{
Description: An OData $expand clause. ,
Required: False ,
}
string ,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service exactly matches the value specified by the client. ,
Required: False ,
}
string ,
If-None-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service does not match the value specified by the client. ,
Required: False ,
}
string ,
If-Modified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Unmodified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has not been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
}
,
$schema:
{
id:
{
Description: The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). ,
Required: False ,
}
string ,
displayName:
{
Required: False ,
}
string ,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
url:
{
Required: False ,
}
string ,
eTag:
{
Description: This is an opaque string. You can use it to detect whether the Job has changed between requests. In particular, you can be pass the ETag when updating a Job to specify that your changes should take effect only if nobody else has modified the Job in the meantime. ,
Required: False ,
}
string ,
lastModified:
{
Description: This is the last time at which the Job level data, such as the Job state or priority, changed. It does not factor in task-level changes such as adding new Tasks or Tasks changing state. ,
Format: date-time ,
Required: False ,
}
string ,
creationTime:
{
Format: date-time ,
Required: False ,
}
string ,
state:
{
Enum:
{
active: The Job is available to have Tasks scheduled. ,
disabling: A user has requested that the Job be disabled, but the disable operation is still in progress (for example, waiting for Tasks to terminate). ,
disabled: A user has disabled the Job. No Tasks are running, and no new Tasks will be scheduled. ,
enabling: A user has requested that the Job be enabled, but the enable operation is still in progress. ,
terminating: The Job is about to complete, either because a Job Manager Task has completed or because the user has terminated the Job, but the terminate operation is still in progress (for example, because Job Release Tasks are running). ,
completed: All Tasks have terminated, and the system will not accept any more Tasks or any further changes to the Job. ,
deleting: A user has requested that the Job be deleted, but the delete operation is still in progress (for example, because the system is still terminating running Tasks). ,
}
,
Required: False ,
}
enum ,
stateTransitionTime:
{
Format: date-time ,
Required: False ,
}
string ,
previousState:
{
Description: This property is not set if the Job is in its initial Active state. ,
Enum:
{
active: The Job is available to have Tasks scheduled. ,
disabling: A user has requested that the Job be disabled, but the disable operation is still in progress (for example, waiting for Tasks to terminate). ,
disabled: A user has disabled the Job. No Tasks are running, and no new Tasks will be scheduled. ,
enabling: A user has requested that the Job be enabled, but the enable operation is still in progress. ,
terminating: The Job is about to complete, either because a Job Manager Task has completed or because the user has terminated the Job, but the terminate operation is still in progress (for example, because Job Release Tasks are running). ,
completed: All Tasks have terminated, and the system will not accept any more Tasks or any further changes to the Job. ,
deleting: A user has requested that the Job be deleted, but the delete operation is still in progress (for example, because the system is still terminating running Tasks). ,
}
,
Required: False ,
}
enum ,
previousStateTransitionTime:
{
Description: This property is not set if the Job is in its initial Active state. ,
Format: date-time ,
Required: False ,
}
string ,
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: The Job Manager Task is automatically started when the Job is created. The Batch service tries to schedule the Job Manager Task before any other Tasks in the Job. When shrinking a Pool, the Batch service tries to preserve Nodes where Job Manager Tasks are running for as long as possible (that is, Compute Nodes running 'normal' Tasks are removed before Compute Nodes running Job Manager Tasks). When a Job Manager Task fails and needs to be restarted, the system tries to schedule it at the highest priority. If there are no idle Compute Nodes available, the system may terminate one of the running Tasks in the Pool and return it to the queue in order to make room for the Job Manager Task to restart. Note that a Job Manager Task in one Job does not have priority over Tasks in other Jobs. Across Jobs, only Job level priorities are observed. For example, if a Job Manager in a priority 0 Job needs to be restarted, it will not displace Tasks of a priority 1 Job. Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: The Job Preparation Task is a special Task run on each Compute Node before any other Task of the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: The Job Release Task is a special Task run at the end of the Job on each Compute Node that has run any other Task of the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: False ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
onAllTasksComplete:
{
Description: The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: A Task is considered to have failed if has a failureInfo. A failureInfo is set if the Task completes with a non-zero exit code after exhausting its retry count, or if there was an error starting the Task, for example due to a resource file download error. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
executionInfo:
{
Required: False ,
}
{
startTime:
{
Description: This is the time at which the Job was created. ,
Format: date-time ,
Required: True ,
}
string ,
endTime:
{
Description: This property is set only if the Job is in the completed state. ,
Format: date-time ,
Required: False ,
}
string ,
poolId:
{
Description: This element contains the actual Pool where the Job is assigned. When you get Job details from the service, they also contain a poolInfo element, which contains the Pool configuration data from when the Job was added or updated. That poolInfo element may also contain a poolId element. If it does, the two IDs are the same. If it does not, it means the Job ran on an auto Pool, and this property contains the ID of that auto Pool. ,
Required: False ,
}
string ,
schedulingError:
{
Description: This property is not set if there was no error starting the Job. ,
Required: False ,
}
{
category:
{
Enum:
{
usererror: The error is due to a user issue, such as misconfiguration. ,
servererror: The error is due to an internal server issue. ,
}
,
Required: True ,
}
enum ,
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
string ,
details:
{
Required: False ,
}
[
{
name:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
terminateReason:
{
Description: This property is set only if the Job is in the completed state. If the Batch service terminates the Job, it sets the reason as follows: JMComplete - the Job Manager Task completed, and killJobOnCompletion was set to true. MaxWallClockTimeExpiry - the Job reached its maxWallClockTime constraint. TerminateJobSchedule - the Job ran as part of a schedule, and the schedule terminated. AllTasksComplete - the Job's onAllTasksComplete attribute is set to terminatejob, and all Tasks in the Job are complete. TaskFailed - the Job's onTaskFailure attribute is set to performExitOptionsJobAction, and a Task in the Job failed with an exit condition that specified a jobAction of terminatejob. Any other string is a user-defined reason specified in a call to the 'Terminate a Job' operation. ,
Required: False ,
}
string ,
}
,
stats:
{
Description: This property is populated only if the CloudJob was retrieved with an expand clause including the 'stats' attribute; otherwise it is null. The statistics may not be immediately available. The Batch service performs periodic roll-up of statistics. The typical delay is about 30 minutes. ,
Required: False ,
}
{
url:
{
Required: True ,
}
string ,
startTime:
{
Format: date-time ,
Required: True ,
}
string ,
lastUpdateTime:
{
Format: date-time ,
Required: True ,
}
string ,
userCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
kernelCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
wallClockTime:
{
Description: The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. ,
Format: duration ,
Required: True ,
}
string ,
readIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
writeIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
readIOGiB:
{
Format: double ,
Required: True ,
}
number ,
writeIOGiB:
{
Format: double ,
Required: True ,
}
number ,
numSucceededTasks:
{
Description: A Task completes successfully if it returns exit code 0. ,
Format: int64 ,
Required: True ,
}
integer ,
numFailedTasks:
{
Description: A Task fails if it exhausts its maximum retry count without returning exit code 0. ,
Format: int64 ,
Required: True ,
}
integer ,
numTaskRetries:
{
Format: int64 ,
Required: True ,
}
integer ,
waitTime:
{
Description: The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.) This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. ,
Format: duration ,
Required: True ,
}
string ,
}
,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
Job_Add (updated)
Description :  The Batch service supports two ways to control the work done as part of a Job. In the first approach, the user specifies a Job Manager Task. The Batch service launches this Task when it is ready to start the Job. The Job Manager Task controls all other Tasks that run under this Job, by using the Task APIs. In the second approach, the user directly controls the execution of Tasks under an active Job, by using the Task APIs. Also note: when naming Jobs, avoid including sensitive information such as user names or secret project names. This information may appear in telemetry logs accessible to Microsoft Support engineers.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Job_Add",
  "$parameters": {
    "job": {
      "$properties": {
        "jobManagerTask": [
          {
            "#name": "authenticationTokenSettings",
            "Description": {
              "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
              "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
            }
          }
        ]
      }
    }
  }
}

⚼ Request

POST:  /jobs
{
job:
{
Description: The Job to be added. ,
Required: True ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). ,
Required: True ,
}
string ,
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. ,
Format: int32 ,
Required: False ,
}
integer ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
constraints:
{
Description: The execution constraints for the Job. ,
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: If the Job does not specify a Job Manager Task, the user must explicitly add Tasks to the Job. If the Job does specify a Job Manager Task, the Batch service creates the Job Manager Task when the Job is created, and will try to schedule the Job Manager Task before scheduling other Tasks in the Job. The Job Manager Task's typical purpose is to control and/or monitor Job execution, for example by deciding what additional Tasks to run, determining when the work is complete, etc. (However, a Job Manager Task is not restricted to these activities - it is a fully-fledged Task in the system and perform whatever actions are required for the Job.) For example, a Job Manager Task might download a file specified as a parameter, analyze the contents of that file and submit additional Tasks based on those contents. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: If a Job has a Job Preparation Task, the Batch service will run the Job Preparation Task on a Node before starting any Tasks of that Job on that Compute Node. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: A Job Release Task cannot be specified without also specifying a Job Preparation Task for the Job. The Batch service runs the Job Release Task on the Nodes that have run the Job Preparation Task. The primary purpose of the Job Release Task is to undo changes to Compute Nodes made by the Job Preparation Task. Example activities include deleting local files, or shutting down services that were started as part of Job preparation. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: True ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
onAllTasksComplete:
{
Description: Note that if a Job contains no Tasks, then all Tasks are considered complete. This option is therefore most commonly used with a Job Manager task; if you want to use automatic Job termination without a Job Manager, you should initially set onAllTasksComplete to noaction and update the Job properties to set onAllTasksComplete to terminatejob once you have finished adding Tasks. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: A Task is considered to have failed if has a failureInfo. A failureInfo is set if the Task completes with a non-zero exit code after exhausting its retry count, or if there was an error starting the Task, for example due to a resource file download error. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
}
,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (201)

{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
dataserviceid:
{
Description: The OData ID of the resource to which the request applied. ,
}
string ,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
Job_List (updated)
Description :  Lists all of the Jobs in the specified Account.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Job_List",
  "$responses": {
    "200": {
      "$properties": {
        "value": {
          "$properties": {
            "jobManagerTask": [
              {
                "#name": "authenticationTokenSettings",
                "Description": {
                  "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                  "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
                }
              }
            ]
          }
        }
      }
    }
  }
}

⚼ Request

GET:  /jobs
{
$filter:
{
Description: An OData $filter clause. For more information on constructing this filter, see https://learn.microsoft.com/rest/api/batchservice/odata-filters-in-batch#list-jobs. ,
Required: False ,
}
string ,
$select:
{
Description: An OData $select clause. ,
Required: False ,
}
string ,
$expand:
{
Description: An OData $expand clause. ,
Required: False ,
}
string ,
maxresults:
{
Description: The maximum number of items to return in the response. A maximum of 1000 Jobs can be returned. ,
Format: int32 ,
Required: False ,
}
integer ,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
}
,
$schema:
{
value:
{
Required: False ,
}
[
{
id:
{
Description: The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). ,
Required: False ,
}
string ,
displayName:
{
Required: False ,
}
string ,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
url:
{
Required: False ,
}
string ,
eTag:
{
Description: This is an opaque string. You can use it to detect whether the Job has changed between requests. In particular, you can be pass the ETag when updating a Job to specify that your changes should take effect only if nobody else has modified the Job in the meantime. ,
Required: False ,
}
string ,
lastModified:
{
Description: This is the last time at which the Job level data, such as the Job state or priority, changed. It does not factor in task-level changes such as adding new Tasks or Tasks changing state. ,
Format: date-time ,
Required: False ,
}
string ,
creationTime:
{
Format: date-time ,
Required: False ,
}
string ,
state:
{
Enum:
{
active: The Job is available to have Tasks scheduled. ,
disabling: A user has requested that the Job be disabled, but the disable operation is still in progress (for example, waiting for Tasks to terminate). ,
disabled: A user has disabled the Job. No Tasks are running, and no new Tasks will be scheduled. ,
enabling: A user has requested that the Job be enabled, but the enable operation is still in progress. ,
terminating: The Job is about to complete, either because a Job Manager Task has completed or because the user has terminated the Job, but the terminate operation is still in progress (for example, because Job Release Tasks are running). ,
completed: All Tasks have terminated, and the system will not accept any more Tasks or any further changes to the Job. ,
deleting: A user has requested that the Job be deleted, but the delete operation is still in progress (for example, because the system is still terminating running Tasks). ,
}
,
Required: False ,
}
enum ,
stateTransitionTime:
{
Format: date-time ,
Required: False ,
}
string ,
previousState:
{
Description: This property is not set if the Job is in its initial Active state. ,
Enum:
{
active: The Job is available to have Tasks scheduled. ,
disabling: A user has requested that the Job be disabled, but the disable operation is still in progress (for example, waiting for Tasks to terminate). ,
disabled: A user has disabled the Job. No Tasks are running, and no new Tasks will be scheduled. ,
enabling: A user has requested that the Job be enabled, but the enable operation is still in progress. ,
terminating: The Job is about to complete, either because a Job Manager Task has completed or because the user has terminated the Job, but the terminate operation is still in progress (for example, because Job Release Tasks are running). ,
completed: All Tasks have terminated, and the system will not accept any more Tasks or any further changes to the Job. ,
deleting: A user has requested that the Job be deleted, but the delete operation is still in progress (for example, because the system is still terminating running Tasks). ,
}
,
Required: False ,
}
enum ,
previousStateTransitionTime:
{
Description: This property is not set if the Job is in its initial Active state. ,
Format: date-time ,
Required: False ,
}
string ,
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: The Job Manager Task is automatically started when the Job is created. The Batch service tries to schedule the Job Manager Task before any other Tasks in the Job. When shrinking a Pool, the Batch service tries to preserve Nodes where Job Manager Tasks are running for as long as possible (that is, Compute Nodes running 'normal' Tasks are removed before Compute Nodes running Job Manager Tasks). When a Job Manager Task fails and needs to be restarted, the system tries to schedule it at the highest priority. If there are no idle Compute Nodes available, the system may terminate one of the running Tasks in the Pool and return it to the queue in order to make room for the Job Manager Task to restart. Note that a Job Manager Task in one Job does not have priority over Tasks in other Jobs. Across Jobs, only Job level priorities are observed. For example, if a Job Manager in a priority 0 Job needs to be restarted, it will not displace Tasks of a priority 1 Job. Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: The Job Preparation Task is a special Task run on each Compute Node before any other Task of the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: The Job Release Task is a special Task run at the end of the Job on each Compute Node that has run any other Task of the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: False ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
onAllTasksComplete:
{
Description: The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: A Task is considered to have failed if has a failureInfo. A failureInfo is set if the Task completes with a non-zero exit code after exhausting its retry count, or if there was an error starting the Task, for example due to a resource file download error. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
executionInfo:
{
Required: False ,
}
{
startTime:
{
Description: This is the time at which the Job was created. ,
Format: date-time ,
Required: True ,
}
string ,
endTime:
{
Description: This property is set only if the Job is in the completed state. ,
Format: date-time ,
Required: False ,
}
string ,
poolId:
{
Description: This element contains the actual Pool where the Job is assigned. When you get Job details from the service, they also contain a poolInfo element, which contains the Pool configuration data from when the Job was added or updated. That poolInfo element may also contain a poolId element. If it does, the two IDs are the same. If it does not, it means the Job ran on an auto Pool, and this property contains the ID of that auto Pool. ,
Required: False ,
}
string ,
schedulingError:
{
Description: This property is not set if there was no error starting the Job. ,
Required: False ,
}
{
category:
{
Enum:
{
usererror: The error is due to a user issue, such as misconfiguration. ,
servererror: The error is due to an internal server issue. ,
}
,
Required: True ,
}
enum ,
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
string ,
details:
{
Required: False ,
}
[
{
name:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
terminateReason:
{
Description: This property is set only if the Job is in the completed state. If the Batch service terminates the Job, it sets the reason as follows: JMComplete - the Job Manager Task completed, and killJobOnCompletion was set to true. MaxWallClockTimeExpiry - the Job reached its maxWallClockTime constraint. TerminateJobSchedule - the Job ran as part of a schedule, and the schedule terminated. AllTasksComplete - the Job's onAllTasksComplete attribute is set to terminatejob, and all Tasks in the Job are complete. TaskFailed - the Job's onTaskFailure attribute is set to performExitOptionsJobAction, and a Task in the Job failed with an exit condition that specified a jobAction of terminatejob. Any other string is a user-defined reason specified in a call to the 'Terminate a Job' operation. ,
Required: False ,
}
string ,
}
,
stats:
{
Description: This property is populated only if the CloudJob was retrieved with an expand clause including the 'stats' attribute; otherwise it is null. The statistics may not be immediately available. The Batch service performs periodic roll-up of statistics. The typical delay is about 30 minutes. ,
Required: False ,
}
{
url:
{
Required: True ,
}
string ,
startTime:
{
Format: date-time ,
Required: True ,
}
string ,
lastUpdateTime:
{
Format: date-time ,
Required: True ,
}
string ,
userCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
kernelCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
wallClockTime:
{
Description: The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. ,
Format: duration ,
Required: True ,
}
string ,
readIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
writeIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
readIOGiB:
{
Format: double ,
Required: True ,
}
number ,
writeIOGiB:
{
Format: double ,
Required: True ,
}
number ,
numSucceededTasks:
{
Description: A Task completes successfully if it returns exit code 0. ,
Format: int64 ,
Required: True ,
}
integer ,
numFailedTasks:
{
Description: A Task fails if it exhausts its maximum retry count without returning exit code 0. ,
Format: int64 ,
Required: True ,
}
integer ,
numTaskRetries:
{
Format: int64 ,
Required: True ,
}
integer ,
waitTime:
{
Description: The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.) This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. ,
Format: duration ,
Required: True ,
}
string ,
}
,
}
,
]
,
odata.nextLink:
{
Required: False ,
}
string ,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
Job_ListFromJobSchedule (updated)
Description :  Lists the Jobs that have been created under the specified Job Schedule.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Job_ListFromJobSchedule",
  "$responses": {
    "200": {
      "$properties": {
        "value": {
          "$properties": {
            "jobManagerTask": [
              {
                "#name": "authenticationTokenSettings",
                "Description": {
                  "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                  "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
                }
              }
            ]
          }
        }
      }
    }
  }
}

⚼ Request

GET:  /jobschedules/{jobScheduleId}/jobs
{
jobScheduleId:
{
Description: The ID of the Job Schedule from which you want to get a list of Jobs. ,
Required: True ,
}
string ,
$filter:
{
Description: An OData $filter clause. For more information on constructing this filter, see https://learn.microsoft.com/rest/api/batchservice/odata-filters-in-batch#list-jobs-in-a-job-schedule. ,
Required: False ,
}
string ,
$select:
{
Description: An OData $select clause. ,
Required: False ,
}
string ,
$expand:
{
Description: An OData $expand clause. ,
Required: False ,
}
string ,
maxresults:
{
Description: The maximum number of items to return in the response. A maximum of 1000 Jobs can be returned. ,
Format: int32 ,
Required: False ,
}
integer ,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
}
,
$schema:
{
value:
{
Required: False ,
}
[
{
id:
{
Description: The ID is case-preserving and case-insensitive (that is, you may not have two IDs within an Account that differ only by case). ,
Required: False ,
}
string ,
displayName:
{
Required: False ,
}
string ,
usesTaskDependencies:
{
Required: False ,
}
boolean ,
url:
{
Required: False ,
}
string ,
eTag:
{
Description: This is an opaque string. You can use it to detect whether the Job has changed between requests. In particular, you can be pass the ETag when updating a Job to specify that your changes should take effect only if nobody else has modified the Job in the meantime. ,
Required: False ,
}
string ,
lastModified:
{
Description: This is the last time at which the Job level data, such as the Job state or priority, changed. It does not factor in task-level changes such as adding new Tasks or Tasks changing state. ,
Format: date-time ,
Required: False ,
}
string ,
creationTime:
{
Format: date-time ,
Required: False ,
}
string ,
state:
{
Enum:
{
active: The Job is available to have Tasks scheduled. ,
disabling: A user has requested that the Job be disabled, but the disable operation is still in progress (for example, waiting for Tasks to terminate). ,
disabled: A user has disabled the Job. No Tasks are running, and no new Tasks will be scheduled. ,
enabling: A user has requested that the Job be enabled, but the enable operation is still in progress. ,
terminating: The Job is about to complete, either because a Job Manager Task has completed or because the user has terminated the Job, but the terminate operation is still in progress (for example, because Job Release Tasks are running). ,
completed: All Tasks have terminated, and the system will not accept any more Tasks or any further changes to the Job. ,
deleting: A user has requested that the Job be deleted, but the delete operation is still in progress (for example, because the system is still terminating running Tasks). ,
}
,
Required: False ,
}
enum ,
stateTransitionTime:
{
Format: date-time ,
Required: False ,
}
string ,
previousState:
{
Description: This property is not set if the Job is in its initial Active state. ,
Enum:
{
active: The Job is available to have Tasks scheduled. ,
disabling: A user has requested that the Job be disabled, but the disable operation is still in progress (for example, waiting for Tasks to terminate). ,
disabled: A user has disabled the Job. No Tasks are running, and no new Tasks will be scheduled. ,
enabling: A user has requested that the Job be enabled, but the enable operation is still in progress. ,
terminating: The Job is about to complete, either because a Job Manager Task has completed or because the user has terminated the Job, but the terminate operation is still in progress (for example, because Job Release Tasks are running). ,
completed: All Tasks have terminated, and the system will not accept any more Tasks or any further changes to the Job. ,
deleting: A user has requested that the Job be deleted, but the delete operation is still in progress (for example, because the system is still terminating running Tasks). ,
}
,
Required: False ,
}
enum ,
previousStateTransitionTime:
{
Description: This property is not set if the Job is in its initial Active state. ,
Format: date-time ,
Required: False ,
}
string ,
priority:
{
Description: Priority values can range from -1000 to 1000, with -1000 being the lowest priority and 1000 being the highest priority. The default value is 0. ,
Format: int32 ,
Required: False ,
}
integer ,
allowTaskPreemption:
{
Description: If the value is set to True, other high priority jobs submitted to the system will take precedence and will be able requeue tasks from this job. You can update a job's allowTaskPreemption after it has been created using the update job API. ,
Required: False ,
}
boolean ,
maxParallelTasks:
{
Description: The value of maxParallelTasks must be -1 or greater than 0 if specified. If not specified, the default value is -1, which means there's no limit to the number of tasks that can be run at once. You can update a job's maxParallelTasks after it has been created using the update job API. ,
Format: int32 ,
Required: False ,
}
integer ,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If the Job does not complete within the time limit, the Batch service terminates it and any Tasks that are still running. In this case, the termination reason will be MaxWallClockTimeExpiry. If this property is not specified, there is no time limit on how long the Job may run. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries. The Batch service will try each Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries a Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry Tasks. If the maximum retry count is -1, the Batch service retries Tasks without limit. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
jobManagerTask:
{
Description: The Job Manager Task is automatically started when the Job is created. The Batch service tries to schedule the Job Manager Task before any other Tasks in the Job. When shrinking a Pool, the Batch service tries to preserve Nodes where Job Manager Tasks are running for as long as possible (that is, Compute Nodes running 'normal' Tasks are removed before Compute Nodes running Job Manager Tasks). When a Job Manager Task fails and needs to be restarted, the system tries to schedule it at the highest priority. If there are no idle Compute Nodes available, the system may terminate one of the running Tasks in the Pool and return it to the queue in order to make room for the Job Manager Task to restart. Note that a Job Manager Task in one Job does not have priority over Tasks in other Jobs. Across Jobs, only Job level priorities are observed. For example, if a Job Manager in a priority 0 Job needs to be restarted, it will not displace Tasks of a priority 1 Job. Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. ,
Required: True ,
}
string ,
displayName:
{
Description: It need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this property is not supported and must not be specified. ,
Format: int32 ,
Required: False ,
}
integer ,
killJobOnCompletion:
{
Description: If true, when the Job Manager Task completes, the Batch service marks the Job as complete. If any Tasks are still running at this time (other than Job Release), those Tasks are terminated. If false, the completion of the Job Manager Task does not affect the Job status. In this case, you should either use the onAllTasksComplete attribute to terminate the Job, or have a client or user terminate the Job explicitly. An example of this is if the Job Manager creates a set of Tasks but then takes no further role in their execution. The default value is true. If you are using the onAllTasksComplete and onTaskFailure attributes to control Job lifetime, and using the Job Manager Task only to create the Tasks for the Job (not to monitor progress), then it is important to set killJobOnCompletion to false. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
runExclusive:
{
Description: If true, no other Tasks will run on the same Node for as long as the Job Manager is running. If false, other Tasks can run simultaneously with the Job Manager on a Compute Node. The Job Manager Task counts normally against the Compute Node's concurrent Task limit, so this is only relevant if the Compute Node allows multiple concurrent Tasks. The default value is true. ,
Required: False ,
}
boolean ,
applicationPackageReferences:
{
Description: Application Packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced Application Package is already on the Compute Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Application Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
allowLowPriorityNode:
{
Description: The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobPreparationTask:
{
Description: The Job Preparation Task is a special Task run on each Compute Node before any other Task of the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobpreparation'. No other Task in the Job can have the same ID as the Job Preparation Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobPreparationTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
waitForSuccess:
{
Description: If true and the Job Preparation Task fails on a Node, the Batch service retries the Job Preparation Task up to its maximum retry count (as specified in the constraints element). If the Task has still not completed successfully after all retries, then the Batch service will not schedule Tasks of the Job to the Node. The Node remains active and eligible to run Tasks of other Jobs. If false, the Batch service will not wait for the Job Preparation Task to complete. In this case, other Tasks of the Job can start executing on the Compute Node while the Job Preparation Task is still running; and even if the Job Preparation Task fails, new Tasks will continue to be scheduled on the Compute Node. The default value is true. ,
Required: False ,
}
boolean ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task on Windows Compute Nodes, or a non-administrative user unique to the Pool on Linux Compute Nodes. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
rerunOnNodeRebootAfterSuccess:
{
Description: The Job Preparation Task is always rerun if a Compute Node is reimaged, or if the Job Preparation Task did not complete (e.g. because the reboot occurred while the Task was running). Therefore, you should always write a Job Preparation Task to be idempotent and to behave correctly if run multiple times. The default value is true. ,
Required: False ,
}
boolean ,
}
,
jobReleaseTask:
{
Description: The Job Release Task is a special Task run at the end of the Job on each Compute Node that has run any other Task of the Job. ,
Required: False ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores and cannot contain more than 64 characters. If you do not specify this property, the Batch service assigns a default value of 'jobrelease'. No other Task in the Job can have the same ID as the Job Release Task. If you try to submit a Task with the same id, the Batch service rejects the request with error code TaskIdSameAsJobReleaseTask; if you are calling the REST API directly, the HTTP status code is 409 (Conflict). ,
Required: False ,
}
string ,
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
maxWallClockTime:
{
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
}
,
commonEnvironmentSettings:
{
Description: Individual Tasks can override an environment setting specified here by specifying the same setting name with a different value. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
poolInfo:
{
Required: False ,
}
{
poolId:
{
Description: You must ensure that the Pool referenced by this property exists. If the Pool does not exist at the time the Batch service tries to schedule a Job, no Tasks for the Job will run until you create a Pool with that id. Note that the Batch service will not reject the Job request; it will simply not run Tasks until the Pool exists. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
string ,
autoPoolSpecification:
{
Description: If auto Pool creation fails, the Batch service moves the Job to a completed state, and the Pool creation error is set in the Job's scheduling error property. The Batch service manages the lifetime (both creation and, unless keepAlive is specified, deletion) of the auto Pool. Any user actions that affect the lifetime of the auto Pool while the Job is active will result in unexpected behavior. You must specify either the Pool ID or the auto Pool specification, but not both. ,
Required: False ,
}
{
autoPoolIdPrefix:
{
Description: The Batch service assigns each auto Pool a unique identifier on creation. To distinguish between Pools created for different purposes, you can specify this element to add a prefix to the ID that is assigned. The prefix can be up to 20 characters long. ,
Required: False ,
}
string ,
poolLifetimeOption:
{
Enum:
{
jobschedule: The Pool exists for the lifetime of the Job Schedule. The Batch Service creates the Pool when it creates the first Job on the schedule. You may apply this option only to Job Schedules, not to Jobs. ,
job: The Pool exists for the lifetime of the Job to which it is dedicated. The Batch service creates the Pool when it creates the Job. If the 'job' option is applied to a Job Schedule, the Batch service creates a new auto Pool for every Job created on the schedule. ,
}
,
Required: True ,
}
enum ,
keepAlive:
{
Description: If false, the Batch service deletes the Pool once its lifetime (as determined by the poolLifetimeOption setting) expires; that is, when the Job or Job Schedule completes. If true, the Batch service does not delete the Pool automatically. It is up to the user to delete auto Pools created with this option. ,
Required: False ,
}
boolean ,
pool:
{
Required: False ,
}
{
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
vmSize:
{
Description: For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://learn.microsoft.com/azure/batch/batch-pool-vm-sizes). ,
Required: True ,
}
string ,
virtualMachineConfiguration:
{
Description: This property must be specified. ,
Required: False ,
}
{
imageReference:
{
Required: True ,
}
{
publisher:
{
Description: For example, Canonical or MicrosoftWindowsServer. ,
Required: False ,
}
string ,
offer:
{
Description: For example, UbuntuServer or WindowsServer. ,
Required: False ,
}
string ,
sku:
{
Description: For example, 18.04-LTS or 2019-Datacenter. ,
Required: False ,
}
string ,
version:
{
Description: A value of 'latest' can be specified to select the latest version of an Image. If omitted, the default is 'latest'. ,
Required: False ,
}
string ,
virtualMachineImageId:
{
Description: This property is mutually exclusive with other ImageReference properties. The Azure Compute Gallery Image must have replicas in the same region and must be in the same subscription as the Azure Batch account. If the image version is not specified in the imageId, the latest version will be used. For information about the firewall settings for the Batch Compute Node agent to communicate with the Batch service see https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration. ,
Required: False ,
}
string ,
exactVersion:
{
Description: The specific version of the platform image or marketplace image used to create the node. This read-only field differs from 'version' only if the value specified for 'version' when the pool was created was 'latest'. ,
Required: False ,
}
string ,
sharedGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. ,
Required: False ,
}
string ,
communityGalleryImageId:
{
Description: This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. ,
Required: False ,
}
string ,
}
,
nodeAgentSKUId:
{
Description: The Batch Compute Node agent is a program that runs on each Compute Node in the Pool, and provides the command-and-control interface between the Compute Node and the Batch service. There are different implementations of the Compute Node agent, known as SKUs, for different operating systems. You must specify a Compute Node agent SKU which matches the selected Image reference. To get the list of supported Compute Node agent SKUs along with their list of verified Image references, see the 'List supported Compute Node agent SKUs' operation. ,
Required: True ,
}
string ,
windowsConfiguration:
{
Description: This property must not be specified if the imageReference property specifies a Linux OS Image. ,
Required: False ,
}
{
enableAutomaticUpdates:
{
Description: If omitted, the default value is true. ,
Required: False ,
}
boolean ,
}
,
dataDisks:
{
Description: This property must be specified if the Compute Nodes in the Pool need to have empty data disks attached to them. This cannot be updated. Each Compute Node gets its own disk (the disk is not a file share). Existing disks cannot be attached, each attached disk is empty. When the Compute Node is removed from the Pool, the disk and all data associated with it is also deleted. The disk is not formatted after being attached, it must be formatted before use - for more information see https://learn.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://learn.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. ,
Required: False ,
}
[
{
lun:
{
Description: The lun is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct lun. The value must be between 0 and 63, inclusive. ,
Format: int32 ,
Required: True ,
}
integer ,
caching:
{
Description: The default value for caching is readwrite. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
diskSizeGB:
{
Format: int32 ,
Required: True ,
}
integer ,
storageAccountType:
{
Description: If omitted, the default is "standard_lrs". ,
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
}
,
]
,
licenseType:
{
Description: This only applies to Images that contain the Windows operating system, and should only be used when you hold valid on-premises licenses for the Compute Nodes which will be deployed. If omitted, no on-premises licensing discount is applied. Values are: Windows_Server - The on-premises license is for Windows Server. Windows_Client - The on-premises license is for Windows Client. ,
Required: False ,
}
string ,
containerConfiguration:
{
Description: If specified, setup is performed on each Compute Node in the Pool to allow Tasks to run in containers. All regular Tasks and Job manager Tasks run on this Pool must specify the containerSettings property, and all other Tasks may specify it. ,
Required: False ,
}
{
type:
{
Enum:
{
dockerCompatible: A Docker compatible container technology will be used to launch the containers. ,
criCompatible: A CRI based technology will be used to launch the containers. ,
}
,
Required: True ,
}
enum ,
containerImageNames:
{
Description: This is the full Image reference, as would be specified to "docker pull". An Image will be sourced from the default Docker registry unless the Image is fully qualified with an alternative registry. ,
Required: False ,
}
[
string ,
]
,
containerRegistries:
{
Description: If any Images must be downloaded from a private registry which requires credentials, then those credentials must be provided here. ,
Required: False ,
}
[
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
diskEncryptionConfiguration:
{
Description: If specified, encryption is performed on each node in the pool during node provisioning. ,
Required: False ,
}
{
targets:
{
Description: The list of disk targets Batch Service will encrypt on the compute node. ,
Required: False ,
}
[
string ,
]
,
}
,
nodePlacementConfiguration:
{
Description: This configuration will specify rules on how nodes in the pool will be physically allocated. ,
Required: False ,
}
{
policy:
{
Description: Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. ,
Enum:
{
regional: All nodes in the pool will be allocated in the same region. ,
zonal: Nodes in the pool will be spread across different availability zones with best effort balancing. ,
}
,
Required: False ,
}
enum ,
}
,
extensions:
{
Description: If specified, the extensions mentioned in this configuration will be installed on each node. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
publisher:
{
Required: True ,
}
string ,
type:
{
Required: True ,
}
string ,
typeHandlerVersion:
{
Required: False ,
}
string ,
autoUpgradeMinorVersion:
{
Description: Indicates whether the extension should use a newer minor version if one is available at deployment time. Once deployed, however, the extension will not upgrade minor versions unless redeployed, even with this property set to true. ,
Required: False ,
}
boolean ,
enableAutomaticUpgrade:
{
Description: Indicates whether the extension should be automatically upgraded by the platform if there is a newer version of the extension available. ,
Required: False ,
}
boolean ,
settings:
{
Required: False ,
}
object ,
protectedSettings:
{
Description: The extension can contain either protectedSettings or protectedSettingsFromKeyVault or no protected settings at all. ,
Required: False ,
}
object ,
provisionAfterExtensions:
{
Description: Collection of extension names after which this extension needs to be provisioned. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
osDisk:
{
Required: False ,
}
{
ephemeralOSDiskSettings:
{
Required: False ,
}
{
placement:
{
Description: This property can be used by user in the request to choose the location e.g., cache disk space for Ephemeral OS disk provisioning. For more information on Ephemeral OS disk size requirements, please refer to Ephemeral OS disk size requirements for Windows VMs at https://learn.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://learn.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. ,
Enum:
{
CacheDisk: The Ephemeral OS Disk is stored on the VM cache. ,
}
,
Required: False ,
}
enum ,
}
,
caching:
{
Description: The default value for caching is none. For information about the caching options see: https://blogs.msdn.microsoft.com/windowsazurestorage/2012/06/27/exploring-windows-azure-drives-disks-and-images/. ,
Enum:
{
none: The caching mode for the disk is not enabled. ,
readonly: The caching mode for the disk is read only. ,
readwrite: The caching mode for the disk is read and write. ,
}
,
Required: False ,
}
enum ,
managedDisk:
{
Required: False ,
}
{
storageAccountType:
{
Enum:
{
standard_lrs: The data disk / OS disk should use standard locally redundant storage. ,
premium_lrs: The data disk / OS disk should use premium locally redundant storage. ,
standardssd_lrs: The data disk / OS disk should use standard SSD locally redundant storage. ,
}
,
Required: False ,
}
enum ,
securityProfile:
{
Description: Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. ,
Required: False ,
}
{
securityEncryptionType:
{
Enum:
{
NonPersistedTPM: No description available. ,
VMGuestStateOnly: No description available. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
diskSizeGB:
{
Format: int32 ,
Required: False ,
}
integer ,
writeAcceleratorEnabled:
{
Required: False ,
}
boolean ,
}
,
securityProfile:
{
Description: Specifies the security profile settings for the virtual machine or virtual machine scale set. ,
Required: False ,
}
{
securityType:
{
Enum:
{
trustedLaunch: Trusted launch protects against advanced and persistent attack techniques. ,
confidentialVM: Azure confidential computing offers confidential VMs are for tenants with high security and confidentiality requirements. These VMs provide a strong, hardware-enforced boundary to help meet your security needs. You can use confidential VMs for migrations without making changes to your code, with the platform protecting your VM's state from being read or modified. ,
}
,
Required: False ,
}
enum ,
encryptionAtHost:
{
Description: This property can be used by user in the request to enable or disable the Host Encryption for the virtual machine or virtual machine scale set. This will enable the encryption for all the disks including Resource/Temp disk at host itself. For more information on encryption at host requirements, please refer to https://learn.microsoft.com/azure/virtual-machines/disk-encryption#supported-vm-sizes. ,
Required: False ,
}
boolean ,
uefiSettings:
{
Description: Specifies the security settings like secure boot and vTPM used while creating the virtual machine. ,
Required: False ,
}
{
secureBootEnabled:
{
Description: Specifies whether secure boot should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
vTpmEnabled:
{
Description: Specifies whether vTPM should be enabled on the virtual machine. ,
Required: False ,
}
boolean ,
}
,
}
,
serviceArtifactReference:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: False ,
}
{
id:
{
Description: The service artifact reference id in the form of /subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Compute/galleries/{galleryName}/serviceArtifacts/{serviceArtifactName}/vmArtifactsProfiles/{vmArtifactsProfilesName} ,
Required: True ,
}
string ,
}
,
}
,
taskSlotsPerNode:
{
Description: The default value is 1. The maximum value is the smaller of 4 times the number of cores of the vmSize of the pool or 256. ,
Format: int32 ,
Required: False ,
}
integer ,
taskSchedulingPolicy:
{
Description: If not specified, the default is spread. ,
Required: False ,
}
{
nodeFillType:
{
Description: If not specified, the default is spread. ,
Enum:
{
spread: Tasks should be assigned evenly across all Compute Nodes in the Pool. ,
pack: As many Tasks as possible (taskSlotsPerNode) should be assigned to each Compute Node in the Pool before any Tasks are assigned to the next Compute Node in the Pool. ,
}
,
Required: True ,
}
enum ,
}
,
resizeTimeout:
{
Description: This timeout applies only to manual scaling; it has no effect when enableAutoScale is set to true. The default value is 15 minutes. The minimum value is 5 minutes. If you specify a value less than 5 minutes, the Batch service rejects the request with an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
targetDedicatedNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
targetLowPriorityNodes:
{
Description: This property must not be specified if enableAutoScale is set to true. If enableAutoScale is set to false, then you must set either targetDedicatedNodes, targetLowPriorityNodes, or both. ,
Format: int32 ,
Required: False ,
}
integer ,
enableAutoScale:
{
Description: If false, at least one of targetDedicatedNodes and targetLowPriorityNodes must be specified. If true, the autoScaleFormula element is required. The Pool automatically resizes according to the formula. The default value is false. ,
Required: False ,
}
boolean ,
autoScaleFormula:
{
Description: This property must not be specified if enableAutoScale is set to false. It is required if enableAutoScale is set to true. The formula is checked for validity before the Pool is created. If the formula is not valid, the Batch service rejects the request with detailed error information. ,
Required: False ,
}
string ,
autoScaleEvaluationInterval:
{
Description: The default value is 15 minutes. The minimum and maximum value are 5 minutes and 168 hours respectively. If you specify a value less than 5 minutes or greater than 168 hours, the Batch service rejects the request with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Format: duration ,
Required: False ,
}
string ,
enableInterNodeCommunication:
{
Description: Enabling inter-node communication limits the maximum size of the Pool due to deployment restrictions on the Compute Nodes of the Pool. This may result in the Pool not reaching its desired size. The default value is false. ,
Required: False ,
}
boolean ,
networkConfiguration:
{
Description: The network configuration for a Pool. ,
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes in the Pool. If the subnet doesn't have enough free IP addresses, the Pool will partially allocate Nodes and a resize error will occur. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet. The specified subnet must allow communication from the Azure Batch service to be able to schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. Only ARM virtual networks ('Microsoft.Network/virtualNetworks') are supported. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication, including ports 29876 and 29877. Also enable outbound connections to Azure Storage on port 443. For more details see: https://learn.microsoft.com/azure/batch/nodes-and-pools#virtual-network-vnet-and-firewall-configuration ,
Required: False ,
}
string ,
dynamicVNetAssignmentScope:
{
Enum:
{
none: No dynamic VNet assignment is enabled. ,
job: Dynamic VNet assignment is done per-job. ,
}
,
Required: False ,
}
enum ,
endpointConfiguration:
{
Required: False ,
}
{
inboundNATPools:
{
Description: The maximum number of inbound NAT Pools per Batch Pool is 5. If the maximum number of inbound NAT Pools is exceeded the request fails with HTTP status code 400. This cannot be specified if the IPAddressProvisioningType is NoPublicIPAddresses. ,
Required: True ,
}
[
{
name:
{
Description: The name must be unique within a Batch Pool, can contain letters, numbers, underscores, periods, and hyphens. Names must start with a letter or number, must end with a letter, number, or underscore, and cannot exceed 77 characters. If any invalid values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
protocol:
{
Enum:
{
tcp: Use TCP for the endpoint. ,
udp: Use UDP for the endpoint. ,
}
,
Required: True ,
}
enum ,
backendPort:
{
Description: This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeStart:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
frontendPortRangeEnd:
{
Description: Acceptable values range between 1 and 65534 except ports from 50000 to 55000 which are reserved by the Batch service. All ranges within a Pool must be distinct and cannot overlap. Each range must contain at least 40 ports. If any reserved or overlapping values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
networkSecurityGroupRules:
{
Description: The maximum number of rules that can be specified across all the endpoints on a Batch Pool is 25. If no network security group rules are specified, a default rule will be created to allow inbound access to the specified backendPort. If the maximum number of network security group rules is exceeded the request fails with HTTP status code 400. ,
Required: False ,
}
[
{
priority:
{
Description: Priorities within a Pool must be unique and are evaluated in order of priority. The lower the number the higher the priority. For example, rules could be specified with order numbers of 150, 250, and 350. The rule with the order number of 150 takes precedence over the rule that has an order of 250. Allowed priorities are 150 to 4096. If any reserved or duplicate values are provided the request fails with HTTP status code 400. ,
Format: int32 ,
Required: True ,
}
integer ,
access:
{
Enum:
{
allow: Allow access. ,
deny: Deny access. ,
}
,
Required: True ,
}
enum ,
sourceAddressPrefix:
{
Description: Valid values are a single IP address (i.e. 10.10.10.10), IP subnet (i.e. 192.168.1.0/24), default tag, or * (for all addresses). If any other values are provided the request fails with HTTP status code 400. ,
Required: True ,
}
string ,
sourcePortRanges:
{
Description: Valid values are '*' (for all ports 0 - 65535), a specific port (i.e. 22), or a port range (i.e. 100-200). The ports must be in the range of 0 to 65535. Each entry in this collection must not overlap any other entry (either a range or an individual port). If any other values are provided the request fails with HTTP status code 400. The default value is '*'. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
}
,
]
,
}
,
publicIPAddressConfiguration:
{
Description: The public IP Address configuration of the networking configuration of a Pool. ,
Required: False ,
}
{
provision:
{
Description: The default value is BatchManaged. ,
Enum:
{
batchmanaged: A public IP will be created and managed by Batch. There may be multiple public IPs depending on the size of the Pool. ,
usermanaged: Public IPs are provided by the user and will be used to provision the Compute Nodes. ,
nopublicipaddresses: No public IP Address will be created. ,
}
,
Required: False ,
}
enum ,
ipAddressIds:
{
Description: The number of IPs specified here limits the maximum size of the Pool - 100 dedicated nodes or 100 Spot/Low-priority nodes can be allocated for each public IP. For example, a pool needing 250 dedicated VMs would need at least 3 public IPs specified. Each element of this collection is of the form: /subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.Network/publicIPAddresses/{ip}. ,
Required: False ,
}
[
string ,
]
,
}
,
enableAcceleratedNetworking:
{
Description: Accelerated networking enables single root I/O virtualization (SR-IOV) to a VM, which may lead to improved networking performance. For more details, see: https://learn.microsoft.com/azure/virtual-network/accelerated-networking-overview. ,
Required: False ,
}
boolean ,
}
,
startTask:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. In some cases the StartTask may be re-run even though the Compute Node was not rebooted. Special care should be taken to avoid StartTasks which create breakaway process or install/launch services from the StartTask working directory, as this will block Batch from being able to re-run the StartTask. ,
Required: False ,
}
{
commandLine:
{
Description: The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: Files listed under this element are located in the Task's working directory. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
maxTaskRetryCount:
{
Description: The Batch service retries a Task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
waitForSuccess:
{
Description: If true and the StartTask fails on a Node, the Batch service retries the StartTask up to its maximum retry count (maxTaskRetryCount). If the Task has still not completed successfully after all retries, then the Batch service marks the Node unusable, and will not schedule Tasks to it. This condition can be detected via the Compute Node state and failure info details. If false, the Batch service will not wait for the StartTask to complete. In this case, other Tasks can start executing on the Compute Node while the StartTask is still running; and even if the StartTask fails, new Tasks will continue to be scheduled on the Compute Node. The default is true. ,
Required: False ,
}
boolean ,
}
,
certificateReferences:
{
Description: For Windows Nodes, the Batch service installs the Certificates to the specified Certificate store and location. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. Warning: This property is deprecated and will be removed after February, 2024. Please use the [Azure KeyVault Extension](https://learn.microsoft.com/azure/batch/batch-certificate-migration-guide) instead. ,
Required: False ,
}
[
{
thumbprint:
{
Required: True ,
}
string ,
thumbprintAlgorithm:
{
Required: True ,
}
string ,
storeLocation:
{
Description: The default value is currentuser. This property is applicable only for Pools configured with Windows Compute Nodes. For Linux Compute Nodes, the Certificates are stored in a directory inside the Task working directory and an environment variable AZ_BATCH_CERTIFICATES_DIR is supplied to the Task to query for this location. For Certificates with visibility of 'remoteUser', a 'certs' directory is created in the user's home directory (e.g., /home/{user-name}/certs) and Certificates are placed in that directory. ,
Enum:
{
currentuser: Certificates should be installed to the CurrentUser Certificate store. ,
localmachine: Certificates should be installed to the LocalMachine Certificate store. ,
}
,
Required: False ,
}
enum ,
storeName:
{
Description: This property is applicable only for Pools configured with Windows Compute Nodes. Common store names include: My, Root, CA, Trust, Disallowed, TrustedPeople, TrustedPublisher, AuthRoot, AddressBook, but any custom store name can also be used. The default value is My. ,
Required: False ,
}
string ,
visibility:
{
Description: You can specify more than one visibility in this collection. The default is all Accounts. ,
Required: False ,
}
[
string ,
]
,
}
,
]
,
applicationPackageReferences:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). Changes to Package references affect all new Nodes joining the Pool, but do not affect Compute Nodes that are already in the Pool until they are rebooted or reimaged. There is a maximum of 10 Package references on any given Pool. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
userAccounts:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
password:
{
Required: True ,
}
string ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
linuxUserConfiguration:
{
Description: This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. ,
Required: False ,
}
{
uid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the uid. ,
Format: int32 ,
Required: False ,
}
integer ,
gid:
{
Description: The uid and gid properties must be specified together or not at all. If not specified the underlying operating system picks the gid. ,
Format: int32 ,
Required: False ,
}
integer ,
sshPrivateKey:
{
Description: The private key must not be password protected. The private key is used to automatically configure asymmetric-key based authentication for SSH between Compute Nodes in a Linux Pool when the Pool's enableInterNodeCommunication property is true (it is ignored if enableInterNodeCommunication is false). It does this by placing the key pair into the user's .ssh directory. If not specified, password-less SSH is not configured between Compute Nodes (no modification of the user's .ssh directory is done). ,
Required: False ,
}
string ,
}
,
windowsUserConfiguration:
{
Description: This property can only be specified if the user is on a Windows Pool. If not specified and on a Windows Pool, the user is created with the default options. ,
Required: False ,
}
{
loginMode:
{
Description: The default is 'batch'. ,
Enum:
{
batch: The LOGON32_LOGON_BATCH Win32 login mode. The batch login mode is recommended for long running parallel processes. ,
interactive: The LOGON32_LOGON_INTERACTIVE Win32 login mode. UAC is enabled on Windows Pools. If this option is used with an elevated user identity in a Windows Pool, the user session will not be elevated unless the application executed by the Task command line is configured to always require administrative privilege or to always require maximum privilege. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
mountConfiguration:
{
Description: This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. ,
Required: False ,
}
[
{
azureBlobFileSystemConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
containerName:
{
Required: True ,
}
string ,
accountKey:
{
Description: This property is mutually exclusive with both sasKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
sasKey:
{
Description: This property is mutually exclusive with both accountKey and identity; exactly one must be specified. ,
Required: False ,
}
string ,
blobfuseOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
identityReference:
{
Description: This property is mutually exclusive with both accountKey and sasKey; exactly one must be specified. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
nfsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
cifsMountConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
username:
{
Required: True ,
}
string ,
source:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
password:
{
Required: True ,
}
string ,
}
,
azureFileShareConfiguration:
{
Description: This property is mutually exclusive with all other properties. ,
Required: False ,
}
{
accountName:
{
Required: True ,
}
string ,
azureFileUrl:
{
Description: This is of the form 'https://{account}.file.core.windows.net/'. ,
Required: True ,
}
string ,
accountKey:
{
Required: True ,
}
string ,
relativeMountPath:
{
Description: All file systems are mounted relative to the Batch mounts directory, accessible via the AZ_BATCH_NODE_MOUNTS_DIR environment variable. ,
Required: True ,
}
string ,
mountOptions:
{
Description: These are 'net use' options in Windows and 'mount' options in Linux. ,
Required: False ,
}
string ,
}
,
}
,
]
,
targetNodeCommunicationMode:
{
Description: If omitted, the default value is Default. ,
Enum:
{
default: The node communication mode is automatically set by the Batch service. ,
classic: Nodes using the classic communication mode require inbound TCP communication on ports 29876 and 29877 from the "BatchNodeManagement.{region}" service tag and outbound TCP communication on port 443 to the "Storage.region" and "BatchNodeManagement.{region}" service tags. ,
simplified: Nodes using the simplified communication mode require outbound TCP communication on port 443 to the "BatchNodeManagement.{region}" service tag. No open inbound ports are required. ,
}
,
Required: False ,
}
enum ,
upgradePolicy:
{
Description: Describes an upgrade policy - automatic, manual, or rolling. ,
Required: False ,
}
{
mode:
{
Enum:
{
automatic: All virtual machines in the scale set are automatically updated at the same time. ,
manual: You control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action. ,
rolling: The existing instances in a scale set are brought down in batches to be upgraded. Once the upgraded batch is complete, the instances will begin taking traffic again and the next batch will begin. This continues until all instances brought up-to-date. ,
}
,
Required: True ,
}
enum ,
automaticOSUpgradePolicy:
{
Description: The configuration parameters used for performing automatic OS upgrade. ,
Required: False ,
}
{
disableAutomaticRollback:
{
Description: Whether OS image rollback feature should be disabled. ,
Required: False ,
}
boolean ,
enableAutomaticOSUpgrade:
{
Description: Indicates whether OS upgrades should automatically be applied to scale set instances in a rolling fashion when a newer version of the OS image becomes available.

If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. ,
Required: False ,
}
boolean ,
useRollingUpgradePolicy:
{
Description: Indicates whether rolling upgrade policy should be used during Auto OS Upgrade. Auto OS Upgrade will fallback to the default policy if no policy is defined on the VMSS. ,
Required: False ,
}
boolean ,
osRollingUpgradeDeferral:
{
Description: Defer OS upgrades on the TVMs if they are running tasks. ,
Required: False ,
}
boolean ,
}
,
rollingUpgradePolicy:
{
Description: The configuration parameters used while performing a rolling upgrade. ,
Required: False ,
}
{
enableCrossZoneUpgrade:
{
Description: Allow VMSS to ignore AZ boundaries when constructing upgrade batches. Take into consideration the Update Domain and maxBatchInstancePercent to determine the batch size. This field is able to be set to true or false only when using NodePlacementConfiguration as Zonal. ,
Required: False ,
}
boolean ,
maxBatchInstancePercent:
{
Description: The maximum percent of total virtual machine instances that will be upgraded simultaneously by the rolling upgrade in one batch. As this is a maximum, unhealthy instances in previous or future batches can cause the percentage of instances in a batch to decrease to ensure higher reliability. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyInstancePercent:
{
Description: The maximum percentage of the total virtual machine instances in the scale set that can be simultaneously unhealthy, either as a result of being upgraded, or by being found in an unhealthy state by the virtual machine health checks before the rolling upgrade aborts. This constraint will be checked prior to starting any batch. The value of this field should be between 5 and 100, inclusive. If both maxBatchInstancePercent and maxUnhealthyInstancePercent are assigned with value, the value of maxBatchInstancePercent should not be more than maxUnhealthyInstancePercent. ,
Format: int32 ,
Required: False ,
}
integer ,
maxUnhealthyUpgradedInstancePercent:
{
Description: The maximum percentage of upgraded virtual machine instances that can be found to be in an unhealthy state. This check will happen after each batch is upgraded. If this percentage is ever exceeded, the rolling update aborts. The value of this field should be between 0 and 100, inclusive. ,
Format: int32 ,
Required: False ,
}
integer ,
pauseTimeBetweenBatches:
{
Description: The wait time between completing the update for all virtual machines in one batch and starting the next batch. The time duration should be specified in ISO 8601 format. ,
Format: duration ,
Required: False ,
}
string ,
prioritizeUnhealthyInstances:
{
Description: Upgrade all unhealthy instances in a scale set before any healthy instances. ,
Required: False ,
}
boolean ,
rollbackFailedInstancesOnPolicyBreach:
{
Description: Rollback failed instances to previous model if the Rolling Upgrade policy is violated. ,
Required: False ,
}
boolean ,
}
,
}
,
resourceTags:
{
Description: The user-defined tags to be associated with the Azure Batch Pool. When specified, these tags are propagated to the backing Azure resources associated with the pool. This property can only be specified when the Batch account was created with the poolAllocationMode property set to 'UserSubscription'. ,
Required: False ,
}
object ,
}
,
}
,
}
,
onAllTasksComplete:
{
Description: The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
terminatejob: Terminate the Job. The Job's terminateReason is set to 'AllTasksComplete'. ,
}
,
Required: False ,
}
enum ,
onTaskFailure:
{
Description: A Task is considered to have failed if has a failureInfo. A failureInfo is set if the Task completes with a non-zero exit code after exhausting its retry count, or if there was an error starting the Task, for example due to a resource file download error. The default is noaction. ,
Enum:
{
noaction: Do nothing. The Job remains active unless terminated or disabled by some other means. ,
performexitoptionsjobaction: Take the action associated with the Task exit condition in the Task's exitConditions collection. (This may still result in no action being taken, if that is what the Task specifies.) ,
}
,
Required: False ,
}
enum ,
networkConfiguration:
{
Required: False ,
}
{
subnetId:
{
Description: The virtual network must be in the same region and subscription as the Azure Batch Account. The specified subnet should have enough free IP addresses to accommodate the number of Compute Nodes which will run Tasks from the Job. This can be up to the number of Compute Nodes in the Pool. The 'MicrosoftAzureBatch' service principal must have the 'Classic Virtual Machine Contributor' Role-Based Access Control (RBAC) role for the specified VNet so that Azure Batch service can schedule Tasks on the Nodes. This can be verified by checking if the specified VNet has any associated Network Security Groups (NSG). If communication to the Nodes in the specified subnet is denied by an NSG, then the Batch service will set the state of the Compute Nodes to unusable. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. If the specified VNet has any associated Network Security Groups (NSG), then a few reserved system ports must be enabled for inbound communication from the Azure Batch service. For Pools created with a Virtual Machine configuration, enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Port 443 is also required to be open for outbound connections for communications to Azure Storage. For more details see: https://learn.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration ,
Required: True ,
}
string ,
skipWithdrawFromVNet:
{
Description: If true, nodes will remain joined to the virtual network to DNC. If false, nodes will automatically withdraw when the job ends. Defaults to false. ,
Required: False ,
}
boolean ,
}
,
metadata:
{
Description: The Batch service does not assign any meaning to metadata; it is solely for the use of user code. ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: True ,
}
string ,
}
,
]
,
executionInfo:
{
Required: False ,
}
{
startTime:
{
Description: This is the time at which the Job was created. ,
Format: date-time ,
Required: True ,
}
string ,
endTime:
{
Description: This property is set only if the Job is in the completed state. ,
Format: date-time ,
Required: False ,
}
string ,
poolId:
{
Description: This element contains the actual Pool where the Job is assigned. When you get Job details from the service, they also contain a poolInfo element, which contains the Pool configuration data from when the Job was added or updated. That poolInfo element may also contain a poolId element. If it does, the two IDs are the same. If it does not, it means the Job ran on an auto Pool, and this property contains the ID of that auto Pool. ,
Required: False ,
}
string ,
schedulingError:
{
Description: This property is not set if there was no error starting the Job. ,
Required: False ,
}
{
category:
{
Enum:
{
usererror: The error is due to a user issue, such as misconfiguration. ,
servererror: The error is due to an internal server issue. ,
}
,
Required: True ,
}
enum ,
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
string ,
details:
{
Required: False ,
}
[
{
name:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
terminateReason:
{
Description: This property is set only if the Job is in the completed state. If the Batch service terminates the Job, it sets the reason as follows: JMComplete - the Job Manager Task completed, and killJobOnCompletion was set to true. MaxWallClockTimeExpiry - the Job reached its maxWallClockTime constraint. TerminateJobSchedule - the Job ran as part of a schedule, and the schedule terminated. AllTasksComplete - the Job's onAllTasksComplete attribute is set to terminatejob, and all Tasks in the Job are complete. TaskFailed - the Job's onTaskFailure attribute is set to performExitOptionsJobAction, and a Task in the Job failed with an exit condition that specified a jobAction of terminatejob. Any other string is a user-defined reason specified in a call to the 'Terminate a Job' operation. ,
Required: False ,
}
string ,
}
,
stats:
{
Description: This property is populated only if the CloudJob was retrieved with an expand clause including the 'stats' attribute; otherwise it is null. The statistics may not be immediately available. The Batch service performs periodic roll-up of statistics. The typical delay is about 30 minutes. ,
Required: False ,
}
{
url:
{
Required: True ,
}
string ,
startTime:
{
Format: date-time ,
Required: True ,
}
string ,
lastUpdateTime:
{
Format: date-time ,
Required: True ,
}
string ,
userCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
kernelCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
wallClockTime:
{
Description: The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If a Task was retried, this includes the wall clock time of all the Task retries. ,
Format: duration ,
Required: True ,
}
string ,
readIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
writeIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
readIOGiB:
{
Format: double ,
Required: True ,
}
number ,
writeIOGiB:
{
Format: double ,
Required: True ,
}
number ,
numSucceededTasks:
{
Description: A Task completes successfully if it returns exit code 0. ,
Format: int64 ,
Required: True ,
}
integer ,
numFailedTasks:
{
Description: A Task fails if it exhausts its maximum retry count without returning exit code 0. ,
Format: int64 ,
Required: True ,
}
integer ,
numTaskRetries:
{
Format: int64 ,
Required: True ,
}
integer ,
waitTime:
{
Description: The wait time for a Task is defined as the elapsed time between the creation of the Task and the start of Task execution. (If the Task is retried due to failures, the wait time is the time to the most recent Task execution.) This value is only reported in the Account lifetime statistics; it is not included in the Job statistics. ,
Format: duration ,
Required: True ,
}
string ,
}
,
}
,
]
,
odata.nextLink:
{
Required: False ,
}
string ,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
Task_Add (updated)
Description :  The maximum lifetime of a Task from addition to completion is 180 days. If a Task has not completed within 180 days of being added it will be terminated by the Batch service and left in whatever state it was in at that time.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Task_Add",
  "$parameters": {
    "task": {
      "$properties": [
        {
          "#name": "authenticationTokenSettings",
          "Description": {
            "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
            "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
          }
        }
      ]
    }
  }
}

⚼ Request

POST:  /jobs/{jobId}/tasks
{
jobId:
{
Description: The ID of the Job to which the Task is to be added. ,
Required: True ,
}
string ,
task:
{
Description: The Task to be added. ,
Required: True ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within a Job that differ only by case). ,
Required: True ,
}
string ,
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: For multi-instance Tasks, the command line is executed as the primary Task, after the primary Task and all subtasks have finished executing the coordination command line. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
exitConditions:
{
Description: How the Batch service should respond when the Task completes. ,
Required: False ,
}
{
exitCodes:
{
Required: False ,
}
[
{
code:
{
Format: int32 ,
Required: True ,
}
integer ,
exitOptions:
{
Required: True ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
exitCodeRanges:
{
Required: False ,
}
[
{
start:
{
Format: int32 ,
Required: True ,
}
integer ,
end:
{
Format: int32 ,
Required: True ,
}
integer ,
exitOptions:
{
Required: True ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
preProcessingError:
{
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
fileUploadError:
{
Description: If the Task exited with an exit code that was specified via exitCodes or exitCodeRanges, and then encountered a file upload error, then the action specified by the exit code takes precedence. ,
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
default:
{
Description: This value is used if the Task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. ,
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
resourceFiles:
{
Description: For multi-instance Tasks, the resource files will only be downloaded to the Compute Node on which the primary Task is executed. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
affinityInfo:
{
Required: False ,
}
{
affinityId:
{
Description: You can pass the affinityId of a Node to indicate that this Task needs to run on that Compute Node. Note that this is just a soft affinity. If the target Compute Node is busy or unavailable at the time the Task is scheduled, then the Task will be scheduled elsewhere. ,
Required: True ,
}
string ,
}
,
constraints:
{
Description: If you do not specify constraints, the maxTaskRetryCount is the maxTaskRetryCount specified for the Job, the maxWallClockTime is infinite, and the retentionTime is 7 days. ,
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this must be 1. ,
Format: int32 ,
Required: False ,
}
integer ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
multiInstanceSettings:
{
Description: Multi-instance Tasks are commonly used to support MPI Tasks. In the MPI case, if any of the subtasks fail (for example due to exiting with a non-zero exit code) the entire multi-instance Task fails. The multi-instance Task is then terminated and retried, up to its retry limit. ,
Required: False ,
}
{
numberOfInstances:
{
Description: If omitted, the default is 1. ,
Format: int32 ,
Required: False ,
}
integer ,
coordinationCommandLine:
{
Description: A typical coordination command line launches a background service and verifies that the service is ready to process inter-node messages. ,
Required: True ,
}
string ,
commonResourceFiles:
{
Description: The difference between common resource files and Task resource files is that common resource files are downloaded for all subtasks including the primary, whereas Task resource files are downloaded only for the primary. Also note that these resource files are not downloaded to the Task working directory, but instead are downloaded to the Task root directory (one directory above the working directory). There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
dependsOn:
{
Description: This Task will not be scheduled until all Tasks that it depends on have completed successfully. If any of those Tasks fail and exhaust their retry counts, this Task will never be scheduled. If the Job does not have usesTaskDependencies set to true, and this element is present, the request fails with error code TaskDependenciesNotSpecifiedOnJob. ,
Required: False ,
}
{
taskIds:
{
Description: The taskIds collection is limited to 64000 characters total (i.e. the combined length of all Task IDs). If the taskIds collection exceeds the maximum length, the Add Task request fails with error code TaskDependencyListTooLong. In this case consider using Task ID ranges instead. ,
Required: False ,
}
[
string ,
]
,
taskIdRanges:
{
Required: False ,
}
[
{
start:
{
Format: int32 ,
Required: True ,
}
integer ,
end:
{
Format: int32 ,
Required: True ,
}
integer ,
}
,
]
,
}
,
applicationPackageReferences:
{
Description: Application packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced package is already on the Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
}
,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (201)

{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
dataserviceid:
{
Description: The OData ID of the resource to which the request applied. ,
}
string ,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
Task_List (updated)
Description :  For multi-instance Tasks, information such as affinityId, executionInfo and nodeInfo refer to the primary Task. Use the list subtasks API to retrieve information about subtasks.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Task_List",
  "$responses": {
    "200": {
      "$properties": {
        "value": {
          "$properties": [
            {
              "#name": "authenticationTokenSettings",
              "Description": {
                "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
              }
            }
          ]
        }
      }
    }
  }
}

⚼ Request

GET:  /jobs/{jobId}/tasks
{
jobId:
{
Description: The ID of the Job. ,
Required: True ,
}
string ,
$filter:
{
Description: An OData $filter clause. For more information on constructing this filter, see https://learn.microsoft.com/rest/api/batchservice/odata-filters-in-batch#list-tasks. ,
Required: False ,
}
string ,
$select:
{
Description: An OData $select clause. ,
Required: False ,
}
string ,
$expand:
{
Description: An OData $expand clause. ,
Required: False ,
}
string ,
maxresults:
{
Description: The maximum number of items to return in the response. A maximum of 1000 Tasks can be returned. ,
Format: int32 ,
Required: False ,
}
integer ,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
}
,
$schema:
{
value:
{
Required: False ,
}
[
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. ,
Required: False ,
}
string ,
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
url:
{
Required: False ,
}
string ,
eTag:
{
Description: This is an opaque string. You can use it to detect whether the Task has changed between requests. In particular, you can be pass the ETag when updating a Task to specify that your changes should take effect only if nobody else has modified the Task in the meantime. ,
Required: False ,
}
string ,
lastModified:
{
Format: date-time ,
Required: False ,
}
string ,
creationTime:
{
Format: date-time ,
Required: False ,
}
string ,
exitConditions:
{
Description: How the Batch service should respond when the Task completes. ,
Required: False ,
}
{
exitCodes:
{
Required: False ,
}
[
{
code:
{
Format: int32 ,
Required: True ,
}
integer ,
exitOptions:
{
Required: True ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
exitCodeRanges:
{
Required: False ,
}
[
{
start:
{
Format: int32 ,
Required: True ,
}
integer ,
end:
{
Format: int32 ,
Required: True ,
}
integer ,
exitOptions:
{
Required: True ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
preProcessingError:
{
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
fileUploadError:
{
Description: If the Task exited with an exit code that was specified via exitCodes or exitCodeRanges, and then encountered a file upload error, then the action specified by the exit code takes precedence. ,
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
default:
{
Description: This value is used if the Task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. ,
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
state:
{
Enum:
{
active: The Task is queued and able to run, but is not currently assigned to a Compute Node. A Task enters this state when it is created, when it is enabled after being disabled, or when it is awaiting a retry after a failed run. ,
preparing: The Task has been assigned to a Compute Node, but is waiting for a required Job Preparation Task to complete on the Compute Node. If the Job Preparation Task succeeds, the Task will move to running. If the Job Preparation Task fails, the Task will return to active and will be eligible to be assigned to a different Compute Node. ,
running: The Task is running on a Compute Node. This includes task-level preparation such as downloading resource files or deploying Packages specified on the Task - it does not necessarily mean that the Task command line has started executing. ,
completed: The Task is no longer eligible to run, usually because the Task has finished successfully, or the Task has finished unsuccessfully and has exhausted its retry limit. A Task is also marked as completed if an error occurred launching the Task, or when the Task has been terminated. ,
}
,
Required: False ,
}
enum ,
stateTransitionTime:
{
Format: date-time ,
Required: False ,
}
string ,
previousState:
{
Description: This property is not set if the Task is in its initial Active state. ,
Enum:
{
active: The Task is queued and able to run, but is not currently assigned to a Compute Node. A Task enters this state when it is created, when it is enabled after being disabled, or when it is awaiting a retry after a failed run. ,
preparing: The Task has been assigned to a Compute Node, but is waiting for a required Job Preparation Task to complete on the Compute Node. If the Job Preparation Task succeeds, the Task will move to running. If the Job Preparation Task fails, the Task will return to active and will be eligible to be assigned to a different Compute Node. ,
running: The Task is running on a Compute Node. This includes task-level preparation such as downloading resource files or deploying Packages specified on the Task - it does not necessarily mean that the Task command line has started executing. ,
completed: The Task is no longer eligible to run, usually because the Task has finished successfully, or the Task has finished unsuccessfully and has exhausted its retry limit. A Task is also marked as completed if an error occurred launching the Task, or when the Task has been terminated. ,
}
,
Required: False ,
}
enum ,
previousStateTransitionTime:
{
Description: This property is not set if the Task is in its initial Active state. ,
Format: date-time ,
Required: False ,
}
string ,
commandLine:
{
Description: For multi-instance Tasks, the command line is executed as the primary Task, after the primary Task and all subtasks have finished executing the coordination command line. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: False ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: For multi-instance Tasks, the resource files will only be downloaded to the Compute Node on which the primary Task is executed. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
affinityInfo:
{
Required: False ,
}
{
affinityId:
{
Description: You can pass the affinityId of a Node to indicate that this Task needs to run on that Compute Node. Note that this is just a soft affinity. If the target Compute Node is busy or unavailable at the time the Task is scheduled, then the Task will be scheduled elsewhere. ,
Required: True ,
}
string ,
}
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this must be 1. ,
Format: int32 ,
Required: False ,
}
integer ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
executionInfo:
{
Required: False ,
}
{
startTime:
{
Description: 'Running' corresponds to the running state, so if the Task specifies resource files or Packages, then the start time reflects the time at which the Task started downloading or deploying these. If the Task has been restarted or retried, this is the most recent time at which the Task started running. This property is present only for Tasks that are in the running or completed state. ,
Format: date-time ,
Required: False ,
}
string ,
endTime:
{
Description: This property is set only if the Task is in the Completed state. ,
Format: date-time ,
Required: False ,
}
string ,
exitCode:
{
Description: This property is set only if the Task is in the completed state. In general, the exit code for a process reflects the specific convention implemented by the application developer for that process. If you use the exit code value to make decisions in your code, be sure that you know the exit code convention used by the application process. However, if the Batch service terminates the Task (due to timeout, or user termination via the API) you may see an operating system-defined exit code. ,
Format: int32 ,
Required: False ,
}
integer ,
containerInfo:
{
Description: This property is set only if the Task runs in a container context. ,
Required: False ,
}
{
containerId:
{
Required: False ,
}
string ,
state:
{
Description: This is the state of the container according to the Docker service. It is equivalent to the status field returned by "docker inspect". ,
Required: False ,
}
string ,
error:
{
Description: This is the detailed error string from the Docker service, if available. It is equivalent to the error field returned by "docker inspect". ,
Required: False ,
}
string ,
}
,
failureInfo:
{
Description: This property is set only if the Task is in the completed state and encountered a failure. ,
Required: False ,
}
{
category:
{
Enum:
{
usererror: The error is due to a user issue, such as misconfiguration. ,
servererror: The error is due to an internal server issue. ,
}
,
Required: True ,
}
enum ,
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
string ,
details:
{
Required: False ,
}
[
{
name:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
retryCount:
{
Description: Task application failures (non-zero exit code) are retried, pre-processing errors (the Task could not be run) and file upload errors are not retried. The Batch service will retry the Task up to the limit specified by the constraints. ,
Format: int32 ,
Required: True ,
}
integer ,
lastRetryTime:
{
Description: This element is present only if the Task was retried (i.e. retryCount is nonzero). If present, this is typically the same as startTime, but may be different if the Task has been restarted for reasons other than retry; for example, if the Compute Node was rebooted during a retry, then the startTime is updated but the lastRetryTime is not. ,
Format: date-time ,
Required: False ,
}
string ,
requeueCount:
{
Description: When the user removes Compute Nodes from a Pool (by resizing/shrinking the pool) or when the Job is being disabled, the user can specify that running Tasks on the Compute Nodes be requeued for execution. This count tracks how many times the Task has been requeued for these reasons. ,
Format: int32 ,
Required: True ,
}
integer ,
lastRequeueTime:
{
Description: This property is set only if the requeueCount is nonzero. ,
Format: date-time ,
Required: False ,
}
string ,
result:
{
Description: If the value is 'failed', then the details of the failure can be found in the failureInfo property. ,
Enum:
{
success: The Task ran successfully. ,
failure: There was an error during processing of the Task. The failure may have occurred before the Task process was launched, while the Task process was executing, or after the Task process exited. ,
}
,
Required: False ,
}
enum ,
}
,
nodeInfo:
{
Required: False ,
}
{
affinityId:
{
Required: False ,
}
string ,
nodeUrl:
{
Required: False ,
}
string ,
poolId:
{
Required: False ,
}
string ,
nodeId:
{
Required: False ,
}
string ,
taskRootDirectory:
{
Required: False ,
}
string ,
taskRootDirectoryUrl:
{
Required: False ,
}
string ,
}
,
multiInstanceSettings:
{
Description: Multi-instance Tasks are commonly used to support MPI Tasks. In the MPI case, if any of the subtasks fail (for example due to exiting with a non-zero exit code) the entire multi-instance Task fails. The multi-instance Task is then terminated and retried, up to its retry limit. ,
Required: False ,
}
{
numberOfInstances:
{
Description: If omitted, the default is 1. ,
Format: int32 ,
Required: False ,
}
integer ,
coordinationCommandLine:
{
Description: A typical coordination command line launches a background service and verifies that the service is ready to process inter-node messages. ,
Required: True ,
}
string ,
commonResourceFiles:
{
Description: The difference between common resource files and Task resource files is that common resource files are downloaded for all subtasks including the primary, whereas Task resource files are downloaded only for the primary. Also note that these resource files are not downloaded to the Task working directory, but instead are downloaded to the Task root directory (one directory above the working directory). There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
stats:
{
Required: False ,
}
{
url:
{
Required: True ,
}
string ,
startTime:
{
Format: date-time ,
Required: True ,
}
string ,
lastUpdateTime:
{
Format: date-time ,
Required: True ,
}
string ,
userCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
kernelCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
wallClockTime:
{
Description: The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If the Task was retried, this includes the wall clock time of all the Task retries. ,
Format: duration ,
Required: True ,
}
string ,
readIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
writeIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
readIOGiB:
{
Format: double ,
Required: True ,
}
number ,
writeIOGiB:
{
Format: double ,
Required: True ,
}
number ,
waitTime:
{
Format: duration ,
Required: True ,
}
string ,
}
,
dependsOn:
{
Description: This Task will not be scheduled until all Tasks that it depends on have completed successfully. If any of those Tasks fail and exhaust their retry counts, this Task will never be scheduled. ,
Required: False ,
}
{
taskIds:
{
Description: The taskIds collection is limited to 64000 characters total (i.e. the combined length of all Task IDs). If the taskIds collection exceeds the maximum length, the Add Task request fails with error code TaskDependencyListTooLong. In this case consider using Task ID ranges instead. ,
Required: False ,
}
[
string ,
]
,
taskIdRanges:
{
Required: False ,
}
[
{
start:
{
Format: int32 ,
Required: True ,
}
integer ,
end:
{
Format: int32 ,
Required: True ,
}
integer ,
}
,
]
,
}
,
applicationPackageReferences:
{
Description: Application packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced package is already on the Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
}
,
]
,
odata.nextLink:
{
Required: False ,
}
string ,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
Task_AddCollection (updated)
Description :  Note that each Task must have a unique ID. The Batch service may not return the results for each Task in the same order the Tasks were submitted in this request. If the server times out or the connection is closed during the request, the request may have been partially or fully processed, or not at all. In such cases, the user should re-issue the request. Note that it is up to the user to correctly handle failures when re-issuing a request. For example, you should use the same Task IDs during a retry so that if the prior operation succeeded, the retry will not create extra Tasks unexpectedly. If the response contains any Tasks which failed to add, a client can retry the request. In a retry, it is most efficient to resubmit only Tasks that failed to add, and to omit Tasks that were successfully added on the first attempt. The maximum lifetime of a Task from addition to completion is 180 days. If a Task has not completed within 180 days of being added it will be terminated by the Batch service and left in whatever state it was in at that time.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Task_AddCollection",
  "$parameters": {
    "taskCollection": {
      "$properties": {
        "value": {
          "$properties": [
            {
              "#name": "authenticationTokenSettings",
              "Description": {
                "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
                "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
              }
            }
          ]
        }
      }
    }
  }
}

⚼ Request

POST:  /jobs/{jobId}/addtaskcollection
{
jobId:
{
Description: The ID of the Job to which the Task collection is to be added. ,
Required: True ,
}
string ,
taskCollection:
{
Description: The Tasks to be added. ,
Required: True ,
}
{
value:
{
Description: The total serialized size of this collection must be less than 1MB. If it is greater than 1MB (for example if each Task has 100's of resource files or environment variables), the request will fail with code 'RequestBodyTooLarge' and should be retried again with fewer Tasks. ,
Required: True ,
}
[
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. The ID is case-preserving and case-insensitive (that is, you may not have two IDs within a Job that differ only by case). ,
Required: True ,
}
string ,
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
commandLine:
{
Description: For multi-instance Tasks, the command line is executed as the primary Task, after the primary Task and all subtasks have finished executing the coordination command line. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: True ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
exitConditions:
{
Description: How the Batch service should respond when the Task completes. ,
Required: False ,
}
{
exitCodes:
{
Required: False ,
}
[
{
code:
{
Format: int32 ,
Required: True ,
}
integer ,
exitOptions:
{
Required: True ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
exitCodeRanges:
{
Required: False ,
}
[
{
start:
{
Format: int32 ,
Required: True ,
}
integer ,
end:
{
Format: int32 ,
Required: True ,
}
integer ,
exitOptions:
{
Required: True ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
preProcessingError:
{
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
fileUploadError:
{
Description: If the Task exited with an exit code that was specified via exitCodes or exitCodeRanges, and then encountered a file upload error, then the action specified by the exit code takes precedence. ,
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
default:
{
Description: This value is used if the Task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. ,
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
resourceFiles:
{
Description: For multi-instance Tasks, the resource files will only be downloaded to the Compute Node on which the primary Task is executed. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
affinityInfo:
{
Required: False ,
}
{
affinityId:
{
Description: You can pass the affinityId of a Node to indicate that this Task needs to run on that Compute Node. Note that this is just a soft affinity. If the target Compute Node is busy or unavailable at the time the Task is scheduled, then the Task will be scheduled elsewhere. ,
Required: True ,
}
string ,
}
,
constraints:
{
Description: If you do not specify constraints, the maxTaskRetryCount is the maxTaskRetryCount specified for the Job, the maxWallClockTime is infinite, and the retentionTime is 7 days. ,
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this must be 1. ,
Format: int32 ,
Required: False ,
}
integer ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
multiInstanceSettings:
{
Description: Multi-instance Tasks are commonly used to support MPI Tasks. In the MPI case, if any of the subtasks fail (for example due to exiting with a non-zero exit code) the entire multi-instance Task fails. The multi-instance Task is then terminated and retried, up to its retry limit. ,
Required: False ,
}
{
numberOfInstances:
{
Description: If omitted, the default is 1. ,
Format: int32 ,
Required: False ,
}
integer ,
coordinationCommandLine:
{
Description: A typical coordination command line launches a background service and verifies that the service is ready to process inter-node messages. ,
Required: True ,
}
string ,
commonResourceFiles:
{
Description: The difference between common resource files and Task resource files is that common resource files are downloaded for all subtasks including the primary, whereas Task resource files are downloaded only for the primary. Also note that these resource files are not downloaded to the Task working directory, but instead are downloaded to the Task root directory (one directory above the working directory). There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
dependsOn:
{
Description: This Task will not be scheduled until all Tasks that it depends on have completed successfully. If any of those Tasks fail and exhaust their retry counts, this Task will never be scheduled. If the Job does not have usesTaskDependencies set to true, and this element is present, the request fails with error code TaskDependenciesNotSpecifiedOnJob. ,
Required: False ,
}
{
taskIds:
{
Description: The taskIds collection is limited to 64000 characters total (i.e. the combined length of all Task IDs). If the taskIds collection exceeds the maximum length, the Add Task request fails with error code TaskDependencyListTooLong. In this case consider using Task ID ranges instead. ,
Required: False ,
}
[
string ,
]
,
taskIdRanges:
{
Required: False ,
}
[
{
start:
{
Format: int32 ,
Required: True ,
}
integer ,
end:
{
Format: int32 ,
Required: True ,
}
integer ,
}
,
]
,
}
,
applicationPackageReferences:
{
Description: Application packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced package is already on the Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
}
,
]
,
}
,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 2 minutes. If the value is larger than 120, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
}
,
$schema:
{
value:
{
Required: False ,
}
[
{
status:
{
Enum:
{
success: The Task was added successfully. ,
clienterror: The Task failed to add due to a client error and should not be retried without modifying the request as appropriate. ,
servererror: Task failed to add due to a server error and can be retried without modification. ,
}
,
Required: True ,
}
enum ,
taskId:
{
Required: True ,
}
string ,
eTag:
{
Description: You can use this to detect whether the Task has changed between requests. In particular, you can be pass the ETag with an Update Task request to specify that your changes should take effect only if nobody else has modified the Job in the meantime. ,
Required: False ,
}
string ,
lastModified:
{
Format: date-time ,
Required: False ,
}
string ,
location:
{
Required: False ,
}
string ,
error:
{
Required: False ,
}
{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
]
,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
Task_Get (updated)
Description :  For multi-instance Tasks, information such as affinityId, executionInfo and nodeInfo refer to the primary Task. Use the list subtasks API to retrieve information about subtasks.
Reference :  Link ¶

⚶ Changes

{
  "#id": "Task_Get",
  "$responses": {
    "200": {
      "$properties": [
        {
          "#name": "authenticationTokenSettings",
          "Description": {
            "new": "Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information",
            "old": "If this property is set, the Batch service provides the Task with an authentication token which can be used to authenticate Batch service operations without requiring an Account access key. The token is provided via the AZ_BATCH_AUTHENTICATION_TOKEN environment variable. The operations that the Task can carry out using the token depend on the settings. For example, a Task can request Job permissions in order to add other Tasks to the Job, or check the status of the Job or of other Tasks under the Job."
          }
        }
      ]
    }
  }
}

⚼ Request

GET:  /jobs/{jobId}/tasks/{taskId}
{
jobId:
{
Description: The ID of the Job that contains the Task. ,
Required: True ,
}
string ,
taskId:
{
Description: The ID of the Task to get information about. ,
Required: True ,
}
string ,
$select:
{
Description: An OData $select clause. ,
Required: False ,
}
string ,
$expand:
{
Description: An OData $expand clause. ,
Required: False ,
}
string ,
timeout:
{
Description: The maximum time that the server can spend processing the request, in seconds. The default is 30 seconds. If the value is larger than 30, the default will be used instead. ,
Format: int32 ,
Required: False ,
}
integer ,
client-request-id:
{
Description: The caller-generated request identity, in the form of a GUID with no decoration such as curly braces, e.g. 9C4D50EE-2D56-4CD3-8152-34347DC9F2B0. ,
Format: uuid ,
Required: False ,
}
string ,
return-client-request-id:
{
Description: Whether the server should return the client-request-id in the response. ,
Required: False ,
}
boolean ,
ocp-date:
{
Description: The time the request was issued. Client libraries typically set this to the current system clock time; set it explicitly if you are calling the REST API directly. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service exactly matches the value specified by the client. ,
Required: False ,
}
string ,
If-None-Match:
{
Description: An ETag value associated with the version of the resource known to the client. The operation will be performed only if the resource's current ETag on the service does not match the value specified by the client. ,
Required: False ,
}
string ,
If-Modified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
If-Unmodified-Since:
{
Description: A timestamp indicating the last modified time of the resource known to the client. The operation will be performed only if the resource on the service has not been modified since the specified time. ,
Format: date-time-rfc1123 ,
Required: False ,
}
string ,
api-version:
{
Description: Client API Version. ,
Required: True ,
}
string ,
}

⚐ Response (200)

{
$headers:
{
client-request-id:
{
Description: The client-request-id provided by the client during the request. This will be returned only if the return-client-request-id parameter was set to true. ,
}
string ,
request-id:
{
Description: A unique identifier for the request that was made to the Batch service. If a request is consistently failing and you have verified that the request is properly formulated, you may use this value to report the error to Microsoft. In your report, include the value of this request ID, the approximate time that the request was made, the Batch Account against which the request was made, and the region that Account resides in. ,
}
string ,
etag:
{
Description: The ETag HTTP response header. This is an opaque string. You can use it to detect whether the resource has changed between requests. In particular, you can pass the ETag to one of the If-Modified-Since, If-Unmodified-Since, If-Match or If-None-Match headers. ,
}
string ,
last-modified:
{
Description: The time at which the resource was last modified. ,
}
string ,
dataserviceid:
{
Description: The OData ID of the resource to which the request applied. ,
}
string ,
}
,
$schema:
{
Description: Batch will retry Tasks when a recovery operation is triggered on a Node. Examples of recovery operations include (but are not limited to) when an unhealthy Node is rebooted or a Compute Node disappeared due to host failure. Retries due to recovery operations are independent of and are not counted against the maxTaskRetryCount. Even if the maxTaskRetryCount is 0, an internal retry due to a recovery operation may occur. Because of this, all Tasks should be idempotent. This means Tasks need to tolerate being interrupted and restarted without causing any corruption or duplicate data. The best practice for long running Tasks is to use some form of checkpointing. ,
}
{
id:
{
Description: The ID can contain any combination of alphanumeric characters including hyphens and underscores, and cannot contain more than 64 characters. ,
Required: False ,
}
string ,
displayName:
{
Description: The display name need not be unique and can contain any Unicode characters up to a maximum length of 1024. ,
Required: False ,
}
string ,
url:
{
Required: False ,
}
string ,
eTag:
{
Description: This is an opaque string. You can use it to detect whether the Task has changed between requests. In particular, you can be pass the ETag when updating a Task to specify that your changes should take effect only if nobody else has modified the Task in the meantime. ,
Required: False ,
}
string ,
lastModified:
{
Format: date-time ,
Required: False ,
}
string ,
creationTime:
{
Format: date-time ,
Required: False ,
}
string ,
exitConditions:
{
Description: How the Batch service should respond when the Task completes. ,
Required: False ,
}
{
exitCodes:
{
Required: False ,
}
[
{
code:
{
Format: int32 ,
Required: True ,
}
integer ,
exitOptions:
{
Required: True ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
exitCodeRanges:
{
Required: False ,
}
[
{
start:
{
Format: int32 ,
Required: True ,
}
integer ,
end:
{
Format: int32 ,
Required: True ,
}
integer ,
exitOptions:
{
Required: True ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
]
,
preProcessingError:
{
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
fileUploadError:
{
Description: If the Task exited with an exit code that was specified via exitCodes or exitCodeRanges, and then encountered a file upload error, then the action specified by the exit code takes precedence. ,
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
default:
{
Description: This value is used if the Task exits with any nonzero exit code not listed in the exitCodes or exitCodeRanges collection, with a pre-processing error if the preProcessingError property is not present, or with a file upload error if the fileUploadError property is not present. If you want non-default behavior on exit code 0, you must list it explicitly using the exitCodes or exitCodeRanges collection. ,
Required: False ,
}
{
jobAction:
{
Description: The default is none for exit code 0 and terminate for all other exit conditions. If the Job's onTaskFailed property is noaction, then specifying this property returns an error and the add Task request fails with an invalid property value error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). ,
Enum:
{
none: Take no action. ,
disable: Disable the Job. This is equivalent to calling the disable Job API, with a disableTasks value of requeue. ,
terminate: Terminate the Job. The terminateReason in the Job's executionInfo is set to "TaskFailed". ,
}
,
Required: False ,
}
enum ,
dependencyAction:
{
Description: Possible values are 'satisfy' (allowing dependent tasks to progress) and 'block' (dependent tasks continue to wait). Batch does not yet support cancellation of dependent tasks. ,
Enum:
{
satisfy: Satisfy tasks waiting on this task; once all dependencies are satisfied, the task will be scheduled to run. ,
block: Blocks tasks waiting on this task, preventing them from being scheduled. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
state:
{
Enum:
{
active: The Task is queued and able to run, but is not currently assigned to a Compute Node. A Task enters this state when it is created, when it is enabled after being disabled, or when it is awaiting a retry after a failed run. ,
preparing: The Task has been assigned to a Compute Node, but is waiting for a required Job Preparation Task to complete on the Compute Node. If the Job Preparation Task succeeds, the Task will move to running. If the Job Preparation Task fails, the Task will return to active and will be eligible to be assigned to a different Compute Node. ,
running: The Task is running on a Compute Node. This includes task-level preparation such as downloading resource files or deploying Packages specified on the Task - it does not necessarily mean that the Task command line has started executing. ,
completed: The Task is no longer eligible to run, usually because the Task has finished successfully, or the Task has finished unsuccessfully and has exhausted its retry limit. A Task is also marked as completed if an error occurred launching the Task, or when the Task has been terminated. ,
}
,
Required: False ,
}
enum ,
stateTransitionTime:
{
Format: date-time ,
Required: False ,
}
string ,
previousState:
{
Description: This property is not set if the Task is in its initial Active state. ,
Enum:
{
active: The Task is queued and able to run, but is not currently assigned to a Compute Node. A Task enters this state when it is created, when it is enabled after being disabled, or when it is awaiting a retry after a failed run. ,
preparing: The Task has been assigned to a Compute Node, but is waiting for a required Job Preparation Task to complete on the Compute Node. If the Job Preparation Task succeeds, the Task will move to running. If the Job Preparation Task fails, the Task will return to active and will be eligible to be assigned to a different Compute Node. ,
running: The Task is running on a Compute Node. This includes task-level preparation such as downloading resource files or deploying Packages specified on the Task - it does not necessarily mean that the Task command line has started executing. ,
completed: The Task is no longer eligible to run, usually because the Task has finished successfully, or the Task has finished unsuccessfully and has exhausted its retry limit. A Task is also marked as completed if an error occurred launching the Task, or when the Task has been terminated. ,
}
,
Required: False ,
}
enum ,
previousStateTransitionTime:
{
Description: This property is not set if the Task is in its initial Active state. ,
Format: date-time ,
Required: False ,
}
string ,
commandLine:
{
Description: For multi-instance Tasks, the command line is executed as the primary Task, after the primary Task and all subtasks have finished executing the coordination command line. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. If the command line refers to file paths, it should use a relative path (relative to the Task working directory), or use the Batch provided environment variable (https://learn.microsoft.com/azure/batch/batch-compute-node-environment-variables). ,
Required: False ,
}
string ,
containerSettings:
{
Description: If the Pool that will run this Task has containerConfiguration set, this must be set as well. If the Pool that will run this Task doesn't have containerConfiguration set, this must not be set. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all Task environment variables are mapped into the container, and the Task command line is executed in the container. Files produced in the container outside of AZ_BATCH_NODE_ROOT_DIR might not be reflected to the host disk, meaning that Batch file APIs will not be able to access those files. ,
Required: False ,
}
{
containerRunOptions:
{
Description: These additional options are supplied as arguments to the "docker create" command, in addition to those controlled by the Batch Service. ,
Required: False ,
}
string ,
imageName:
{
Description: This is the full Image reference, as would be specified to "docker pull". If no tag is provided as part of the Image name, the tag ":latest" is used as a default. ,
Required: True ,
}
string ,
registry:
{
Description: This setting can be omitted if was already provided at Pool creation. ,
Required: False ,
}
{
username:
{
Required: False ,
}
string ,
password:
{
Required: False ,
}
string ,
registryServer:
{
Description: If omitted, the default is "docker.io". ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
workingDirectory:
{
Description: The default is 'taskWorkingDirectory'. ,
Enum:
{
taskWorkingDirectory: Use the standard Batch service Task working directory, which will contain the Task Resource Files populated by Batch. ,
containerImageDefault: Use the working directory defined in the container Image. Beware that this directory will not contain the Resource Files downloaded by Batch. ,
}
,
Required: False ,
}
enum ,
containerHostBatchBindMounts:
{
Description: If this array is null or be not present, container task will mount entire temporary disk drive in windows (or AZ_BATCH_NODE_ROOT_DIR in Linux). It won't' mount any data paths into container if this array is set as empty. ,
Required: False ,
}
[
{
source:
{
Enum:
{
Shared: The path for multi-instances task to shared their files. ,
Startup: The path for start task. ,
VfsMounts: The path contains all virtual file systems are mounted on this node. ,
Task: The task path. ,
JobPrep: The job-prep task path. ,
Applications: The applications path. ,
}
,
Required: False ,
}
enum ,
isReadOnly:
{
Description: For Linux, if you mount this path as a read/write mode, this does not mean that all users in container have the read/write access for the path, it depends on the access in host VM. If this path is mounted read-only, all users within the container will not be able to modify the path. ,
Required: False ,
}
boolean ,
}
,
]
,
}
,
resourceFiles:
{
Description: For multi-instance Tasks, the resource files will only be downloaded to the Compute Node on which the primary Task is executed. There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
outputFiles:
{
Description: For multi-instance Tasks, the files will only be uploaded from the Compute Node on which the primary Task is executed. ,
Required: False ,
}
[
{
filePattern:
{
Description: Both relative and absolute paths are supported. Relative paths are relative to the Task working directory. The following wildcards are supported: * matches 0 or more characters (for example pattern abc* would match abc or abcdef), ** matches any directory, ? matches any single character, [abc] matches one character in the brackets, and [a-c] matches one character in the range. Brackets can include a negation to match any character not specified (for example [!abc] matches any character but a, b, or c). If a file name starts with "." it is ignored by default but may be matched by specifying it explicitly (for example *.gif will not match .a.gif, but .*.gif will). A simple example: **\*.txt matches any file that does not start in '.' and ends with .txt in the Task working directory or any subdirectory. If the filename contains a wildcard character it can be escaped using brackets (for example abc[*] would match a file named abc*). Note that both \ and / are treated as directory separators on Windows, but only / is on Linux. Environment variables (%var% on Windows or $var on Linux) are expanded prior to the pattern being applied. ,
Required: True ,
}
string ,
destination:
{
Required: True ,
}
{
container:
{
Required: False ,
}
{
path:
{
Description: If filePattern refers to a specific file (i.e. contains no wildcards), then path is the name of the blob to which to upload that file. If filePattern contains one or more wildcards (and therefore may match multiple files), then path is the name of the blob virtual directory (which is prepended to each blob name) to which to upload the file(s). If omitted, file(s) are uploaded to the root of the container with a blob name matching their file name. ,
Required: False ,
}
string ,
containerUrl:
{
Description: If not using a managed identity, the URL must include a Shared Access Signature (SAS) granting write permissions to the container. ,
Required: True ,
}
string ,
identityReference:
{
Description: The identity must have write access to the Azure Blob Storage container ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
uploadHeaders:
{
Description: These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://learn.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types ,
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
}
,
uploadOptions:
{
Required: True ,
}
{
uploadCondition:
{
Description: The default is taskcompletion. ,
Enum:
{
tasksuccess: Upload the file(s) only after the Task process exits with an exit code of 0. ,
taskfailure: Upload the file(s) only after the Task process exits with a nonzero exit code. ,
taskcompletion: Upload the file(s) after the Task process exits, no matter what the exit code was. ,
}
,
Required: True ,
}
enum ,
}
,
}
,
]
,
environmentSettings:
{
Required: False ,
}
[
{
name:
{
Required: True ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
affinityInfo:
{
Required: False ,
}
{
affinityId:
{
Description: You can pass the affinityId of a Node to indicate that this Task needs to run on that Compute Node. Note that this is just a soft affinity. If the target Compute Node is busy or unavailable at the time the Task is scheduled, then the Task will be scheduled elsewhere. ,
Required: True ,
}
string ,
}
,
constraints:
{
Required: False ,
}
{
maxWallClockTime:
{
Description: If this is not specified, there is no time limit on how long the Task may run. ,
Format: duration ,
Required: False ,
}
string ,
retentionTime:
{
Description: The default is 7 days, i.e. the Task directory will be retained for 7 days unless the Compute Node is removed or the Job is deleted. ,
Format: duration ,
Required: False ,
}
string ,
maxTaskRetryCount:
{
Description: Note that this value specifically controls the number of retries for the Task executable due to a nonzero exit code. The Batch service will try the Task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the Task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the Task after the first attempt. If the maximum retry count is -1, the Batch service retries the Task without limit, however this is not recommended for a start task or any task. The default value is 0 (no retries). ,
Format: int32 ,
Required: False ,
}
integer ,
}
,
requiredSlots:
{
Description: The default is 1. A Task can only be scheduled to run on a compute node if the node has enough free scheduling slots available. For multi-instance Tasks, this must be 1. ,
Format: int32 ,
Required: False ,
}
integer ,
userIdentity:
{
Description: If omitted, the Task runs as a non-administrative user unique to the Task. ,
Required: False ,
}
{
username:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
string ,
autoUser:
{
Description: The userName and autoUser properties are mutually exclusive; you must specify one but not both. ,
Required: False ,
}
{
scope:
{
Description: The default value is pool. If the pool is running Windows a value of Task should be specified if stricter isolation between tasks is required. For example, if the task mutates the registry in a way which could impact other tasks, or if certificates have been specified on the pool which should not be accessible by normal tasks but should be accessible by StartTasks. ,
Enum:
{
task: Specifies that the service should create a new user for the Task. ,
pool: Specifies that the Task runs as the common auto user Account which is created on every Compute Node in a Pool. ,
}
,
Required: False ,
}
enum ,
elevationLevel:
{
Description: The default value is nonAdmin. ,
Enum:
{
nonadmin: The user is a standard user without elevated access. ,
admin: The user is a user with elevated access and operates with full Administrator permissions. ,
}
,
Required: False ,
}
enum ,
}
,
}
,
executionInfo:
{
Required: False ,
}
{
startTime:
{
Description: 'Running' corresponds to the running state, so if the Task specifies resource files or Packages, then the start time reflects the time at which the Task started downloading or deploying these. If the Task has been restarted or retried, this is the most recent time at which the Task started running. This property is present only for Tasks that are in the running or completed state. ,
Format: date-time ,
Required: False ,
}
string ,
endTime:
{
Description: This property is set only if the Task is in the Completed state. ,
Format: date-time ,
Required: False ,
}
string ,
exitCode:
{
Description: This property is set only if the Task is in the completed state. In general, the exit code for a process reflects the specific convention implemented by the application developer for that process. If you use the exit code value to make decisions in your code, be sure that you know the exit code convention used by the application process. However, if the Batch service terminates the Task (due to timeout, or user termination via the API) you may see an operating system-defined exit code. ,
Format: int32 ,
Required: False ,
}
integer ,
containerInfo:
{
Description: This property is set only if the Task runs in a container context. ,
Required: False ,
}
{
containerId:
{
Required: False ,
}
string ,
state:
{
Description: This is the state of the container according to the Docker service. It is equivalent to the status field returned by "docker inspect". ,
Required: False ,
}
string ,
error:
{
Description: This is the detailed error string from the Docker service, if available. It is equivalent to the error field returned by "docker inspect". ,
Required: False ,
}
string ,
}
,
failureInfo:
{
Description: This property is set only if the Task is in the completed state and encountered a failure. ,
Required: False ,
}
{
category:
{
Enum:
{
usererror: The error is due to a user issue, such as misconfiguration. ,
servererror: The error is due to an internal server issue. ,
}
,
Required: True ,
}
enum ,
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
string ,
details:
{
Required: False ,
}
[
{
name:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}
,
retryCount:
{
Description: Task application failures (non-zero exit code) are retried, pre-processing errors (the Task could not be run) and file upload errors are not retried. The Batch service will retry the Task up to the limit specified by the constraints. ,
Format: int32 ,
Required: True ,
}
integer ,
lastRetryTime:
{
Description: This element is present only if the Task was retried (i.e. retryCount is nonzero). If present, this is typically the same as startTime, but may be different if the Task has been restarted for reasons other than retry; for example, if the Compute Node was rebooted during a retry, then the startTime is updated but the lastRetryTime is not. ,
Format: date-time ,
Required: False ,
}
string ,
requeueCount:
{
Description: When the user removes Compute Nodes from a Pool (by resizing/shrinking the pool) or when the Job is being disabled, the user can specify that running Tasks on the Compute Nodes be requeued for execution. This count tracks how many times the Task has been requeued for these reasons. ,
Format: int32 ,
Required: True ,
}
integer ,
lastRequeueTime:
{
Description: This property is set only if the requeueCount is nonzero. ,
Format: date-time ,
Required: False ,
}
string ,
result:
{
Description: If the value is 'failed', then the details of the failure can be found in the failureInfo property. ,
Enum:
{
success: The Task ran successfully. ,
failure: There was an error during processing of the Task. The failure may have occurred before the Task process was launched, while the Task process was executing, or after the Task process exited. ,
}
,
Required: False ,
}
enum ,
}
,
nodeInfo:
{
Required: False ,
}
{
affinityId:
{
Required: False ,
}
string ,
nodeUrl:
{
Required: False ,
}
string ,
poolId:
{
Required: False ,
}
string ,
nodeId:
{
Required: False ,
}
string ,
taskRootDirectory:
{
Required: False ,
}
string ,
taskRootDirectoryUrl:
{
Required: False ,
}
string ,
}
,
multiInstanceSettings:
{
Description: Multi-instance Tasks are commonly used to support MPI Tasks. In the MPI case, if any of the subtasks fail (for example due to exiting with a non-zero exit code) the entire multi-instance Task fails. The multi-instance Task is then terminated and retried, up to its retry limit. ,
Required: False ,
}
{
numberOfInstances:
{
Description: If omitted, the default is 1. ,
Format: int32 ,
Required: False ,
}
integer ,
coordinationCommandLine:
{
Description: A typical coordination command line launches a background service and verifies that the service is ready to process inter-node messages. ,
Required: True ,
}
string ,
commonResourceFiles:
{
Description: The difference between common resource files and Task resource files is that common resource files are downloaded for all subtasks including the primary, whereas Task resource files are downloaded only for the primary. Also note that these resource files are not downloaded to the Task working directory, but instead are downloaded to the Task root directory (one directory above the working directory). There is a maximum size for the list of resource files. When the max size is exceeded, the request will fail and the response error code will be RequestEntityTooLarge. If this occurs, the collection of ResourceFiles must be reduced in size. This can be achieved using .zip files, Application Packages, or Docker Containers. ,
Required: False ,
}
[
{
autoStorageContainerName:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. ,
Required: False ,
}
string ,
storageContainerUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. This URL must be readable and listable from compute nodes. There are three ways to get such a URL for a container in Azure storage: include a Shared Access Signature (SAS) granting read and list permissions on the container, use a managed identity with read and list permissions, or set the ACL for the container to allow public access. ,
Required: False ,
}
string ,
httpUrl:
{
Description: The autoStorageContainerName, storageContainerUrl and httpUrl properties are mutually exclusive and one of them must be specified. If the URL points to Azure Blob Storage, it must be readable from compute nodes. There are three ways to get such a URL for a blob in Azure storage: include a Shared Access Signature (SAS) granting read permissions on the blob, use a managed identity with read permission, or set the ACL for the blob or its container to allow public access. ,
Required: False ,
}
string ,
blobPrefix:
{
Description: The property is valid only when autoStorageContainerName or storageContainerUrl is used. This prefix can be a partial filename or a subdirectory. If a prefix is not specified, all the files in the container will be downloaded. ,
Required: False ,
}
string ,
filePath:
{
Description: If the httpUrl property is specified, the filePath is required and describes the path which the file will be downloaded to, including the filename. Otherwise, if the autoStorageContainerName or storageContainerUrl property is specified, filePath is optional and is the directory to download the files to. In the case where filePath is used as a directory, any directory structure already associated with the input data will be retained in full and appended to the specified filePath directory. The specified relative path cannot break out of the Task's working directory (for example by using '..'). ,
Required: False ,
}
string ,
fileMode:
{
Description: This property applies only to files being downloaded to Linux Compute Nodes. It will be ignored if it is specified for a resourceFile which will be downloaded to a Windows Compute Node. If this property is not specified for a Linux Compute Node, then a default value of 0770 is applied to the file. ,
Required: False ,
}
string ,
identityReference:
{
Description: The reference to a user assigned identity associated with the Batch pool which a compute node will use. ,
Required: False ,
}
{
resourceId:
{
Description: The ARM resource id of the user assigned identity. ,
Required: False ,
}
string ,
}
,
}
,
]
,
}
,
stats:
{
Required: False ,
}
{
url:
{
Required: True ,
}
string ,
startTime:
{
Format: date-time ,
Required: True ,
}
string ,
lastUpdateTime:
{
Format: date-time ,
Required: True ,
}
string ,
userCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
kernelCPUTime:
{
Format: duration ,
Required: True ,
}
string ,
wallClockTime:
{
Description: The wall clock time is the elapsed time from when the Task started running on a Compute Node to when it finished (or to the last time the statistics were updated, if the Task had not finished by then). If the Task was retried, this includes the wall clock time of all the Task retries. ,
Format: duration ,
Required: True ,
}
string ,
readIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
writeIOps:
{
Format: int64 ,
Required: True ,
}
integer ,
readIOGiB:
{
Format: double ,
Required: True ,
}
number ,
writeIOGiB:
{
Format: double ,
Required: True ,
}
number ,
waitTime:
{
Format: duration ,
Required: True ,
}
string ,
}
,
dependsOn:
{
Description: This Task will not be scheduled until all Tasks that it depends on have completed successfully. If any of those Tasks fail and exhaust their retry counts, this Task will never be scheduled. ,
Required: False ,
}
{
taskIds:
{
Description: The taskIds collection is limited to 64000 characters total (i.e. the combined length of all Task IDs). If the taskIds collection exceeds the maximum length, the Add Task request fails with error code TaskDependencyListTooLong. In this case consider using Task ID ranges instead. ,
Required: False ,
}
[
string ,
]
,
taskIdRanges:
{
Required: False ,
}
[
{
start:
{
Format: int32 ,
Required: True ,
}
integer ,
end:
{
Format: int32 ,
Required: True ,
}
integer ,
}
,
]
,
}
,
applicationPackageReferences:
{
Description: Application packages are downloaded and deployed to a shared directory, not the Task working directory. Therefore, if a referenced package is already on the Node, and is up to date, then it is not re-downloaded; the existing copy on the Compute Node is used. If a referenced Package cannot be installed, for example because the package has been deleted or because download failed, the Task fails. ,
Required: False ,
}
[
{
applicationId:
{
Description: When creating a pool, the package's application ID must be fully qualified (/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Batch/batchAccounts/{accountName}/applications/{applicationName}). ,
Required: True ,
}
string ,
version:
{
Description: If this is omitted on a Pool, and no default version is specified for this application, the request fails with the error code InvalidApplicationPackageReferences and HTTP status code 409. If this is omitted on a Task, and no default version is specified for this application, the Task fails with a pre-processing error. ,
Required: False ,
}
string ,
}
,
]
,
authenticationTokenSettings:
{
Description: Warning: This object is deprecated and will be removed after September 30, 2024. Please see https://azure.microsoft.com/updates?id=azure-batch-task-authentication-token-will-be-retired-on-30-september-2024 for more information ,
Required: False ,
}
{
access:
{
Description: The authentication token grants access to a limited set of Batch service operations. Currently the only supported value for the access property is 'job', which grants access to all operations related to the Job which contains the Task. ,
Required: False ,
}
[
string ,
]
,
}
,
}
,
}

⚐ Response (default)

{
code:
{
Required: False ,
}
string ,
message:
{
Required: False ,
}
{
lang:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
values:
{
Required: False ,
}
[
{
key:
{
Required: False ,
}
string ,
value:
{
Required: False ,
}
string ,
}
,
]
,
}