VMware to Azure Migration Center¶

The definitive resource for migrating from on-premises VMware/vSphere to Microsoft Azure -- Azure VMware Solution (AVS), Azure IaaS, and CSA-in-a-Box as your data analytics landing zone.

Who this is for¶

This migration center serves federal CIOs, CTOs, infrastructure architects, cloud engineers, and platform teams who are evaluating or executing a migration from VMware/vSphere to Azure. Whether you are reacting to Broadcom's acquisition-driven pricing changes, pursuing cloud-native modernization, or executing an Azure-first strategy, these resources provide the business case, technical guidance, and step-by-step tutorials to migrate confidently.

Primary audiences:

• Executive decision-makers (CIO, CTO, CFO): strategic brief, TCO analysis, decision framework
• Infrastructure architects: feature mapping, networking migration, storage migration, DR patterns
• Cloud engineers: HCX tutorials, Azure Migrate walkthroughs, Bicep/CLI deployment guides
• Security and compliance teams: security migration, federal compliance, Defender integration
• Data platform teams: how CSA-in-a-Box modernizes VM-based data workloads post-migration

The Broadcom forcing function¶

In November 2023, Broadcom completed its $69 billion acquisition of VMware. The consequences for VMware customers have been immediate and severe:

• Perpetual licenses eliminated -- all customers forced to subscription-only
• Product consolidation -- 80+ SKUs collapsed to 4 bundles requiring purchase of capabilities many customers do not need
• Price increases of 2x to 12x documented across the customer base
• Partner ecosystem disrupted -- channel partner program restructured, many partners de-authorized
• Support quality concerns -- reduced support staff, longer resolution times reported
• 500,000+ affected organizations worldwide

This is the single largest forcing function in enterprise infrastructure since the mainframe-to-client-server transition. Every organization running VMware must evaluate its options.

Quick-start decision matrix¶

Migration path decision matrix¶

The fundamental decision is which migration path to use. Most organizations use a combination.

flowchart TD
    A[VMware Workload Assessment] --> B{VMware-dependent?}
    B -->|Yes - vSphere APIs, NSX rules| C[AVS Lift-and-Shift]
    B -->|No| D{Data/Analytics workload?}
    D -->|Yes - DB, ETL, BI| E[Modernize to PaaS via CSA-in-a-Box]
    D -->|No - Standard VM| F{Performance-sensitive?}
    F -->|Yes| G[Azure IaaS - Dedicated Host]
    F -->|No| H[Azure IaaS - Standard VM]
    C --> I[Post-Migration: Evaluate re-platform over time]
    E --> J[Fabric + Databricks + ADF + Power BI]
    G --> K[Azure VM with Premium SSD / Ultra Disk]
    H --> L[Azure VM with auto-scaling]

Strategic resources¶

Documents providing the business case, cost analysis, and strategic framing for decision-makers.

Technical references¶

Migration guides¶

Domain-specific deep dives covering every aspect of a VMware-to-Azure migration.

Tutorials¶

Hands-on, step-by-step walkthroughs for common migration scenarios.

Government and federal¶

How CSA-in-a-Box fits¶

CSA-in-a-Box is the data and analytics landing zone for your VMware-to-Azure migration. While AVS and Azure Migrate handle infrastructure migration (moving VMs), CSA-in-a-Box modernizes the data workloads running on those VMs into cloud-native Azure services.

What CSA-in-a-Box provides post-migration¶

Architecture -- infrastructure migration meets data modernization¶

flowchart LR
    subgraph OnPrem["On-Premises VMware"]
        VP[vSphere/vCenter]
        NSX[NSX Networking]
        VSAN[vSAN Storage]
        DBVMs[Database VMs]
        ETLVMs[ETL Server VMs]
        RPTVMs[Reporting VMs]
    end

    subgraph Azure["Azure Landing Zone"]
        subgraph Infra["Infrastructure (AVS / IaaS)"]
            AVS[Azure VMware Solution]
            AVM[Azure Virtual Machines]
        end
        subgraph CSA["CSA-in-a-Box Data Platform"]
            FAB[Microsoft Fabric]
            DBX[Databricks]
            ADF[Azure Data Factory]
            PBI[Power BI]
            PUR[Microsoft Purview]
            AOI[Azure OpenAI / AI Foundry]
        end
    end

    VP -->|HCX / Azure Migrate| AVS
    VP -->|Azure Migrate| AVM
    NSX -->|Re-architect| Azure
    VSAN -->|Migrate| Azure
    DBVMs -->|Modernize| FAB
    ETLVMs -->|Modernize| ADF
    RPTVMs -->|Modernize| PBI

CSA-in-a-Box compliance coverage¶

For migrated data workloads, CSA-in-a-Box provides machine-readable compliance mappings:

• FedRAMP High: csa_platform/csa_platform/governance/compliance/nist-800-53-rev5.yaml
• CMMC 2.0 Level 2: csa_platform/csa_platform/governance/compliance/cmmc-2.0-l2.yaml
• HIPAA Security Rule: csa_platform/csa_platform/governance/compliance/hipaa-security-rule.yaml

Migration timeline overview¶

gantt
    title Typical VMware-to-Azure Migration (24-36 weeks)
    dateFormat  YYYY-MM-DD
    section Discovery
    VMware inventory and assessment     :a1, 2026-06-01, 4w
    section Landing Zones
    Deploy AVS / IaaS / CSA-in-a-Box    :a2, 2026-06-15, 4w
    section Infrastructure Migration
    AVS migration (HCX)                 :a3, after a2, 8w
    Azure IaaS migration (Azure Migrate):a4, after a2, 10w
    section Data Modernization
    Database and ETL modernization      :a5, after a3, 10w
    section Networking
    NSX to Azure networking cutover     :a6, after a3, 4w
    section Validation
    Parallel run and decommission       :a7, after a5, 8w

Related migration centers¶

Last updated: 2026-04-30 Maintainers: CSA-in-a-Box core team