Azure Batch updates

Since the previous update, we have added the following capabilities to Azure Batch:​ * ​**Custom images and virtual networks** * Batch already supported custom images and virtual networks, but now a "User Subscription" Batch account is no longer required to create a pool that's created through a custom VM image or references a virtual network. You can use the default "Batch service" Batch account. * Because "Batch Service" accounts can use custom images and virtual networks, you can use custom images and virtual networks in conjunction with low-priority VMs. * Custom images are created via image resources instead of blob VHD files. Batch uses managed disks to create the pool VMs and therefore uses an image resource. This means that there is no limit to the number of VMs in a pool created through a custom image. It also means that the multiple copies of the VHD blob for large pools are no longer required. Custom image pools are much easier to create and scale. [Updated documentation ](https://docs.microsoft.com/azure/batch/batch-custom-images)is available. * Note that to use custom images or virtual networks, you need to use Azure Active Directory authentication. Authentication via account name and key will not work. * ​**Batch low-priority VMs** * Support for low-priority VMs has moved from public preview to GA. Note that preview pricing is still in effect for a few months. It will move to regional pricing—the same as dedicated VMs. This might cause a slight increase in pricing, depending on region. * **Batch rendering platform** * The ability to get Batch pools with pre-installed rendering applications and pay for those applications by the minute is GA. See the [rendering platform documentation ](https://docs.microsoft.com/azure/batch/batch-rendering-service)for more information. * **Containers** * You can create Batch container pools and execute container image tasks. When a pool is created, one or more container images can be specified to copy down to the VM. When a task is run, a container image is specified and container run options can be provided. Task environment variables and folders are mapped to the container. Pool virtual machine configuration has a [new container configuration](https://docs.microsoft.com/rest/api/batchservice/pool/add#definitions%5Fcontainerconfiguration). New [container settings](https://docs.microsoft.com/rest/api/batchservice/Task/Add#definitions%5Ftaskcontainersettings) are available on a Batch task. For Windows, the "Windows Server 2016 with Containers" Azure Marketplace image is used. * **Azure Hybrid Use Benefit** * You can create Batch Windows virtual machine pools and specify that [Azure Hybrid Use Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/) licensing is used. When Azure Hybrid Use Benefit is specified, a discount is applied to the VM price. A [new license type property](https://docs.microsoft.com/rest/api/batchservice/Pool/Add#definitions%5Fvirtualmachineconfiguration) has been added to the virtual machine configuration. * **Pool VM data disks** * You can attach one or more empty data disks to virtual machine pool VMs by using a new [data disk configuration](https://docs.microsoft.com/rest/api/batchservice/Pool/Add#definitions%5Fdatadisk) that is part of the virtual machine configuration. * **New VM sizes** * Batch supports the recently added Dv3 and Ev3 sizes. Note that currently, these VM sizes are available only in [some regions](https://azure.microsoft.com/regions/services/). For a summary of all API updates, see the following documentation: * [REST API versions](https://docs.microsoft.com/rest/api/batchservice/batch-service-rest-api-versioning) * [C# Client API versions](https://github.com/Azure/azure-sdk-for-net/blob/psSdkJson6/src/SDKs/Batch/DataPlane/changelog.md) * Batch * Features * [ Batch](https://azure.microsoft.com/en-gb/services/batch/)