Azure Batch pools without public IP addresses (classic) are retiring on March 31st, 2023

[azure-deprecation-automation]

Azure Batch pools without public IP addresses (classic) are retiring on March 31st, 2023

Deprecation ID: 5e65941b-dc57-4573-9732-44525945a13e
Deadline: Mar 31, 2023
Impacted Services:

• Azure Batch

More information:

• Announcement
• Migration Guide

Notice

Here's the official report from Microsoft:

Azure Batch pools without public IP addresses (classic) has been updated to simplified compute node communication pools without public IP addresses, because we launched a Simplified compute node communication model for Batch to improve security and simplify the user experience. Batch pools without public addresses (classic) will be retired on 31 March 2023. Please transition to using Simplified compute node communication pools without public IP addresses.

Timeline

Phase	Date	Description
Announcement	Oct 07, 2022	Deprecation was announced
Deprecation	Mar 31, 2023	The functionality of the existing pool in that configuration may break, such as scale out operations, or may be actively scaled down to zero at any point in time.

Impact

Azure Batch pools without public IP addresses (classic) are retiring on March 31st, 2023 and migration to simplified compute node communication pools without public IP addresses in Azure Batch is required.

Required Action

A migration guide is provided here.

Here's the official report from Microsoft:

To avoid disruptions to your workflow, follow these steps to transition to Simplified compute node communication pools without public IP addresses before 31 March 2023. After that, we will stop supporting Batch pools without public IP addresses (classic). The functionality of the existing pool in that configuration may break, such as scale out operations, or may be actively scaled down to zero at any point in time.

Contact

You can get in touch through the following options:

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

[azure-deprecation-automation]

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