Azure Batch pools from Classic to Simplified compute node communication model

Anuja Vishwanatulawar 1 Reputation point
2024-11-14T20:46:49.21+00:00

We have received the Microsoft service health advisory regarding Transition Azure Batch pools to the Simplified compute node communication model by 31 March 2026 and currently we have some of the batch pools in Classic and for the same we have below queries.

  1. What will be the impact if we update the Node communication mode from Classic to Simplified in Batch Pool?
  2. What will be the downtime required to perform the activity?
  3. Some of the Batch pools in our environment having the Node communication mode mentioned as N/A. Will the batch pools get auto updated to Simplified Mode or we need to update before 31st March 2026?
  4. In case if we haven't update the node communication mode from classic to simplified before 31st March 2026, what will be the impact to the batch pools from 1st April 2026
Azure Batch
Azure Batch
An Azure service that provides cloud-scale job scheduling and compute management.
348 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Akshay kumar Mandha 1,655 Reputation points Microsoft Vendor
    2024-11-15T06:20:35.22+00:00

    Hi Anuja Vishwanatulawar,
    Welcome to the Microsoft Q&A Platform. Thank you for posting your query here.

    Based on your query, when migrating the classic to simplified impact and downtime mentioned below
    While updating the node communication mode from Classic to Simplified in a Batch Pool advantage is reduces networking complexity by requiring fewer inbound connections and simplifying security configurations. It also improves control over data flow, as no outbound communication to Azure Storage is needed.

    For downtime, you need to scale the Batch pool down to zero nodes, migrate to the simplified mode, and then scale it back up. The downtime will vary based on your specific setup but will generally involve some temporary disruption during the scale-down and scale-up processes. Make sure Test the new mode with a small workload first, have a backup and rollback plan. After migration, monitor the system to address any issues quickly

    Please refer below document for more information. If you are already familiar with it, that's great.
    Use simplified compute node communication
    Migrate Azure Batch pools to the simplified compute node communication model

    As you ask another query, some of the nodes are marked as N/A. Those pools must be manually updated to the simplified mode before this date.

    In case of not updating, the classic compute node communication mode before the date it will be retired. which means batch pools using this mode will stop working properly, leading to service disruptions. Any new features or updates won't be compatible with the classic mode, limiting your ability to take advantage of improvements. The simplified communication model also offers better security, and continuing with the classic mode could leave your pools exposed to vulnerabilities. Additionally, the classic mode requires more complex networking setups, making it harder to manage and maintain compared to the simplified version.

    If my information is helpful, could you please accepting the answer on my post and "Upvote" it👍answer for other community members reference with the same concern can benefitUser's image


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.