Azure Local

Azure Local architecture and design

A written design you can build from: cluster size, storage resiliency, network intents, identity, the Azure side and the reasons behind each choice.

What we do

Scope of the work

  • Choose the cluster size and the storage resiliency for your failure tolerance
  • Design management, compute and storage network intents and the switch configuration
  • Plan IP ranges, VLANs, logical networks, DNS and time
  • Design identity, Key Vault, the witness and the Azure resource layout
  • Plan backup, disaster recovery, updates and monitoring from day one
What you receive
  • A design document with a decision record for every choice
  • Network diagrams and a completed deployment parameter sheet
  • A build plan with the validation steps for each stage

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

Field notes

What we check first.

Resiliency is chosen once

The storage resiliency you pick sets how much raw capacity is usable and how many failures the cluster survives. Changing it later means moving data.

Switchless or switched storage

Small clusters can cable storage directly between machines. It saves switches, but it limits how you can add machines later, so we decide it with your growth plan.

The witness

A two-machine cluster needs a witness to keep running when one machine is down. We place it where a single site failure cannot take both.

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.

Do you design for hardware we have not bought yet?

Yes. That is the best time. The design gives you a bill of materials to quote against, and we review the quotes before you order.

Will the design match Microsoft's reference patterns?

We start from Microsoft's documented network reference patterns and record every deviation with its reason.

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.