Azure Local and LocalBox Guide / Start here

L400 edition · Azure landing-zone design mapping · Recorded lab: October 2026 · Identifiers masked

Azure Local with Jumpstart LocalBox

An L400 six-chapter engineering walkthrough: architecture and landing-zone boundaries, validated deployment gates, AKS on Azure Local and NGINX, an Ubuntu VM on Azure Local, and your planned migration with observable success and recovery criteria.

What is Jumpstart LocalBox?

Jumpstart LocalBox is an Azure Arc Jumpstart sandbox for learning and demonstrating Azure Local. It deploys an Azure VM that hosts a nested Azure Local environment, so you can explore the platform without procuring physical Azure Local servers. Azure Local is the infrastructure product; LocalBox is the lab environment used to explore it. “Azure LocalBox” is not the product name used in this guide. See the official LocalBox overview.

Five names, five different responsibilities
Name used in this guide	What it means
Azure Local	The infrastructure platform that runs the local VMs and Kubernetes workloads.
Jumpstart LocalBox; then LocalBox	The educational sandbox. This recorded deployment has two nested Azure Local nodes inside one outer Azure VM.
`LocalBox-Client`	The recorded outer Azure VM's resource name, not a separate product or an Azure Local cluster node.
Azure Arc	The Azure management capabilities connecting the local infrastructure and supported workload resources to Azure; not a general-purpose VPN.
Azure landing zones	The enterprise organization and governance design model, not software installed by LocalBox. This guide maps a proposed target separately from the recorded lab.

Use LocalBox for training, demonstrations, and disposable proof-of-concept exercises. It runs actual Azure Local software in nested VMs, but the two nodes share the outer VM's failure domain. It is not a production deployment or proof of physical high availability. Read how the host, nodes, management services, VMs, and AKS fit together, or use the terminology and acronym reference.

Every stage expanded: execution context, identity/permissions, preflight inputs, control/data flows, operational acceptance, failure diagnosis and recovery boundaries. Open the six-view editable Azure-icon architecture and Microsoft Cloud Adoption Framework (CAF) control mapping. Target landing-zone controls are explicitly separated from the recorded lab.

Lab, not production. Two nested Azure Local nodes share one outer Azure VM. They do not provide physical fault isolation. The single-worker AKS example is intentionally small, not a highly available application platform.

Azure Local and LocalBox overview

Understand the product, the Jumpstart LocalBox sandbox, and the management and workload layers.

Choose the deployment scenario

Separate a nested learning lab from a physical production cluster.

Deploy Azure Local with LocalBox

Prerequisites, Jumpstart LocalBox deployment, Azure Arc onboarding, validation, and readiness gates.

Deploy AKS on Azure Local and NGINX

One worker, the mandatory control plane, complete YAML, and a private CLI tunnel.

Deploy Ubuntu and a web application

Prepare the image, create an Azure Local VM, and install an NGINX example.

Practice VM live migration

Find the current owner, connect to the cluster, and manually move the running VM.

What this edition retains and masks

Account, subscription, tenant, credentials, and billing sections remain in the guide. Their actual values are masked, not silently removed. No masked value is stored in hidden HTML, comments, URLs, metadata, downloads, or original image pixels.

Field retained	Public value	When following the tutorial
Azure account	`[MASKED: account]`	Sign in with your own authorized account.
Subscription name / ID	`[MASKED: subscription]`	Enter your chosen subscription at the prompt.
Microsoft Entra tenant ID	`[MASKED: tenant]`	Enter the tenant that owns your subscription.
Windows / domain administrator	`[MASKED: administrator]`	Use the account authorized for that target.
Administrator password / SSH private key	`[MASKED: credential]`	Supply locally; never paste into a repository or guide.
Actual spend, billing account and entitlement	`[MASKED: billing information]`	Check your own cost analysis, budget and license terms.

Recorded outcomes and honest boundaries

Recorded Azure Local deployment: two connected Arc nodes and completed validation/deployment.
Recorded AKS workload: one Linux worker plus one mandatory control plane; one NGINX replica Ready and private HTTP access.
Recorded VM: an Ubuntu guest on Azure Local with an identity web application and fresh cluster-owner telemetry.
The observed Ubuntu identity application was Python-based. Chapter 5 adds a clearly labeled new reproducible NGINX example; it is not presented as software already installed in the captured lab.
The migration screenshot shows the menu before destination selection. A completed manual migration and an uninterrupted application session have not been demonstrated by that image.

How to use the examples: private values are entered at runtime. Example RFC1918 IP addresses, node names, and generic resource names are instructional and must be reconciled with your own network. Commands are not an instruction to rerun an existing deployment.

Begin with the architecture Review code and privacy policy