What Is Azure Local and Why It Matters
Azure Local — formerly known as Azure Stack HCI — is Microsoft's solution for running Azure services on your own on-premises hardware. It brings the Azure control plane, Azure Arc integration, and a curated set of Azure services directly into your datacentre or edge location, giving you a genuinely hybrid infrastructure without forcing a lift-and-shift to the public cloud.
For organisations in regulated industries, those with data sovereignty requirements, or those running latency-sensitive workloads, Azure Local is a production-grade option that deserves serious consideration in your architecture planning.
Hardware Requirements Before You Download Anything
Before touching the ISO, confirm your hardware meets the baseline requirements. Azure Local requires validated hardware from the Azure Local Catalog — Microsoft maintains a list of certified servers, switches, and storage solutions that have been tested for compatibility. Running Azure Local on uncertified hardware is technically possible but unsupported and not recommended for production.
Minimum requirements for a single-node deployment include a 64-bit processor with second-level address translation, at least 32 GB RAM (64 GB or more recommended for workloads), and NVMe or SSD storage. Network requirements depend on your intended workload density and storage replication configuration.
Where to Find and Download the Azure Local ISO
The Azure Local ISO is available through the Azure portal and through the Microsoft Evaluation Center for trial deployments. Navigate to the Azure portal and search for Azure Local, or go directly to the Microsoft Evaluation Center at microsoft.com/en-us/evalcenter and search for Azure Local. For production deployments, the ISO is tied to your Azure subscription and downloaded through the Azure portal under the Azure Local resource type. You will need an active Azure subscription and the appropriate permissions to initiate the download. The ISO file is substantial — typically several gigabytes — so plan your download around your network bandwidth and use a download manager or the Azure CLI to ensure a clean, verifiable download.
Verifying the Download
Always verify the SHA-256 hash of the downloaded ISO against the value published by Microsoft before proceeding with any installation. A corrupted or tampered ISO will cause unpredictable failures during setup and is a security risk. The hash is published on the same download page alongside the ISO file.
Initial Configuration After Download
Once the ISO is verified, you boot your target hardware from it to begin the Azure Local installation. The setup process installs the Azure Local operating system — a stripped-down, purpose-built OS based on Windows Server — and registers the node with your Azure subscription via Azure Arc.
- Network configuration: Assign management, storage, and compute network adapters correctly during setup — misconfiguration here causes persistent connectivity issues
- Azure registration: You will need your Azure tenant ID and subscription ID during registration
- Storage pool: Azure Local uses Storage Spaces Direct — configure your storage pool after OS installation
- Cluster validation: Run the built-in cluster validation wizard before considering the deployment production-ready
Key Takeaways
- Use only certified hardware from the Azure Local Catalog for production deployments
- Download the ISO via the Azure portal for production or the Evaluation Center for testing
- Always verify the ISO hash before installation
- Register the node with Azure Arc during setup to unlock portal management and policy enforcement
- Complete cluster validation before putting workloads on the system
