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.363 votes
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.
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.37 votes
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.
If the managed resources for a vm image are missing or the node type doesnt support a requested feature (e.g. managed disk on A series vm) then the pool keeps trying to add nodes eventually hitting resize timeout, after timeout it starts again. Its not easy to debug those situations and a better error report would be very useful.2 votes
The idea I have in mind is to use Azure Batch to export a >100 TB Azure Table, at a much faster rate than Azure Data Factory can manage.
Azure Tables is quoted to cope with 10,000s of simultaneous requests. To maximize my dev velocity, I would create millions of lightweight tasks and let Azure Batch runtime handle all the scheduling details.
But there is a limit of 4 concurrent tasks per core so this would make for extremely underutilized nodes and long runtime.2 votes
- Don't see your idea?