@azure-rest/batch 1.0.0-beta.1 → 1.0.0-beta.2

package/dist/commonjs/outputModels.d.ts

@@ -68,7 +68,7 @@ export interface VirtualMachineConfigurationOutput {
     nodeAgentSKUId: string;
     /** Windows operating system settings on the virtual machine. This property must not be specified if the imageReference property specifies a Linux OS Image. */
     windowsConfiguration?: WindowsConfigurationOutput;
-    /** The configuration for data disks attached to the Compute Nodes in the Pool. 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://docs.microsoft.com/en-us/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://docs.microsoft.com/en-us/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. */
+    /** The configuration for data disks attached to the Compute Nodes in the Pool. 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://docs.microsoft.com/azure/virtual-machines/linux/classic/attach-disk#initialize-a-new-data-disk-in-linux and https://docs.microsoft.com/azure/virtual-machines/windows/attach-disk-ps#add-an-empty-data-disk-to-a-virtual-machine. */
     dataDisks?: Array<DataDiskOutput>;
     /**
      * This only applies to Images that contain the Windows operating system, and
@@ -115,6 +115,10 @@ export interface ImageReferenceOutput {
     virtualMachineImageId?: string;
     /** 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'. */
     readonly exactVersion?: string;
+    /** The shared gallery image unique identifier. This property is mutually exclusive with other properties and can be fetched from shared gallery image GET call. */
+    sharedGalleryImageId?: string;
+    /** The community gallery image unique identifier. This property is mutually exclusive with other properties and can be fetched from community gallery image GET call. */
+    communityGalleryImageId?: string;
 }
 /** Windows operating system settings to apply to the virtual machine. */
 export interface WindowsConfigurationOutput {
@@ -129,16 +133,28 @@ export interface WindowsConfigurationOutput {
 export interface DataDiskOutput {
     /** The logical unit number. The logicalUnitNumber is used to uniquely identify each data disk. If attaching multiple disks, each should have a distinct logicalUnitNumber. The value must be between 0 and 63, inclusive. */
     lun: number;
-    /** The type of caching to be enabled for the data disks. 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/. */
+    /**
+     * The type of caching to be enabled for the data disks. 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/.
+     *
+     * Possible values: "none", "readonly", "readwrite"
+     */
     caching?: CachingTypeOutput;
     /** The initial disk size in gigabytes. */
     diskSizeGB: number;
-    /** The storage Account type to be used for the data disk. If omitted, the default is "standard_lrs". */
+    /**
+     * The storage Account type to be used for the data disk. If omitted, the default is "standard_lrs".
+     *
+     * Possible values: "standard_lrs", "premium_lrs", "standardssd_lrs"
+     */
     storageAccountType?: StorageAccountTypeOutput;
 }
 /** The configuration for container-enabled Pools. */
 export interface ContainerConfigurationOutput {
-    /** The container technology to be used. */
+    /**
+     * The container technology to be used.
+     *
+     * Possible values: "dockerCompatible", "criCompatible"
+     */
     type: ContainerTypeOutput;
     /** The collection of container Image names. 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. */
     containerImageNames?: string[];
@@ -170,7 +186,7 @@ export interface BatchNodeIdentityReferenceOutput {
  * Azure Compute Gallery Image.
  */
 export interface DiskEncryptionConfigurationOutput {
-    /** The list of disk targets Batch Service will encrypt on the compute node. If omitted, no disks on the compute nodes in the pool will be encrypted. On Linux pool, only "TemporaryDisk" is supported; on Windows pool, "OsDisk" and "TemporaryDisk" must be specified. */
+    /** The list of disk targets Batch Service will encrypt on the compute node. The list of disk targets Batch Service will encrypt on the compute node. */
     targets?: DiskEncryptionTargetOutput[];
 }
 /**
@@ -179,7 +195,11 @@ export interface DiskEncryptionConfigurationOutput {
  * with best effort balancing.
  */
 export interface BatchNodePlacementConfigurationOutput {
-    /** Node placement Policy type on Batch Pools. Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy. */
+    /**
+     * Node placement Policy type on Batch Pools. Allocation policy used by Batch Service to provision the nodes. If not specified, Batch will use the regional policy.
+     *
+     * Possible values: "Shared", "Startup", "VfsMounts", "Task", "JobPrep", "Applications"
+     */
     policy?: BatchNodePlacementPolicyTypeOutput;
 }
 /** The configuration for virtual machine extensions. */
@@ -207,7 +227,11 @@ export interface VMExtensionOutput {
 export interface OSDiskOutput {
     /** Specifies the ephemeral Disk Settings for the operating system disk used by the compute node (VM). */
     ephemeralOSDiskSettings?: DiffDiskSettingsOutput;
-    /** Specifies the caching requirements. Possible values are: None, ReadOnly, ReadWrite. The default values are: None for Standard storage. ReadOnly for Premium storage. */
+    /**
+     * Specifies the caching requirements. Possible values are: None, ReadOnly, ReadWrite. The default values are: None for Standard storage. ReadOnly for Premium storage.
+     *
+     * Possible values: "none", "readonly", "readwrite"
+     */
     caching?: CachingTypeOutput;
     /** The initial disk size in GB when creating new OS disk. */
     diskSizeGB?: number;
@@ -221,19 +245,42 @@ export interface OSDiskOutput {
  * compute node (VM).
  */
 export interface DiffDiskSettingsOutput {
-    /** Specifies the ephemeral disk placement for operating system disk for all VMs in the pool. 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://docs.microsoft.com/en-us/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://docs.microsoft.com/en-us/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements. */
+    /**
+     * Specifies the ephemeral disk placement for operating system disk for all VMs in the pool. 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://docs.microsoft.com/azure/virtual-machines/windows/ephemeral-os-disks#size-requirements and Linux VMs at https://docs.microsoft.com/azure/virtual-machines/linux/ephemeral-os-disks#size-requirements.
+     *
+     * Possible values: "cachedisk"
+     */
     placement?: DiffDiskPlacementOutput;
 }
 /** The managed disk parameters. */
 export interface ManagedDiskOutput {
-    /** The storage account type for managed disk. */
-    storageAccountType: StorageAccountTypeOutput;
+    /**
+     * The storage account type for managed disk.
+     *
+     * Possible values: "standard_lrs", "premium_lrs", "standardssd_lrs"
+     */
+    storageAccountType?: StorageAccountTypeOutput;
+    /** Specifies the security profile settings for the managed disk. */
+    securityProfile?: VMDiskSecurityProfileOutput;
+}
+/** Specifies the security profile settings for the managed disk. **Note**: It can only be set for Confidential VMs and required when using Confidential VMs. */
+export interface VMDiskSecurityProfileOutput {
+    /**
+     * Specifies the EncryptionType of the managed disk. It is set to VMGuestStateOnly for encryption of just the VMGuestState blob, and NonPersistedTPM for not persisting firmware state in the VMGuestState blob. **Note**: It can be set for only Confidential VMs and is required when using Confidential VMs.
+     *
+     * Possible values: "NonPersistedTPM", "VMGuestStateOnly"
+     */
+    securityEncryptionType?: SecurityEncryptionTypesOutput;
 }
 /** Specifies the security profile settings for the virtual machine or virtual machine scale set. */
 export interface SecurityProfileOutput {
-    /** 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. */
+    /** 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. */
     encryptionAtHost: boolean;
-    /** Specifies the SecurityType of the virtual machine. It has to be set to any specified value to enable UefiSettings. */
+    /**
+     * Specifies the SecurityType of the virtual machine. It has to be set to any specified value to enable UefiSettings.
+     *
+     * Possible values: "trustedLaunch", "confidentialVM"
+     */
     securityType: SecurityTypesOutput;
     /** Specifies the security settings like secure boot and vTPM used while creating the virtual machine. Specifies the security settings like secure boot and vTPM used while creating the virtual machine. */
     uefiSettings: UefiSettingsOutput;
@@ -255,13 +302,17 @@ export interface ServiceArtifactReferenceOutput {
 }
 /** The network configuration for a Pool. */
 export interface NetworkConfigurationOutput {
-    /** The ARM resource identifier of the virtual network subnet which the Compute Nodes of the Pool will join. This is of the form /subscriptions/{subscription}/resourceGroups/{group}/providers/{provider}/virtualNetworks/{network}/subnets/{subnet}. 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. For Pools created with virtualMachineConfiguration 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. 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. Also enable outbound connections to Azure Storage on port 443. For more details see: https://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */
+    /** The ARM resource identifier of the virtual network subnet which the Compute Nodes of the Pool will join. 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. Enable ports 29876 and 29877, as well as port 22 for Linux and port 3389 for Windows. Also enable outbound connections to Azure Storage on port 443. For more details see: https://docs.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */
     subnetId?: string;
-    /** The scope of dynamic vnet assignment. */
+    /**
+     * The scope of dynamic vnet assignment.
+     *
+     * Possible values: "none", "job"
+     */
     dynamicVNetAssignmentScope?: DynamicVNetAssignmentScopeOutput;
-    /** The configuration for endpoints on Compute Nodes in the Batch Pool. Pool endpoint configuration is only supported on Pools with the virtualMachineConfiguration property. */
+    /** The configuration for endpoints on Compute Nodes in the Batch Pool. */
     endpointConfiguration?: BatchPoolEndpointConfigurationOutput;
-    /** The Public IPAddress configuration for Compute Nodes in the Batch Pool. Public IP configuration property is only supported on Pools with the virtualMachineConfiguration property. */
+    /** The Public IPAddress configuration for Compute Nodes in the Batch Pool. */
     publicIPAddressConfiguration?: PublicIpAddressConfigurationOutput;
     /** Whether this pool should enable accelerated networking. 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. */
     enableAcceleratedNetworking?: boolean;
@@ -278,7 +329,11 @@ export interface BatchPoolEndpointConfigurationOutput {
 export interface InboundNatPoolOutput {
     /** The name of the endpoint. 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. */
     name: string;
-    /** The protocol of the endpoint. */
+    /**
+     * The protocol of the endpoint.
+     *
+     * Possible values: "tcp", "udp"
+     */
     protocol: InboundEndpointProtocolOutput;
     /** The port number on the Compute Node. This must be unique within a Batch Pool. Acceptable values are between 1 and 65535 except for 22, 3389, 29876 and 29877 as these are reserved. If any reserved values are provided the request fails with HTTP status code 400. */
     backendPort: number;
@@ -293,7 +348,11 @@ export interface InboundNatPoolOutput {
 export interface NetworkSecurityGroupRuleOutput {
     /** The priority for this rule. 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. */
     priority: number;
-    /** The action that should be taken for a specified IP address, subnet range or tag. */
+    /**
+     * The action that should be taken for a specified IP address, subnet range or tag.
+     *
+     * Possible values: "allow", "deny"
+     */
     access: NetworkSecurityGroupRuleAccessOutput;
     /** The source address prefix or tag to match for the rule. 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. */
     sourceAddressPrefix: string;
@@ -302,7 +361,11 @@ export interface NetworkSecurityGroupRuleOutput {
 }
 /** The public IP Address configuration of the networking configuration of a Pool. */
 export interface PublicIpAddressConfigurationOutput {
-    /** The provisioning type for Public IP Addresses for the Pool. The default value is BatchManaged. */
+    /**
+     * The provisioning type for Public IP Addresses for the Pool. The default value is BatchManaged.
+     *
+     * Possible values: "batchmanaged", "usermanaged", "nopublicipaddresses"
+     */
     provision?: IpAddressProvisioningTypeOutput;
     /** The list of public IPs which the Batch service will use when provisioning Compute Nodes. 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}. */
     ipAddressIds?: string[];
@@ -323,7 +386,7 @@ export interface PublicIpAddressConfigurationOutput {
  * block Batch from being able to re-run the StartTask.
  */
 export interface BatchStartTaskOutput {
-    /** The command line of the StartTask. 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://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */
+    /** The command line of the StartTask. 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://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */
     commandLine: string;
     /** The settings for the container under which the StartTask runs. 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. */
     containerSettings?: BatchTaskContainerSettingsOutput;
@@ -346,8 +409,25 @@ export interface BatchTaskContainerSettingsOutput {
     imageName: string;
     /** The private registry which contains the container Image. This setting can be omitted if was already provided at Pool creation. */
     registry?: ContainerRegistryReferenceOutput;
-    /** The location of the container Task working directory. The default is 'taskWorkingDirectory'. */
+    /**
+     * The location of the container Task working directory. The default is 'taskWorkingDirectory'.
+     *
+     * Possible values: "taskWorkingDirectory", "containerImageDefault"
+     */
     workingDirectory?: ContainerWorkingDirectoryOutput;
+    /** The paths you want to mounted to container task. 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. */
+    containerHostBatchBindMounts?: Array<ContainerHostBatchBindMountEntryOutput>;
+}
+/** The entry of path and mount mode you want to mount into task container. */
+export interface ContainerHostBatchBindMountEntryOutput {
+    /**
+     * The path which be mounted to container customer can select.
+     *
+     * Possible values: "regional", "zonal"
+     */
+    source?: ContainerHostDataPathOutput;
+    /** Mount this source path as read-only mode or not. Default value is false (read/write mode). 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. */
+    isReadOnly?: boolean;
 }
 /** A single file or multiple files to be downloaded to a Compute Node. */
 export interface ResourceFileOutput {
@@ -382,9 +462,17 @@ export interface UserIdentityOutput {
 }
 /** Specifies the options for the auto user that runs an Azure Batch Task. */
 export interface AutoUserSpecificationOutput {
-    /** The scope for the auto user. 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, such as if the task mutates the registry in a way which could impact other tasks. */
+    /**
+     * The scope for the auto user. 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, such as if the task mutates the registry in a way which could impact other tasks.
+     *
+     * Possible values: "task", "pool"
+     */
     scope?: AutoUserScopeOutput;
-    /** The elevation level of the auto user. The default value is nonAdmin. */
+    /**
+     * The elevation level of the auto user. The default value is nonAdmin.
+     *
+     * Possible values: "nonadmin", "admin"
+     */
     elevationLevel?: ElevationLevelOutput;
 }
 /** A reference to an Package to be deployed to Compute Nodes. */
@@ -396,7 +484,11 @@ export interface BatchApplicationPackageReferenceOutput {
 }
 /** Specifies how Tasks should be distributed across Compute Nodes. */
 export interface BatchTaskSchedulingPolicyOutput {
-    /** How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread. */
+    /**
+     * How Tasks are distributed across Compute Nodes in a Pool. If not specified, the default is spread.
+     *
+     * Possible values: "spread", "pack"
+     */
     nodeFillType: BatchNodeFillTypeOutput;
 }
 /**
@@ -408,7 +500,11 @@ export interface UserAccountOutput {
     name: string;
     /** The password for the user Account. */
     password: string;
-    /** The elevation level of the user Account. The default value is nonAdmin. */
+    /**
+     * The elevation level of the user Account. The default value is nonAdmin.
+     *
+     * Possible values: "nonadmin", "admin"
+     */
     elevationLevel?: ElevationLevelOutput;
     /** The Linux-specific user configuration for the user Account. This property is ignored if specified on a Windows Pool. If not specified, the user is created with the default options. */
     linuxUserConfiguration?: LinuxUserConfigurationOutput;
@@ -426,7 +522,11 @@ export interface LinuxUserConfigurationOutput {
 }
 /** Properties used to create a user Account on a Windows Compute Node. */
 export interface WindowsUserConfigurationOutput {
-    /** The login mode for the user. The default value for VirtualMachineConfiguration Pools is 'batch'. */
+    /**
+     * The login mode for the user. The default is 'batch'.
+     *
+     * Possible values: "batch", "interactive"
+     */
     loginMode?: LoginModeOutput;
 }
 /**
@@ -504,18 +604,22 @@ export interface AzureFileShareConfigurationOutput {
 }
 /** Describes an upgrade policy - automatic, manual, or rolling. */
 export interface UpgradePolicyOutput {
-    /** Specifies the mode of an upgrade to virtual machines in the scale set.<br /><br /> Possible values are:<br /><br /> **Manual** - You  control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action.<br /><br /> **Automatic** - All virtual machines in the scale set are automatically updated at the same time.<br /><br /> **Rolling** - Scale set performs updates in batches with an optional pause time in between. */
+    /**
+     * Specifies the mode of an upgrade to virtual machines in the scale set.<br /><br /> Possible values are:<br /><br /> **Manual** - You  control the application of updates to virtual machines in the scale set. You do this by using the manualUpgrade action.<br /><br /> **Automatic** - All virtual machines in the scale set are automatically updated at the same time.<br /><br /> **Rolling** - Scale set performs updates in batches with an optional pause time in between.
+     *
+     * Possible values: "automatic", "manual", "rolling"
+     */
     mode: UpgradeModeOutput;
     /** Configuration parameters used for performing automatic OS Upgrade. The configuration parameters used for performing automatic OS upgrade. */
     automaticOSUpgradePolicy?: AutomaticOsUpgradePolicyOutput;
-    /** The configuration parameters used while performing a rolling upgrade. This property is only supported on Pools with the virtualMachineConfiguration property. */
+    /** The configuration parameters used while performing a rolling upgrade. */
     rollingUpgradePolicy?: RollingUpgradePolicyOutput;
 }
 /** The configuration parameters used for performing automatic OS upgrade. */
 export interface AutomaticOsUpgradePolicyOutput {
     /** Whether OS image rollback feature should be disabled. */
     disableAutomaticRollback?: boolean;
-    /** 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. <br /><br /> If this is set to true for Windows based pools, [WindowsConfiguration.enableAutomaticUpdates](https://learn.microsoft.com/en-us/rest/api/batchservice/pool/add?tabs=HTTP#windowsconfiguration) cannot be set to true. */
+    /** 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. <br /><br /> 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. */
     enableAutomaticOSUpgrade?: boolean;
     /** 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. */
     useRollingUpgradePolicy?: boolean;
@@ -560,15 +664,23 @@ export interface BatchPoolOutput {
     readonly lastModified?: string;
     /** The creation time of the Pool. */
     readonly creationTime?: string;
-    /** The current state of the Pool. */
+    /**
+     * The current state of the Pool.
+     *
+     * Possible values: "active", "deleting"
+     */
     readonly state?: BatchPoolStateOutput;
     /** The time at which the Pool entered its current state. */
     readonly stateTransitionTime?: string;
-    /** Whether the Pool is resizing. */
+    /**
+     * Whether the Pool is resizing.
+     *
+     * Possible values: "steady", "resizing", "stopping"
+     */
     readonly allocationState?: AllocationStateOutput;
     /** The time at which the Pool entered its current allocation state. */
     readonly allocationStateTransitionTime?: string;
-    /** The size of virtual machines in the Pool. All virtual machines in a Pool are the same size. For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://docs.microsoft.com/azure/batch/batch-pool-vm-sizes). */
+    /** The size of virtual machines in the Pool. All virtual machines in a Pool are the same size. For information about available VM sizes, see Sizes for Virtual Machines (Linux) (https://azure.microsoft.com/documentation/articles/virtual-machines-linux-sizes/) or Sizes for Virtual Machines (Windows) (https://azure.microsoft.com/documentation/articles/virtual-machines-windows-sizes/). Batch supports all Azure VM sizes except STANDARD_A0 and those with premium storage (STANDARD_GS, STANDARD_DS, and STANDARD_DSV2 series). */
     readonly vmSize?: string;
     /** The virtual machine configuration for the Pool. This property must be specified. */
     readonly virtualMachineConfiguration?: VirtualMachineConfigurationOutput;
@@ -610,15 +722,23 @@ export interface BatchPoolOutput {
     readonly userAccounts?: Array<UserAccountOutput>;
     /** A list of name-value pairs associated with the Pool as metadata. */
     readonly metadata?: Array<MetadataItemOutput>;
-    /** Utilization and resource usage statistics for the entire lifetime of the Pool. This property is populated only if the CloudPool 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. */
+    /** Utilization and resource usage statistics for the entire lifetime of the Pool. This property is populated only if the BatchPool 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. */
     readonly stats?: BatchPoolStatisticsOutput;
     /** A list of file systems to mount on each node in the pool. This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. */
     readonly mountConfiguration?: Array<MountConfigurationOutput>;
     /** The identity of the Batch pool, if configured. The list of user identities associated with the Batch pool. The user identity dictionary key references will be ARM resource ids in the form: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{identityName}'. */
     readonly identity?: BatchPoolIdentityOutput;
-    /** The desired node communication mode for the pool. If omitted, the default value is Default. */
+    /**
+     * The desired node communication mode for the pool. If omitted, the default value is Default.
+     *
+     * Possible values: "default", "classic", "simplified"
+     */
     targetNodeCommunicationMode?: BatchNodeCommunicationModeOutput;
-    /** The current state of the pool communication mode. */
+    /**
+     * The current state of the pool communication mode.
+     *
+     * Possible values: "default", "classic", "simplified"
+     */
     readonly currentNodeCommunicationMode?: BatchNodeCommunicationModeOutput;
     /** The upgrade policy for the Pool. Describes an upgrade policy - automatic, manual, or rolling. */
     upgradePolicy?: UpgradePolicyOutput;
@@ -710,7 +830,11 @@ export interface BatchPoolResourceStatisticsOutput {
 }
 /** The identity of the Batch pool, if configured. */
 export interface BatchPoolIdentityOutput {
-    /** The identity of the Batch pool, if configured. The list of user identities associated with the Batch pool. The user identity dictionary key references will be ARM resource ids in the form: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{identityName}'. */
+    /**
+     * The identity of the Batch pool, if configured. The list of user identities associated with the Batch pool. The user identity dictionary key references will be ARM resource ids in the form: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{identityName}'.
+     *
+     * Possible values: "UserAssigned", "None"
+     */
     type: BatchPoolIdentityTypeOutput;
     /** The list of user identities associated with the Batch account. The user identity dictionary key references will be ARM resource ids in the form: '/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ManagedIdentity/userAssignedIdentities/{identityName}'. */
     userAssignedIdentities?: Array<UserAssignedIdentityOutput>;
@@ -740,13 +864,21 @@ export interface BatchSupportedImageOutput {
     nodeAgentSKUId: string;
     /** The reference to the Azure Virtual Machine's Marketplace Image. */
     imageReference: ImageReferenceOutput;
-    /** The type of operating system (e.g. Windows or Linux) of the Image. */
+    /**
+     * The type of operating system (e.g. Windows or Linux) of the Image.
+     *
+     * Possible values: "linux", "windows"
+     */
     osType: OSTypeOutput;
     /** The capabilities or features which the Image supports. Not every capability of the Image is listed. Capabilities in this list are considered of special interest and are generally related to integration with other features in the Azure Batch service. */
     capabilities?: string[];
     /** The time when the Azure Batch service will stop accepting create Pool requests for the Image. */
     batchSupportEndOfLife?: string;
-    /** Whether the Azure Batch service actively verifies that the Image is compatible with the associated Compute Node agent SKU. */
+    /**
+     * Whether the Azure Batch service actively verifies that the Image is compatible with the associated Compute Node agent SKU.
+     *
+     * Possible values: "verified", "unverified"
+     */
     verificationType: ImageVerificationTypeOutput;
 }
 /** The result of listing the Compute Node counts in the Account. */
@@ -793,6 +925,10 @@ export interface BatchNodeCountsOutput {
     unusable: number;
     /** The number of Compute Nodes in the waitingForStartTask state. */
     waitingForStartTask: number;
+    /** The number of Compute Nodes in the deallocated state. */
+    deallocated: number;
+    /** The number of Compute Nodes in the deallocating state. */
+    deallocating: number;
     /** The total number of Compute Nodes. */
     total: number;
     /** The number of Compute Nodes in the upgradingOS state. */
@@ -814,11 +950,19 @@ export interface BatchJobOutput {
     readonly lastModified?: string;
     /** The creation time of the Job. */
     readonly creationTime?: string;
-    /** The current state of the Job. */
+    /**
+     * The current state of the Job.
+     *
+     * Possible values: "active", "disabling", "disabled", "enabling", "terminating", "completed", "deleting"
+     */
     readonly state?: BatchJobStateOutput;
     /** The time at which the Job entered its current state. */
     readonly stateTransitionTime?: string;
-    /** The previous state of the Job. This property is not set if the Job is in its initial Active state. */
+    /**
+     * The previous state of the Job. This property is not set if the Job is in its initial Active state.
+     *
+     * Possible values: "active", "disabling", "disabled", "enabling", "terminating", "completed", "deleting"
+     */
     readonly previousState?: BatchJobStateOutput;
     /** The time at which the Job entered its previous state. This property is not set if the Job is in its initial Active state. */
     readonly previousStateTransitionTime?: string;
@@ -840,9 +984,17 @@ export interface BatchJobOutput {
     readonly commonEnvironmentSettings?: Array<EnvironmentSettingOutput>;
     /** The Pool settings associated with the Job. */
     poolInfo: BatchPoolInfoOutput;
-    /** The action the Batch service should take when all Tasks in the Job are in the completed state. The default is noaction. */
+    /**
+     * The action the Batch service should take when all Tasks in the Job are in the completed state. The default is noaction.
+     *
+     * Possible values: "noaction", "terminatejob"
+     */
     onAllTasksComplete?: OnAllBatchTasksCompleteOutput;
-    /** The action the Batch service should take when any Task in the Job fails. 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. */
+    /**
+     * The action the Batch service should take when any Task in the Job fails. 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.
+     *
+     * Possible values: "noaction", "performexitoptionsjobaction"
+     */
     readonly onTaskFailure?: OnBatchTaskFailureOutput;
     /** The network configuration for the Job. */
     readonly networkConfiguration?: BatchJobNetworkConfigurationOutput;
@@ -850,7 +1002,7 @@ export interface BatchJobOutput {
     metadata?: Array<MetadataItemOutput>;
     /** The execution information for the Job. */
     readonly executionInfo?: BatchJobExecutionInfoOutput;
-    /** Resource usage statistics for the entire lifetime of the Job. 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. */
+    /** Resource usage statistics for the entire lifetime of the Job. This property is populated only if the BatchJob 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. */
     readonly stats?: BatchJobStatisticsOutput;
 }
 /** The execution constraints for a Job. */
@@ -890,7 +1042,7 @@ export interface BatchJobManagerTaskOutput {
     id: string;
     /** The display name of the Job Manager Task. It need not be unique and can contain any Unicode characters up to a maximum length of 1024. */
     displayName?: string;
-    /** The command line of the Job Manager Task. 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://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */
+    /** The command line of the Job Manager Task. 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://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */
     commandLine: string;
     /** The settings for the container under which the Job Manager Task runs. 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. */
     containerSettings?: BatchTaskContainerSettingsOutput;
@@ -948,7 +1100,7 @@ export interface OutputFileBlobContainerDestinationOutput {
     containerUrl: string;
     /** The reference to the user assigned identity to use to access Azure Blob Storage specified by containerUrl. The identity must have write access to the Azure Blob Storage container. */
     identityReference?: BatchNodeIdentityReferenceOutput;
-    /** A list of name-value pairs for headers to be used in uploading output files. These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://docs.microsoft.com/en-us/rest/api/storageservices/put-blob#request-headers-all-blob-types. */
+    /** A list of name-value pairs for headers to be used in uploading output files. These headers will be specified when uploading files to Azure Storage. Official document on allowed headers when uploading blobs: https://docs.microsoft.com/rest/api/storageservices/put-blob#request-headers-all-blob-types. */
     uploadHeaders?: Array<HttpHeaderOutput>;
 }
 /** An HTTP header name-value pair */
@@ -963,7 +1115,11 @@ export interface HttpHeaderOutput {
  * to perform the upload.
  */
 export interface OutputFileUploadConfigOutput {
-    /** The conditions under which the Task output file or set of files should be uploaded. The default is taskcompletion. */
+    /**
+     * The conditions under which the Task output file or set of files should be uploaded. The default is taskcompletion.
+     *
+     * Possible values: "tasksuccess", "taskfailure", "taskcompletion"
+     */
     uploadCondition: OutputFileUploadConditionOutput;
 }
 /** Execution constraints to apply to a Task. */
@@ -1014,7 +1170,7 @@ export interface AuthenticationTokenSettingsOutput {
 export interface BatchJobPreparationTaskOutput {
     /** A string that uniquely identifies the Job Preparation Task within the Job. 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). */
     id?: string;
-    /** The command line of the Job Preparation Task. 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://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */
+    /** The command line of the Job Preparation Task. 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://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */
     commandLine: string;
     /** The settings for the container under which the Job Preparation Task runs. 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. */
     containerSettings?: BatchTaskContainerSettingsOutput;
@@ -1052,7 +1208,7 @@ export interface BatchJobPreparationTaskOutput {
 export interface BatchJobReleaseTaskOutput {
     /** A string that uniquely identifies the Job Release Task within the Job. 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). */
     id?: string;
-    /** The command line of the Job Release Task. 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://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */
+    /** The command line of the Job Release Task. 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://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */
     commandLine: string;
     /** The settings for the container under which the Job Release Task runs. 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. */
     containerSettings?: BatchTaskContainerSettingsOutput;
@@ -1081,7 +1237,11 @@ export interface BatchPoolInfoOutput {
 export interface BatchAutoPoolSpecificationOutput {
     /** A prefix to be added to the unique identifier when a Pool is automatically created. 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. */
     autoPoolIdPrefix?: string;
-    /** The minimum lifetime of created auto Pools, and how multiple Jobs on a schedule are assigned to Pools. */
+    /**
+     * The minimum lifetime of created auto Pools, and how multiple Jobs on a schedule are assigned to Pools.
+     *
+     * Possible values: "jobschedule", "job"
+     */
     poolLifetimeOption: BatchPoolLifetimeOptionOutput;
     /** Whether to keep an auto Pool alive after its lifetime expires. 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. */
     keepAlive?: boolean;
@@ -1094,7 +1254,7 @@ export interface BatchPoolSpecificationOutput {
     displayName?: string;
     /** The size of the virtual machines in the Pool. All virtual machines in a Pool are the same size. For information about available sizes of virtual machines in Pools, see Choose a VM size for Compute Nodes in an Azure Batch Pool (https://docs.microsoft.com/azure/batch/batch-pool-vm-sizes). */
     vmSize: string;
-    /** The virtual machine configuration for the Pool. This property must be specified if the Pool needs to be created with Azure IaaS VMs. If it is not specified then the Batch service returns an error; if you are calling the REST API directly, the HTTP status code is 400 (Bad Request). */
+    /** The virtual machine configuration for the Pool. This property must be specified. */
     virtualMachineConfiguration?: VirtualMachineConfigurationOutput;
     /** The number of task slots that can be used to run concurrent tasks on a single compute node in the pool. 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. */
     taskSlotsPerNode?: number;
@@ -1128,15 +1288,21 @@ export interface BatchPoolSpecificationOutput {
     metadata?: Array<MetadataItemOutput>;
     /** A list of file systems to mount on each node in the pool. This supports Azure Files, NFS, CIFS/SMB, and Blobfuse. */
     mountConfiguration?: Array<MountConfigurationOutput>;
-    /** The desired node communication mode for the pool. If omitted, the default value is Default. */
+    /**
+     * The desired node communication mode for the pool. If omitted, the default value is Default.
+     *
+     * Possible values: "default", "classic", "simplified"
+     */
     targetNodeCommunicationMode?: BatchNodeCommunicationModeOutput;
     /** The upgrade policy for the Pool. Describes an upgrade policy - automatic, manual, or rolling. */
     upgradePolicy?: UpgradePolicyOutput;
 }
 /** The network configuration for the Job. */
 export interface BatchJobNetworkConfigurationOutput {
-    /** The ARM resource identifier of the virtual network subnet which Compute Nodes running Tasks from the Job will join for the duration of the Task. This will only work with a VirtualMachineConfiguration Pool. 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://docs.microsoft.com/en-us/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */
+    /** The ARM resource identifier of the virtual network subnet which Compute Nodes running Tasks from the Job will join for the duration of the Task. 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://docs.microsoft.com/azure/batch/batch-api-basics#virtual-network-vnet-and-firewall-configuration. */
     subnetId: string;
+    /** Whether to withdraw Compute Nodes from the virtual network to DNC when the job is terminated or deleted.  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. */
+    skipWithdrawFromVNet: boolean;
 }
 /** Contains information about the execution of a Job in the Azure Batch service. */
 export interface BatchJobExecutionInfoOutput {
@@ -1153,7 +1319,11 @@ export interface BatchJobExecutionInfoOutput {
 }
 /** An error encountered by the Batch service when scheduling a Job. */
 export interface BatchJobSchedulingErrorOutput {
-    /** The category of the Job scheduling error. */
+    /**
+     * The category of the Job scheduling error.
+     *
+     * Possible values: "usererror", "servererror"
+     */
     category: ErrorCategoryOutput;
     /** An identifier for the Job scheduling error. Codes are invariant and are intended to be consumed programmatically. */
     code?: string;
@@ -1232,7 +1402,11 @@ export interface BatchJobPreparationTaskExecutionInfoOutput {
     startTime: string;
     /** The time at which the Job Preparation Task completed. This property is set only if the Task is in the Completed state. */
     endTime?: string;
-    /** The current state of the Job Preparation Task on the Compute Node. */
+    /**
+     * The current state of the Job Preparation Task on the Compute Node.
+     *
+     * Possible values: "running", "completed"
+     */
     state: BatchJobPreparationTaskStateOutput;
     /** The root directory of the Job Preparation Task on the Compute Node. You can use this path to retrieve files created by the Task, such as log files. */
     taskRootDirectory?: string;
@@ -1248,7 +1422,11 @@ export interface BatchJobPreparationTaskExecutionInfoOutput {
     retryCount: number;
     /** The most recent time at which a retry of the Job Preparation Task started running. This property is set 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. */
     lastRetryTime?: string;
-    /** The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property. */
+    /**
+     * The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property.
+     *
+     * Possible values: "success", "failure"
+     */
     result?: BatchTaskExecutionResultOutput;
 }
 /** Contains information about the container which a Task is executing. */
@@ -1262,7 +1440,11 @@ export interface BatchTaskContainerExecutionInfoOutput {
 }
 /** Information about a Task failure. */
 export interface BatchTaskFailureInfoOutput {
-    /** The category of the Task error. */
+    /**
+     * The category of the Task error.
+     *
+     * Possible values: "usererror", "servererror"
+     */
     category: ErrorCategoryOutput;
     /** An identifier for the Task error. Codes are invariant and are intended to be consumed programmatically. */
     code?: string;
@@ -1280,7 +1462,11 @@ export interface BatchJobReleaseTaskExecutionInfoOutput {
     startTime: string;
     /** The time at which the Job Release Task completed. This property is set only if the Task is in the Completed state. */
     endTime?: string;
-    /** The current state of the Job Release Task on the Compute Node. */
+    /**
+     * The current state of the Job Release Task on the Compute Node.
+     *
+     * Possible values: "running", "completed"
+     */
     state: BatchJobReleaseTaskStateOutput;
     /** The root directory of the Job Release Task on the Compute Node. You can use this path to retrieve files created by the Task, such as log files. */
     taskRootDirectory?: string;
@@ -1292,7 +1478,11 @@ export interface BatchJobReleaseTaskExecutionInfoOutput {
     containerInfo?: BatchTaskContainerExecutionInfoOutput;
     /** Information describing the Task failure, if any. This property is set only if the Task is in the completed state and encountered a failure. */
     failureInfo?: BatchTaskFailureInfoOutput;
-    /** The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property. */
+    /**
+     * The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property.
+     *
+     * Possible values: "success", "failure"
+     */
     result?: BatchTaskExecutionResultOutput;
 }
 /** The Task and TaskSlot counts for a Job. */
@@ -1345,11 +1535,19 @@ export interface BatchJobScheduleOutput {
     readonly lastModified?: string;
     /** The creation time of the Job Schedule. */
     readonly creationTime?: string;
-    /** The current state of the Job Schedule. */
+    /**
+     * The current state of the Job Schedule.
+     *
+     * Possible values: "active", "completed", "disabled", "terminating", "deleting"
+     */
     readonly state?: BatchJobScheduleStateOutput;
     /** The time at which the Job Schedule entered the current state. */
     readonly stateTransitionTime?: string;
-    /** The previous state of the Job Schedule. This property is not present if the Job Schedule is in its initial active state. */
+    /**
+     * The previous state of the Job Schedule. This property is not present if the Job Schedule is in its initial active state.
+     *
+     * Possible values: "active", "completed", "disabled", "terminating", "deleting"
+     */
     readonly previousState?: BatchJobScheduleStateOutput;
     /** The time at which the Job Schedule entered its previous state. This property is not present if the Job Schedule is in its initial active state. */
     readonly previousStateTransitionTime?: string;
@@ -1390,9 +1588,17 @@ export interface BatchJobSpecificationOutput {
     displayName?: string;
     /** Whether Tasks in the Job can define dependencies on each other. The default is false. */
     usesTaskDependencies?: boolean;
-    /** The action the Batch service should take when all Tasks in a Job created under this schedule are in the completed state. 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. */
+    /**
+     * The action the Batch service should take when all Tasks in a Job created under this schedule are in the completed state. 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.
+     *
+     * Possible values: "noaction", "terminatejob"
+     */
     onAllTasksComplete?: OnAllBatchTasksCompleteOutput;
-    /** The action the Batch service should take when any Task fails in a Job created under this schedule. A Task is considered to have failed if it 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. */
+    /**
+     * The action the Batch service should take when any Task fails in a Job created under this schedule. A Task is considered to have failed if it 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.
+     *
+     * Possible values: "noaction", "performexitoptionsjobaction"
+     */
     onTaskFailure?: OnBatchTaskFailureOutput;
     /** The network configuration for the Job. */
     networkConfiguration?: BatchJobNetworkConfigurationOutput;
@@ -1493,9 +1699,17 @@ export interface ExitCodeMappingOutput {
 }
 /** Specifies how the Batch service responds to a particular exit condition. */
 export interface ExitOptionsOutput {
-    /** An action to take on the Job containing the Task, if the Task completes with the given exit condition and the Job's onTaskFailed property is 'performExitOptionsJobAction'. 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). */
+    /**
+     * An action to take on the Job containing the Task, if the Task completes with the given exit condition and the Job's onTaskFailed property is 'performExitOptionsJobAction'. 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).
+     *
+     * Possible values: "none", "disable", "terminate"
+     */
     jobAction?: BatchJobActionOutput;
-    /** An action that the Batch service performs on Tasks that depend on this Task. 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. */
+    /**
+     * An action that the Batch service performs on Tasks that depend on this Task. 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.
+     *
+     * Possible values: "satisfy", "block"
+     */
     dependencyAction?: DependencyActionOutput;
 }
 /**
@@ -1586,15 +1800,23 @@ export interface BatchTaskOutput {
     readonly creationTime?: string;
     /** How the Batch service should respond when the Task completes. */
     readonly exitConditions?: ExitConditionsOutput;
-    /** The current state of the Task. */
+    /**
+     * The current state of the Task.
+     *
+     * Possible values: "active", "preparing", "running", "completed"
+     */
     readonly state?: BatchTaskStateOutput;
     /** The time at which the Task entered its current state. */
     readonly stateTransitionTime?: string;
-    /** The previous state of the Task. This property is not set if the Task is in its initial Active state. */
+    /**
+     * The previous state of the Task. This property is not set if the Task is in its initial Active state.
+     *
+     * Possible values: "active", "preparing", "running", "completed"
+     */
     readonly previousState?: BatchTaskStateOutput;
     /** The time at which the Task entered its previous state. This property is not set if the Task is in its initial Active state. */
     readonly previousStateTransitionTime?: string;
-    /** The command line of the Task. 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://docs.microsoft.com/en-us/azure/batch/batch-compute-node-environment-variables). */
+    /** The command line of the Task. 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://docs.microsoft.com/azure/batch/batch-compute-node-environment-variables). */
     readonly commandLine?: string;
     /** The settings for the container under which the Task runs. 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. */
     readonly containerSettings?: BatchTaskContainerSettingsOutput;
@@ -1647,7 +1869,11 @@ export interface BatchTaskExecutionInfoOutput {
     requeueCount: number;
     /** The most recent time at which the Task has been requeued by the Batch service as the result of a user request. This property is set only if the requeueCount is nonzero. */
     lastRequeueTime?: string;
-    /** The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property. */
+    /**
+     * The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property.
+     *
+     * Possible values: "success", "failure"
+     */
     result?: BatchTaskExecutionResultOutput;
 }
 /** Information about the Compute Node on which a Task ran. */
@@ -1697,7 +1923,11 @@ export interface BatchTaskAddCollectionResultOutput {
 }
 /** Result for a single Task added as part of an add Task collection operation. */
 export interface BatchTaskAddResultOutput {
-    /** The status of the add Task request. */
+    /**
+     * The status of the add Task request.
+     *
+     * Possible values: "success", "clienterror", "servererror"
+     */
     status: BatchTaskAddStatusOutput;
     /** The ID of the Task for which this is the result. */
     taskId: string;
@@ -1733,15 +1963,27 @@ export interface BatchSubtaskOutput {
     containerInfo?: BatchTaskContainerExecutionInfoOutput;
     /** Information describing the Task failure, if any. This property is set only if the Task is in the completed state and encountered a failure. */
     failureInfo?: BatchTaskFailureInfoOutput;
-    /** The current state of the subtask. */
+    /**
+     * The current state of the subtask.
+     *
+     * Possible values: "preparing", "running", "completed"
+     */
     state?: BatchSubtaskStateOutput;
     /** The time at which the subtask entered its current state. */
     stateTransitionTime?: string;
-    /** The previous state of the subtask. This property is not set if the subtask is in its initial running state. */
+    /**
+     * The previous state of the subtask. This property is not set if the subtask is in its initial running state.
+     *
+     * Possible values: "preparing", "running", "completed"
+     */
     previousState?: BatchSubtaskStateOutput;
     /** The time at which the subtask entered its previous state. This property is not set if the subtask is in its initial running state. */
     previousStateTransitionTime?: string;
-    /** The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property. */
+    /**
+     * The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property.
+     *
+     * Possible values: "success", "failure"
+     */
     result?: BatchTaskExecutionResultOutput;
 }
 /**
@@ -1784,9 +2026,17 @@ export interface BatchNodeOutput {
     id?: string;
     /** The URL of the Compute Node. */
     url?: string;
-    /** The current state of the Compute Node. The Spot/Low-priority Compute Node has been preempted. Tasks which were running on the Compute Node when it was preempted will be rescheduled when another Compute Node becomes available. */
+    /**
+     * The current state of the Compute Node. The Spot/Low-priority Compute Node has been preempted. Tasks which were running on the Compute Node when it was preempted will be rescheduled when another Compute Node becomes available.
+     *
+     * Possible values: "idle", "rebooting", "reimaging", "running", "unusable", "creating", "starting", "waitingforstarttask", "starttaskfailed", "unknown", "leavingpool", "offline", "preempted", "upgradingos", "deallocated", "deallocating"
+     */
     state?: BatchNodeStateOutput;
-    /** Whether the Compute Node is available for Task scheduling. */
+    /**
+     * Whether the Compute Node is available for Task scheduling.
+     *
+     * Possible values: "enabled", "disabled"
+     */
     schedulingState?: SchedulingStateOutput;
     /** The time at which the Compute Node entered its current state. */
     stateTransitionTime?: string;
@@ -1835,14 +2085,22 @@ export interface BatchTaskInfoOutput {
     taskId?: string;
     /** The ID of the subtask if the Task is a multi-instance Task. */
     subtaskId?: number;
-    /** The current state of the Task. */
+    /**
+     * The current state of the Task.
+     *
+     * Possible values: "active", "preparing", "running", "completed"
+     */
     taskState: BatchTaskStateOutput;
     /** Information about the execution of the Task. */
     executionInfo?: BatchTaskExecutionInfoOutput;
 }
 /** Information about a StartTask running on a Compute Node. */
 export interface BatchStartTaskInfoOutput {
-    /** The state of the StartTask on the Compute Node. */
+    /**
+     * The state of the StartTask on the Compute Node.
+     *
+     * Possible values: "running", "completed"
+     */
     state: BatchStartTaskStateOutput;
     /** The time at which the StartTask started running. This value is reset every time the Task is restarted or retried (that is, this is the most recent time at which the StartTask started running). */
     startTime: string;
@@ -1858,7 +2116,11 @@ export interface BatchStartTaskInfoOutput {
     retryCount: number;
     /** The most recent time at which a retry of the Task started running. 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. */
     lastRetryTime?: string;
-    /** The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property. */
+    /**
+     * The result of the Task execution. If the value is 'failed', then the details of the failure can be found in the failureInfo property.
+     *
+     * Possible values: "success", "failure"
+     */
     result?: BatchTaskExecutionResultOutput;
 }
 /** An error encountered by a Compute Node. */
@@ -1879,7 +2141,11 @@ export interface BatchNodeEndpointConfigurationOutput {
 export interface InboundEndpointOutput {
     /** The name of the endpoint. */
     name: string;
-    /** The protocol of the endpoint. */
+    /**
+     * The protocol of the endpoint.
+     *
+     * Possible values: "tcp", "udp"
+     */
     protocol: InboundEndpointProtocolOutput;
     /** The public IP address of the Compute Node. */
     publicIPAddress: string;
@@ -1952,7 +2218,11 @@ export interface InstanceViewStatusOutput {
     code?: string;
     /** The localized label for the status. */
     displayStatus?: string;
-    /** Level code. */
+    /**
+     * Level code.
+     *
+     * Possible values: "Error", "Info", "Warning"
+     */
     level?: StatusLevelTypesOutput;
     /** The detailed status message. */
     message?: string;
@@ -1978,6 +2248,8 @@ export type DiskEncryptionTargetOutput = string;
 export type BatchNodePlacementPolicyTypeOutput = string;
 /** Alias for DiffDiskPlacementOutput */
 export type DiffDiskPlacementOutput = string;
+/** Alias for SecurityEncryptionTypesOutput */
+export type SecurityEncryptionTypesOutput = string;
 /** Alias for SecurityTypesOutput */
 export type SecurityTypesOutput = string;
 /** Alias for DynamicVNetAssignmentScopeOutput */
@@ -1990,6 +2262,8 @@ export type NetworkSecurityGroupRuleAccessOutput = string;
 export type IpAddressProvisioningTypeOutput = string;
 /** Alias for ContainerWorkingDirectoryOutput */
 export type ContainerWorkingDirectoryOutput = string;
+/** Alias for ContainerHostDataPathOutput */
+export type ContainerHostDataPathOutput = string;
 /** Alias for AutoUserScopeOutput */
 export type AutoUserScopeOutput = string;
 /** Alias for ElevationLevelOutput */