A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
Yes. A separate Azure Migrate replication appliance is required for each isolated VPC if VPC peering (or other network connectivity) is not enabled between them.
Reasoning based on requirements:
- The replication appliance must have network line-of-sight to every source AWS VM that it will replicate.
- Source AWS VMs communicate with the replication appliance over HTTPS 443 (control/orchestration) and TCP 9443 (replication data) inbound.
- The guidance recommends deploying the replication appliance in the same VPC as the source VMs; if it is in a different VPC, the VPCs must be connected via VPC peering.
Since VPCs in this scenario “do not talk to each other” and peering is explicitly not desired, a single appliance cannot reach VMs across those VPC boundaries. Therefore:
- Deploy one replication appliance VM (Windows Server 2022) per VPC that contains servers to be migrated.
- Ensure each appliance meets the hardware/software/networking requirements and can reach Azure over HTTPS 443 outbound.
- Configure security group rules in each VPC so that the local source VMs can reach their local appliance on ports 443 and 9443.
This way, each isolated VPC has its own appliance handling replication for the VMs inside that VPC, without requiring VPC peering.
References: