When to Choose Azure VMware Solution in AZ-305 Migration Designs
Azure VMware Solution is the migration answer when the scenario is mostly about moving a VMware estate to Azure quickly while preserving the VMware operating model. It is not the answer just because the word "migration" appears, and it is not the same thing as modernizing an application into Azure PaaS.
For AZ-305, read the business constraint first:
- If the workload must move fast with minimal refactoring and the team must keep familiar VMware tools and processes, AVS is a strong candidate.
- If the scenario rewards managed platform features, reduced infrastructure operations, or application redesign, prefer a native Azure VM, PaaS, container, or modernization path.
- If the scenario asks for discovery, readiness, right-sizing, or migration planning, think Azure Migrate first. Azure Migrate can assess the estate and estimate AVS node needs, but it is not the AVS private cloud target.
- If the scenario names HCX, ExpressRoute, or Global Reach, treat them as migration and connectivity design choices. Do not turn them into unconditional requirements unless the scenario requires that pattern.
The major trap is treating AVS as "Azure VMs for VMware." AVS provides a VMware private cloud on dedicated Azure bare-metal infrastructure with familiar VMware components such as vCenter Server, vSAN, vSphere, and NSX. Microsoft manages the AVS infrastructure and VMware software, but the customer still owns workload design, networking, identity, DNS, backup, access, migration execution, and operating decisions inside the environment.
Decision Model
| Scenario clue | Better exam move | Why |
|---|---|---|
| Large VMware estate, tight timeline, minimal refactoring, keep VMware operations | Choose AVS | AVS is built for VMware workload continuity in Azure when refactoring is not the first priority. |
| Application can be redesigned and the goal is managed platform operations | Prefer PaaS, containers, or another modernization path | AVS preserves a VMware operating model; it does not automatically modernize the application. |
| Existing VMs should become Azure IaaS VMs and VMware continuity is not required | Consider native Azure VM migration | Native VM migration usually fits better when the target operating model is Azure IaaS, not VMware private cloud. |
| Need inventory, dependency analysis, readiness, right-sizing, or AVS node estimates | Use Azure Migrate assessment and planning | Azure Migrate is assessment and migration tooling; AVS is a target private cloud platform. |
| Need operational continuity, IP continuity, or a documented VMware migration path | Evaluate HCX and network extension needs | HCX is a documented AVS migration path, but official guidance does not make it mandatory for every migration. |
| Need private connectivity between on-premises, AVS, and Azure VNets | Design the hybrid connectivity path | ExpressRoute and Global Reach are common documented patterns, but avoid saying every migration always requires them. |
Visual Model
Read the diagram from left to right. The decision is not "VMware equals AVS." The decision is whether the migration should preserve the VMware estate, use AVS as the Azure-hosted VMware private cloud, or redirect the workload toward native Azure or managed platform modernization.
Quick Decision Guide
Use this static guide if the interactive decision tree is unavailable:
- Choose AVS when rapid VMware workload relocation, minimal refactoring, and VMware tool continuity are the strongest requirements.
- Do not choose AVS just because the source platform is VMware. If the target operating model should be Azure IaaS, use a native Azure VM migration path.
- Do not choose AVS when the scenario mainly rewards managed platform features, reduced infrastructure administration, or application refactoring. Use the appropriate PaaS, container, or modernization path.
- Use Azure Migrate when the question asks for inventory, readiness, right-sizing, dependency discovery, planning, or estimating AVS node needs.
- Treat HCX as an important documented AVS migration path, especially where continuity matters, but do not claim it is required for every AVS migration.
- Treat ExpressRoute and Global Reach as key documented private connectivity patterns for AVS designs, but avoid unconditional "always required" wording.
- Always include the operating boundary: Microsoft manages the AVS private cloud infrastructure and VMware software; the customer still designs and operates the workloads, network, identity, DNS, backup, access, and migration execution.
Worked Scenario
A manufacturer runs a large VMware estate in an on-premises datacenter. Several business systems must move to Azure before the next datacenter renewal. The application teams cannot refactor the systems in time, and the operations team needs to keep using familiar VMware tools while the migration is underway. The design also needs private connectivity between the datacenter, the AVS private cloud, and Azure VNets that host shared services.
A strong AZ-305 answer is:
- Use Azure Migrate to inventory the VMware environment, assess readiness, support planning, and estimate AVS capacity needs.
- Recommend Azure VMware Solution for the initial migration target because speed, minimal refactoring, and VMware operational continuity are the dominant constraints.
- Plan the private connectivity path between on-premises, AVS, and Azure VNets. ExpressRoute and Global Reach are common documented patterns for this type of design.
- Evaluate HCX or other migration tooling based on the continuity and migration requirements. HCX is a documented AVS path, but it should not be described as mandatory in every AVS scenario.
- Keep modernization as a later or separate decision. AVS can move the estate into Azure, but it does not turn the applications into App Service, AKS, Azure SQL, or another managed platform by itself.
- State the shared-responsibility boundary. Microsoft manages the AVS private cloud infrastructure and VMware software; the customer still owns workload architecture, network design, identity, DNS, backup, access, migration execution, and day-to-day workload operations.
The weaker answer is to pick "Azure VM migration" only because the source machines are virtual machines. That ignores the scenario's strongest clues: minimal refactoring and VMware operating-model continuity.
Exam Nugget
AVS is the "keep VMware while moving to Azure" migration target. Azure Migrate is the assessment and planning tool. HCX is a documented migration path, not a universal requirement. PaaS is the answer when modernization and managed platform operations matter more than VMware continuity.