Skip to content

Commit 2e19412

Browse files
Merge pull request #271861 from MaryMichael-MS/11AprAvailabilitySet
Updated support information.
2 parents 3f1d9bf + dd3fe21 commit 2e19412

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/migrate/tutorial-migrate-vmware.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: piyushdhore
66
ms.manager: vijain
77
ms.topic: tutorial
88
ms.service: azure-migrate
9-
ms.date: 02/22/2024
9+
ms.date: 04/11/2024
1010
ms.custom: mvc, engagement-fy23
1111
---
1212

@@ -87,7 +87,7 @@ Enable replication as follows:
8787
7. In **Virtual Network**, select the Azure VNet/subnet, which the Azure VMs join after migration.
8888
8. In **Availability options**, select:
8989
- Availability Zone to pin the migrated machine to a specific Availability Zone in the region. Use this option to distribute servers that form a multi-node application tier across Availability Zones. If you select this option, you'll need to specify the Availability Zone to use for each of the selected machine in the Compute tab. This option is only available if the target region selected for the migration supports Availability Zones
90-
- Availability Set to place the migrated machine in an Availability Set. The target Resource Group that was selected must have one or more availability sets in order to use this option.
90+
- Availability Set to place the migrated machine in an Availability Set. The target Resource Group that was selected must have one or more availability sets in order to use this option. Availability Set with Proximity Placement Groups is supported.
9191
- No infrastructure redundancy required option if you don't need either of these availability configurations for the migrated machines.
9292
9. In **Disk encryption type**, select:
9393
- Encryption-at-rest with platform-managed key

0 commit comments

Comments
 (0)