Skip to content

Commit 40d7946

Browse files
committed
additional feedback
1 parent d8190df commit 40d7946

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/batch/batch-custom-images.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.date: 05/20/2020
77

88
# Use a managed image to create a pool of virtual machines
99

10-
To create a custom image for your Batch pool's virtual machines (VMs), you can use the [Shared Image Gallery](batch-sig-images.md). We also provide a way to create a custom image with a *managed image* resource.
10+
To create a custom image for your Batch pool's virtual machines (VMs), you can use the [Shared Image Gallery](batch-sig-images.md) to create a managed image. Using just a managed image is also supported, but only for API versions up to and including 2019-08-01.
1111

1212
> [!IMPORTANT]
1313
> In most cases, you should create custom images using the Shared Image Gallery. By using the Shared Image Gallery, you can provision pools faster, scale larger quantities of VMs, and have improved reliability when provisioning VMs. To learn more, see [Use the Shared Image Gallery to create a custom pool](batch-sig-images.md).
@@ -29,7 +29,7 @@ In Azure, you can prepare a managed image from:
2929
- A generalized Azure VM with managed disks
3030
- A generalized on-premises VHD uploaded to the cloud
3131

32-
To scale Batch pools reliably with a custom image, we recommend creating a managed image using *only* the first method: using snapshots of the VM's disks. The following steps show how to prepare a VM, take a snapshot, and create a managed image from the snapshot.
32+
To scale Batch pools reliably with a managed image, we recommend creating the managed image using *only* the first method: using snapshots of the VM's disks. The following steps show how to prepare a VM, take a snapshot, and create a managed image from the snapshot.
3333

3434
### Prepare a VM
3535

articles/batch/batch-sig-images.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Using a Shared Image configured for your scenario can provide several advantages
3737
- **A Shared Image Gallery image**. To create a Shared Image, you need to have or create a managed image resource. The image should be created from snapshots of the VM's OS disk and optionally its attached data disks. For more information, see [Prepare a managed image](#prepare-a-managed-image).
3838

3939
> [!NOTE]
40-
> Your Shared Image must be in the same subscription as the Batch account. Your Shared Image can be in different regions as long as it has replicas in the same region as your Batch account.
40+
> Your Shared Image must be in the same subscription as the Batch account. The image can be in different regions as long as it has replicas in the same region as your Batch account.
4141
4242
## Prepare a managed image
4343

@@ -48,7 +48,7 @@ In Azure, you can prepare a managed image from:
4848
- A generalized on-premises VHD uploaded to the cloud
4949

5050
> [!NOTE]
51-
> Currently, Batch only supports managed images. You can't create a custom image pool from a specialized image at this time.
51+
> Currently, Batch only supports generalized Shared Images. You can't create a custom image pool from a specialized Shared Image at this time.
5252
5353
The following steps show how to prepare a VM, take a snapshot, and create an image from the snapshot.
5454

0 commit comments

Comments
 (0)