1
1
---
2
- title : Migrate Azure Batch pools to the Simplified compute node communication model
2
+ title : Migrate Azure Batch pools to the simplified compute node communication model
3
3
description : Learn how to migrate Azure Batch pools to the simplified compute node communication model and plan for feature end of support.
4
4
ms.service : batch
5
5
ms.topic : how-to
6
6
ms.date : 03/07/2023
7
7
---
8
8
9
- # Migrate Azure Batch pools to the Simplified compute node communication model
9
+ # Migrate Azure Batch pools to the simplified compute node communication model
10
10
11
11
To improve security, simplify the user experience, and enable key future improvements, Azure Batch will retire the classic
12
12
compute node communication model on * March 31, 2026* . Learn how to migrate your Batch pools to using the simplified compute
@@ -34,7 +34,7 @@ After *March 31, 2026*, the option to use classic compute node communication mod
34
34
without user-specified virtual networks are generally unaffected by this change and the Batch service controls the default
35
35
communication mode.
36
36
37
- ## Alternative: Use Simplified Compute Node Communication Model
37
+ ## Alternative: Use simplified compute node communication model
38
38
39
39
The simplified compute node communication mode streamlines the way Batch pool infrastructure is managed on behalf of users.
40
40
This communication mode reduces the complexity and scope of inbound and outbound networking connections required in the
@@ -45,7 +45,7 @@ The simplified model also provides more fine-grained data exfiltration control,
45
45
your workflow. For example, autostorage accounts for AppPackages and other storage accounts for resource files or output files
46
46
can be scoped appropriately.
47
47
48
- ## Migrate Your Eligible Pools
48
+ ## Migrate your eligible pools
49
49
50
50
To migrate your Batch pools from classic to the simplified compute node communication model, follow this document
51
51
from the section entitled
0 commit comments