Skip to content

Commit 493d2ac

Browse files
authored
Apply pencil edits for blocking issues from PR review
1 parent 71d8ebe commit 493d2ac

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

articles/batch/batch-custom-image-pools-to-azure-compute-gallery-migration-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Migrate Azure Batch Custom Image Pools to Azure Compute Gallery
2+
title: Migrate Azure Batch custom image pools to Azure Compute Gallery
33
description: Learn how to migrate Azure Batch custom image pools to Azure compute gallery and plan for feature end of support.
44
ms.service: batch
55
ms.topic: how-to
@@ -33,7 +33,7 @@ Azure Marketplace image and install software on each compute node after allocati
3333
to more efficiencies in faster compute node to ready state and reproducible workloads. Additionally, you can specify multiple
3434
replicas for the shared image so when you create pools with many compute nodes, provisioning latencies can be lower.
3535

36-
## Migrate Your Eligible Pools
36+
## Migrate your eligible pools
3737

3838
To migrate your Batch custom image pools from managed image to shared image, review the Azure Batch guide on using
3939
[Azure Compute Gallery to create a custom image pool](batch-sig-images.md).

articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
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
33
description: Learn how to migrate Azure Batch pools to the simplified compute node communication model and plan for feature end of support.
44
ms.service: batch
55
ms.topic: how-to
66
ms.date: 03/07/2023
77
---
88

9-
# Migrate Azure Batch pools to the Simplified compute node communication model
9+
# Migrate Azure Batch pools to the simplified compute node communication model
1010

1111
To improve security, simplify the user experience, and enable key future improvements, Azure Batch will retire the classic
1212
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
3434
without user-specified virtual networks are generally unaffected by this change and the Batch service controls the default
3535
communication mode.
3636

37-
## Alternative: Use Simplified Compute Node Communication Model
37+
## Alternative: Use simplified compute node communication model
3838

3939
The simplified compute node communication mode streamlines the way Batch pool infrastructure is managed on behalf of users.
4040
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,
4545
your workflow. For example, autostorage accounts for AppPackages and other storage accounts for resource files or output files
4646
can be scoped appropriately.
4747

48-
## Migrate Your Eligible Pools
48+
## Migrate your eligible pools
4949

5050
To migrate your Batch pools from classic to the simplified compute node communication model, follow this document
5151
from the section entitled

0 commit comments

Comments
 (0)