Muokkaa

Jaa

Migrate Batch account certificates to Azure Key Vault

  • Artikkeli

On February 29, 2024, the Azure Batch account certificates feature will be retired. Learn how to migrate your certificates on Azure Batch accounts using Azure Key Vault in this article.

About the feature

Certificates are often required in various scenarios such as decrypting a secret, securing communication channels, or accessing another service. Currently, Azure Batch offers two ways to manage certificates on Batch pools. You can add certificates to a Batch account or you can use the Azure Key Vault VM extension to manage certificates on Batch pools. Only the certificate functionality on an Azure Batch account and the functionality it extends to Batch pools via CertificateReference to Add Pool, Patch Pool, Update Properties and the corresponding references on Get and List Pool APIs are being retired. Additionally, for Linux pools, the environment variable $AZ_BATCH_CERTIFICATES_DIR will no longer be defined and populated.

Feature end of support

Azure Key Vault is the standard, recommended mechanism for storing and accessing secrets and certificates across Azure securely. Therefore, on February 29, 2024, we'll retire the Batch account certificates feature in Azure Batch. The alternative is to use the Azure Key Vault VM Extension and a user-assigned managed identity on the pool to securely access and install certificates on your Batch pools.

After the certificates feature in Azure Batch is retired on February 29, 2024, a certificate in Batch won't work as expected. After that date, you'll no longer be able to add certificates to a Batch account or link these certificates to Batch pools. Pools that continue to use this feature after this date may not behave as expected such as updating certificate references or the ability to install existing certificate references.

Alternative: Use Azure Key Vault VM extension with pool user-assigned managed identity

Azure Key Vault is a fully managed Azure service that provides controlled access to store and manage secrets, certificates, tokens, and keys. Key Vault provides security at the transport layer by ensuring that any data flow from the key vault to the client application is encrypted. Azure Key Vault gives you a secure way to store essential access information and to set fine-grained access control. You can manage all secrets from one dashboard. Choose to store a key in either software-protected or hardware-protected hardware security modules (HSMs). You also can set Key Vault to autorenew certificates.

For a complete guide on how to enable Azure Key Vault VM Extension with Pool User-assigned Managed Identity, see Enable automatic certificate rotation in a Batch pool.

FAQs

  • Do CloudServiceConfiguration pools support Azure Key Vault VM extension and managed identity on pools?

    No. CloudServiceConfiguration pools will be retired on the same date as Azure Batch account certificate retirement on February 29, 2024. We recommend that you migrate to VirtualMachineConfiguration pools before that date where you're able to use these solutions.

  • Do user subscription pool allocation Batch accounts support Azure Key Vault?

    Yes. You may use the same Key Vault as specified with your Batch account as for use with your pools, but your Key Vault used for certificates for your Batch pools may be entirely separate.

  • Are both Linux and Windows Batch pools supported with the Key Vault VM extension?

    Yes. See the documentation for Windows and Linux.

  • Can you update existing pools with a Key Vault VM extension?

    No, these properties aren't updateable on the pool. You need to recreate pools.

  • How do I get references to certificates on Linux Batch Pools since $AZ_BATCH_CERTIFICATES_DIR will be removed?

    The Key Vault VM extension for Linux allows you to specify the certificateStoreLocation, which is an absolute path to where the certificate are stored. The Key Vault VM extension will scope certificates installed at the specified location with only superuser (root) privileges. You need to make sure that your tasks run elevated to access these certificates by default, or copy the certificates to an accessible directly and/or adjust certificate files with proper file modes. You can run such commands as part of an elevated start task or job prep task.

  • How do I install .cer files that don't contain private keys?

    Key Vault doesn't consider these files to be privileged as they don't contain private key information. You can install .cer files using either of the following methods. Use Key Vault secrets with appropriate access privileges for the associated User-assigned Managed Identity and fetch the .cer file as part of your start task to install. Alternatively, store the .cer file as an Azure Storage Blob and reference as a Batch resource file in your start task to install.

  • How do I access Key Vault extension installed certificates for task-level nonadmin autouser pool identities?

    Task-level autousers are created on-demand and can't be predefined for specifying into the accounts property in the Key Vault VM extension. You'll need a custom process that exports the required certificate into a commonly accessible store or ACLs appropriately for access by task-level autousers.

  • Where can I find best practices for using Azure Key Vault?

    See Azure Key Vault best practices.

Next steps

For more information, see Key Vault certificate access control. For more information about Batch functionality related to this migration, see Azure Batch Pool extensions and Azure Batch Pool Managed Identity.