Cloud Service configuration pools in Azure Batch is retiring on 29 February 2024

[azure-deprecation-automation]

Cloud Service configuration pools in Azure Batch is retiring on 29 February 2024

Deadline: Feb 29, 2024
Impacted Services:

• Azure Cognitive Services

More information:

• https://azure.microsoft.com/en-au/updates/azure-batch-cloudserviceconfiguration-pools-will-be-retired-on-29-february-2024/

Notice

Here's the official report from Microsoft:

Batch pools can currently be created using either CloudServiceConfiguration or VirtualMachineConfiguration. CloudServiceConfiguration does not provide access to all Batch features and is not being enhanced with new features. Moving to use ‘VirtualMachineConfiguration’ will enable the use of all Batch features including an expanded selection of VM series, containers and enabling disk encryption.

Timeline

Phase	Date	Description
Announcement	Feb 22, 2021	Deprecation was announced
Deprecation	Feb 29, 2024	You will not be able to create new CloudServiceConfiguration pools or add new nodes to existing pools

Impact

You will not be able to create new CloudServiceConfiguration pools or add new nodes to existing pools.

Required Action

Here's the official report from Microsoft:

Start using VirtualMachineConfiguration before 29 February 2024 to avoid disruption to your applications. After 29 February 2024, you will not be able to create new ‘CloudServiceConfiguration’ pools or add new nodes to existing pools.

Information about how to update your configuration and the differences between the two configurations is available in the Batch documentation.

Contact

You can get in touch through the following options:

• Get answers from Microsoft Q&A (link).
• Contact Azure support (link).

[azure-deprecation-automation]

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