You might be saying it once but not again: “Goodbye VMware, Hello Azure Local!”. If you’re already in the Microsoft ecosystem, Azure Local has some cool advantages that make it feel like a natural next step.
What’s Azure Local?
- Azure Local is the new name for what was previously called Azure Stack HCI. Microsoft rebranded it in June 2025 to bring together all of its distributed infrastructure solutions under one simpler name Microsoft LearnTierPoint, LLC.
- Behind the scenes, everything stays the same operationally—your clusters, scripts, APIs, PowerShell cmdlets, CLI commands, and operating systems remain unchanged Microsoft Learn.
- But now, Azure Local supports more:
- Disconnected operations (perfect for edge or restricted networks),
- Smaller and larger deployments, and
- New features like deploying with local identity via Key Vault Microsoft LearnMicrosoft Azure.
Why It Counts: Azure Local vs. VMware (and Azure Stack HCI)
If you’re used to VMware, Azure Local brings some attractive benefits:
- Unified control plane
With Azure Arc, your on-prem Azure Local clusters show up like any Azure resource. You manage them with the same tools, APIs, and portal you already use—no separate interface required TierPoint, LLCAndy Syrewicze. - Licensing advantage
If you already have Windows Server Datacenter with Software Assurance, licensing for Azure Local is covered via Azure Hybrid Benefit—saving costs compared to VMware. - Native Azure services on-prem
You don’t run third-party equivalents—Azure Local can host real Azure services like AKS (Kubernetes), AVD (Virtual Desktop), and others locally Andy Syrewicze. - Consistent governance and security
You can apply Azure Policy and Microsoft Defender for Cloud just as you would in Azure—no need to manage separate security policies TierPoint, LLC. - Built for Microsoft environments
Integrates smoothly with Active Directory, Group Policy, PowerShell, Windows Admin Center—no third-party plugins or connectors needed.
Migrating to Azure Local with Azure Migrate
Let’s get practical. What if you’ve got VMs sitting on VMware or Hyper-V and need to bring them over to Azure Local? Azure Migrate has your back—and yes, even locally.
Core Migration Flow (still in preview)
- Azure Migrate is your central hub. You register both the source and target appliances under a project.
- On the source side: deploy a source appliance on VMware or Hyper-V.
- On the target: deploy a target appliance within your Azure Local instance.
- You replicate VM data from your on-prem virtualization host to the Azure Local environment and cut over with minimal downtime Microsoft Learn+1.
This setup preserves control: your data stays local, and the Azure portal handles the migration orchestration.
What’s New (Recent 2025 updates)
Azure Migrate keeps getting better. Here’s what’s landed recently:
- PowerShell tooling for migration—now scriptable, easy to automate Microsoft Learn.
- Diagnostic settings—you can monitor migrations, watch logs, and troubleshoot better Microsoft Learn.
- Linux static IP support and physical sector size selection (512B vs 4K) for disks—handly low-level control Microsoft Learn.
- Improved cleanup for failed replications, better error guidance, stricter IP validations, and portal messages to help with Gen-1 vs Gen-2 VMs Microsoft Learn.
These features make migrations smoother and more transparent.
Example Migration Scenario
Let’s say you’ve got a VMware cluster and want to migrate a VM to Azure Local:
- Deploy appliances:
- Spin up the source migration appliance on your VMware host.
- Stand up the target appliance inside Azure Local.
- Create Azure Migrate project and storage account: This lets your appliances talk and store metadata Microsoft Learn+1.
- Discover and replicate: Discover VMs on your source, replicate them to Azure Local, and choose when to cutover Microsoft Learn+1.
- Verify and finalize: Boot the VM in Azure Local, make sure everything runs, pause replication, and decommission the source VM Microsoft Learn+1.
- Monitor via portal or script: Use PowerShell or the portal diagnostics to track progress or debug issues Microsoft Learn.
Quick Comparison Table
| Feature | VMware/HCI + Azure Local |
|---|---|
| Control Plane | Azure Arc (Unified, Azure Portal) |
| Licensing | Covered via Software Assurance |
| Azure Native Services On-Prem | AKS, AVD, etc. supported |
| Security & Governance | Azure Policy + Defender for Cloud via Arc |
| Migration Tool | Azure Migrate (agentless, preview) |
| Monitoring & Automation | PowerShell + diagnostics available |
Summary
Azure Local—formerly Azure Stack HCI—is more than a new name. It’s Microsoft’s effort to simplify hybrid cloud while packing in features you actually use. You get unified control, cost-efficient licensing, real Azure services on premises, and seamless governance.
Migration is straightforward using Azure Migrate—deploy appliances, replicate VMs, and cut over with minimal downtime. And with new scriptable tools and error-handling enhancements, it’s smoother than ever.
So if you’re ready to trade VMware for a path that aligns with Azure cloud services and infrastructure, Azure Local is a solid bet.
References
- Microsoft’s rename of Azure Stack HCI to Azure Local—no break in functionality or tooling Microsoft LearnTierPoint, LLCExigo Tech.
- Azure Migrate overview for Hyper-V and VMware to Azure Local, migration phases Microsoft Learn+1.
- Migration enhancements via PowerShell, diagnostics, static IP and disk size options, cleanup, and errors Microsoft Learn.
- Details on new Azure Local capabilities (disconnected ops, small form factor, local identity via Key Vault) Microsoft LearnMicrosoft Azure.
- Azure Arc integration, Azure Local benefits for SysAdmins and edge deployments TierPoint, LLCAndy Syrewicze
Discover more from SQLYARD
Subscribe to get the latest posts sent to your email.
