Azure Local

Azure Local consulting

One practice for the whole life of an Azure Local cluster: deciding whether it fits, designing it, building it, moving workloads onto it and keeping it healthy.

What we do

Scope of the work

  • Decide whether Azure Local fits the workload, against Azure and plain Hyper-V
  • Size machines, storage and network for the workloads you actually run
  • Deploy the cluster through Azure Arc and validate it before handover
  • Migrate virtual machines from Hyper-V or VMware
  • Set up updates, monitoring, backup and a written repair procedure
What you receive
  • A written design with each decision and its reason
  • A deployed, validated cluster registered in your Azure subscription
  • As-built documentation and runbooks your team can operate from

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

Field notes

What we check first.

Fit before hardware

Azure Local is billed per physical core and needs a regular connection to Azure. We check both against your budget and your site before anyone orders servers.

The network decides the schedule

In our experience, failed deployments often trace back to switch configuration, firewall rules or DNS, so we review those before deployment day.

Validated hardware only

The cluster must run on hardware from the Azure Local catalog with matching firmware and drivers. We check the bill of materials against it.

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 Azure Local the same as Azure Stack HCI?

Azure Local is the current name for the product that was called Azure Stack HCI. The machines still run the Azure Stack HCI operating system, and the cluster is managed from Azure through Azure Arc.

Do you work remotely or on site?

Both. Design, deployment through Azure and most operations work are done remotely. Racking, cabling checks and workshops can be done on site in the New York area.

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.