Reference architecture

Reference architecture: sovereign landing zone on Azure Local

A governed Azure side and a controlled on-premises side, with a documented boundary between them: which data stays, which metadata leaves, who holds the keys and who can log in.

What this architecture covers

Design decisions

  • A landing zone with policies that restrict regions and services
  • Encryption keys under your control
  • A written record of every data flow that crosses the boundary
  • Privileged access that is time-bound, approved and logged
  • Evidence collection built into operations
What you receive
  • The architecture mapped to your requirements
  • Policies and structure as code
  • An access and audit procedure

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

Diagram

The layers, top to bottom.

GovernanceManagement groupsPolicyAudit logsAzure sideArc resourcesKey managementMonitoringBoundaryDocumented data flowsFirewallData planeVirtual machinesAKSPrivate AIPlatformAzure Local clusterAccessPrivileged accessBreak glass
Field notes

What we check first.

The boundary is the design

Sovereignty is decided at the line between your site and the cloud. We draw it and document it.

Metadata counts

Resource names, logs and telemetry are data too. We list what leaves.

Disconnected is a separate decision

A fully disconnected design is possible for eligible customers and costs more. We compare 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.

Is this an official Microsoft architecture?

No. It is our reference design, built from Microsoft's published landing zone and sovereignty guidance and our own experience.

Can it satisfy a specific regulator?

The design is mapped to the text you must meet. The formal opinion comes from your auditor.

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.