Community

Community

Loading...

67 Ideas

Support Managed Service Identity

We made application that uses Managed Service Identity.It's easy and friendly way to access Azure Key Vault that contains some secrets.Actually, Azure Batch is not support Managed Service Identity.In this situation, We have to make another application between MSI enabled environment (Azure VM, Web Apps) and disabled environment (Azure Batch).We don't want writing secrets in application package, environment variables and clear text configuration.We want strongly Managed Service Identity in Azure Batch.

Company Response

2021-05-20 Update: This feature is GA. 2021-02-17 Update: This feature is now in public preview in select regions. Please see https://docs.microsoft.com/azure/batch/managed-identity-pools.Prior update: We appreciate everyone's patience in this feature ask. There was quite a bit of complexity across different teams that needed to be resolved before we could begin. Although we have no ETA to share at this time, implementation of this feature has begun.

Support on Premise Batch Nodes

It would be great to have support for on-premise nodes to support hybrid workloads. This could help with connectivity issues for specific types of specialized data sources. Having a Batch Agent that could be installed on any server so it can register in a pool and be sent work would be really valuable.

Need reimage support on VirtualMachineConfiguration-based pool

Hi Batch Team, we would like to have reimage support on VirtualMachineConfiguration-based pools as well. We know that currently it is supported on CloudServiceConfiguration-based pools. This would greatly reduce the effort to maintain the nodes in the pool as we want to regularly reimage the nodes to keep them healthy without deleting the pool and recreating again. Thanks so much!

Jobs of equal priority should be executed in submission order

If I have a fixed number of dedicated VMs, then it is important that queued jobs run in submission order. Sure I could use the priority to achieve this, but then I can't use priority for real business use case prioritisation. Sure I could reserve priority ranges, but this is getting complicated when it should just process them in submission order.

Allow to apply autoscale formula more frequent then a 5 min

Allow Azure Batch to access a locked down Storage Account

Currently when using a storage account for persisting job output this storage account can not be locked down by using the Firewall and/or Private Endpoint/VNET service endpoint. Therefore the security of the data depends solely on the secrecy of the access keys.If Azure Batch would have VNET integration or similar capability we would be able to add an additional layer of security. An alternative would be if Azure Batch is a 'trusted service' for the storage account. (https://docs.microsoft.com/en-in/azure/storage/common/storage-network-security#trusted-microsoft-services)

All Ideas

Deploy certificate from Azure Key Vault to compute node

Rather than having to associate a certificate with a pool, being able to associate a certificate in a Key Vault that's been created with the -EnabledForDeployment flag would help centralize management of certificates being deployed to both VM's and Batch nodes.

Company Response

2021-02-17 Update: VM extensions on Batch pools is now available. KeyVaultExtension sill require Managed Identity support which is available as public preview in select regions. Please see https://docs.microsoft.com/azure/batch/create-pool-extensions.Prior update: KeyVault support will be coming as part of a larger feature on pools alongside Managed Identity.

Option to base Pool on job topology rather than VM Type

Have the option to specify on the job/task level the CPU, Memory, Disk, network, optional GPUs topology and have the Batch service select the best VM type based on price (OD, Azure Spot) and/or capacity/performance rather than asking the user to specify the VM type upfront

Add support for ceil, round, floor functions in auto-scaling formula

Auto-scaling formulas should add support for these rounding functions:round()ceil()floor()

Azured Batch Job Scheduling: Custom Scheduling

Currently, Azure batch job scheduling allows for scheduling with a recurrence interval. However, I have customer requests where they would like to run Azure Batch jobs on a specific day of each month, year around. The current recurrence interval settings are too stringent to be able to do this easily. Ideally, this feature would allow for custom schedules to accommodate a wide variety of scheduling needs.

Filters

Quick links