Skip to content
This repository has been archived by the owner on Mar 29, 2023. It is now read-only.

Azure Batch Certificates are retiring on February 29th, 2024 #269

Open
azure-deprecation-automation opened this issue Oct 26, 2022 · 1 comment
Labels
area:feature area:api-endpoint All issues related to notices that are applicable to features cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:batch verified All notices that are verified by an official communication
Milestone

Comments

@azure-deprecation-automation

Azure Batch Certificates are retiring on February 29th, 2024

Deprecation ID: 5e784700-0128-4b07-8865-4b73ff2d8a1a
Deadline: Feb 29, 2024
Impacted Services:

  • Azure Batch

More information:

Notice

Here's the official report from Microsoft:

As part of our efforts to modernize Batch to use the latest standard and secure Azure technologies and to improve composability with other offerings in the Azure ecosystem, we’ll retire Batch Certificates on 29 February 2024. Please transition to Azure Key Vault as soon as possible to more quickly realize the security and composability benefits.

Timeline

Phase Date Description
Announcement Oct 07, 2022 Deprecation was announced
Deprecation Feb 29, 2024 Functionality may cease to work properly and requests to create and/or resize pools with certificates will be rejected.

Impact

Azure Batch Certificates are retiring on February 29th, 2024 and migration to Azure Key Vault is required.

Required Action

A migration guide is provided here.

Here's the official report from Microsoft:

Follow these steps to transition using Azure Key Vault before 29 February 2024. After that, the Certificate functionality may cease to work properly and requests to create and/or resize pools with certificates will be rejected.

Contact

You can get in touch through the following options:

  • Contact Azure support (link).
  • Get answers from Microsoft Q&A (link).
@azure-deprecation-automation azure-deprecation-automation added area:feature area:api-endpoint All issues related to notices that are applicable to features cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:batch verified All notices that are verified by an official communication labels Oct 26, 2022
@azure-deprecation-automation azure-deprecation-automation added this to the 2024 milestone Oct 26, 2022
@azure-deprecation-automation
Copy link
Author

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.

@azure-deprecation azure-deprecation locked and limited conversation to collaborators Oct 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:feature area:api-endpoint All issues related to notices that are applicable to features cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:batch verified All notices that are verified by an official communication
Projects
None yet
Development

No branches or pull requests

1 participant