Azure Local

Migration to Azure Local

Moving virtual machines onto Azure Local in planned steps: discovery, replication, a test cutover, a planned cutover window and a way back for every machine.

What we do

Scope of the work

  • Discover the source virtual machines and their dependencies
  • Group machines into migration waves by application
  • Replicate with Azure Migrate or move by export and import where that fits better
  • Run a test cutover and confirm the application with its owner
  • Cut over in an agreed window with a rollback step for each wave
What you receive
  • A wave plan with owners, windows and rollback steps
  • Migrated virtual machines running as Azure Local VMs
  • A cutover record for each wave

Billed at $150.00 per hour. Ask Keith for an estimate.

Field notes

What we check first.

Network first

A migrated machine keeps its IP address only if the same VLAN reaches the new cluster. We confirm that before the first replication.

Generation and boot type

Older virtual machines may need conversion before they can run as Azure Local VMs. We find them in discovery, not at cutover.

Keep the source

The source machine stays powered off and untouched until the owner signs off. That is the rollback.

How an engagement runs

Four steps, written down.

I
Scope

A call with Keith

You describe the goal, the estate and the deadline. Keith turns it into a written scope with an hour estimate at the hourly rate.

II
Design

A written design by Gus

Gus reviews the environment and gives you a written design with each decision and its reason.

III
Build

Hands-on implementation

Gus implements in your tenant and your racks, remotely or on site, with every change logged as it is made.

IV
Hand over

Documents and a named contact

You receive the as-built record and the runbooks. Keith stays on as your account and project manager.

Questions

Asked before every engagement.

Is the migration live?

No. Data replicates while the source keeps running, then there is a short planned outage for the final sync and the switch. We size that window per wave.

Can you migrate from VMware?

Yes. See the VMware to Azure Local page for the specifics of that path.

What does the consulting cost?

Consulting is billed at $150.00 per hour. Keith sends a written hour estimate after the scoping call, and work starts when you approve it.

Rate and contacts

One rate. Two people.

Consulting is billed at $150.00 per hour. Keith runs sales, project management and your account. Gus does the architecture, the design and the implementation.

Hourly rate
$150.00

per consulting hour, for every consulting service

Sales, project management and account management

Keith

keith@apexvanguard.ai
Architecture, design and implementation

Gus

gus@gusitllc.com

Independent practice, not affiliated with Microsoft. Azure Local consulting is part of the infrastructure consulting practice of Gus IT LLC, an independent firm. It is not affiliated with, endorsed by or sponsored by Microsoft Corporation, Dell Technologies, Fortinet or any other vendor named on this site. Microsoft, Azure, Azure Local, Azure Stack HCI, Azure Arc, AKS, Azure Virtual Desktop, Hyper-V and Windows Server are trademarks of Microsoft Corporation. Dell, PowerEdge, PowerSwitch and iDRAC are trademarks of Dell Inc. Microsoft Entra, Active Directory, SQL Server, FSLogix and BitLocker are also trademarks of Microsoft Corporation. Fortinet and FortiGate are trademarks of Fortinet, Inc. VMware and vSphere are trademarks of Broadcom Inc. Kubernetes is a registered trademark of The Linux Foundation. PostgreSQL is a trademark of the PostgreSQL Community Association of Canada. Linux is the registered trademark of Linus Torvalds. All other marks belong to their respective owners and are used for description only. Product capabilities follow each vendor's documentation and change between releases; we confirm the current state during scoping.