Skip to main content

Hardware Requirements

Runbook Azure

DOCUMENT CATEGORY: Runbook SCOPE: Hardware specifications for Azure Local PURPOSE: Define hardware requirements for cluster deployment MASTER REFERENCE: Microsoft Learn - Hardware Requirements

Status: Active


Overview​

This document defines hardware requirements and specifications for Azure Local cluster deployments. It covers:

  • Supported Hardware Platforms - Dell integrated systems and validated nodes
  • Minimum Requirements - CPU, memory, storage, and network specifications
  • Firmware Baselines - Required BIOS, iDRAC, NIC, and controller versions
  • Hardware Discovery - Automated inventory collection via iDRAC Redfish API
  • Node Inventory Worksheets - Per-site hardware documentation
Azure Local Cloud Standard

Azure Local Cloud deploys Dell AX-series integrated systems for Azure Local. All hardware must meet Microsoft Azure Local certification requirements.


Supported Hardware Platforms​

Dell Integrated Systems (AX-Series)​

Dell AX-series nodes are purpose-built for Azure Local with pre-validated configurations:

ModelCPUMax RAMStorageNetworkUse Case
Dell AX-760Intel Xeon Scalable 5th Gen4TBNVMe + SSD4x 100GbEGeneral purpose
Dell AX-770Intel Xeon Scalable 5th Gen4TBNVMe + SSD4x 100GbEHigh-performance

Minimum Hardware Requirements​

Azure Local System Requirements​

Microsoft publishes the following minimums. Microsoft Support may only be provided for Azure Local running on hardware in the Azure Local catalog. The "Cloud Standard baseline" column is the sizing this site assumes for production clusters, which is higher than the Microsoft minimum.

ComponentMicrosoft minimumCloud Standard baselineNotes
Machines per instance1 to 16 (hyperconverged). Up to 64 for disaggregated (SAN)2 to 16Single-node is a supported size, with no node-level failover. All machines must match (model, processor, NICs, drive count and type)
CPU64-bit Intel Nehalem grade or AMD EPYC or later with SLAT16+ cores per node, 32+ recommendedProcessor properties (family, clock, core and thread counts) must match across nodes at deployment
Memory32 GB per machine, ECC128 GB or more per node, 256+ GB recommendedAdd capacity for Arc VM management and workloads
Boot drive200 GB480+ GB SSD400 GB or more for machines with more than 768 GB RAM. BOSS card or M.2 recommended
Data drivesAt least 2 drives per machine, 500 GB or more each4+ NVMeAll-flash recommended. Same count, type, capacity, and firmware at deployment
Host network adaptersAt least 2 adapters from the Windows Server Catalog, qualified for the traffic type they carry (management, compute, storage). Inbox drivers are not supported4+ NICsRDMA-capable adapters for the storage intent. Intent patterns use 2, 4, 6 or 8 ports per node
TPM, Secure Boot, BIOSTPM 2.0 present and enabled, Secure Boot enabled, Intel VT or AMD-V onSameRequired for deployment

Maximums: 512 logical processors per host, 24 TB RAM per host, and 2,048 virtual processors per host. GPU memory up to 192 GB per machine is supported.

Verified against Microsoft Learn (November 2026, view azloc-2610)

See System requirements for Azure Local. The 16 core and 128 GB figures used by the validation script below are the Cloud Standard baseline, not Microsoft requirements. Machines that cannot meet the memory and ECC requirement can use a virtual deployment for testing.

Size before you buy

Use Surveyor to model S2D capacity, resiliency, and workloads, and capture the as-built result with Ranger after deployment.

Storage Requirements​

Storage TierDrive TypeMinimum CountPurpose
Cache TierNVMe SSD2 per nodeHigh-speed caching (hybrid HDD plus flash layouts only: cache devices of 32 GB or more, cache-to-capacity ratio of 15% or more)
Capacity TierSSD or HDD4 per nodeData storage
Boot DriveSSD (BOSS/M.2)1 per nodeOS installation
Storage Configuration
  • Minimum 2 capacity drives required for Storage Spaces Direct resiliency
  • Cache-to-capacity ratio: 1:4 to 1:8 recommended
  • Total raw capacity: Plan for 2-3x usable capacity (mirroring overhead)

Network Requirements​

InterfaceSpeedRDMAPurpose
Management1 GbE or 10 GbENoCluster management, iDRAC
Storage25 GbE or 100 GbE (10 Gb is the minimum for RDMA)Required for S2D storage traffic (RoCEv2 or iWARP)Storage Spaces Direct (S2D). Disaggregated SAN deployments have no RDMA storage intent
Compute/VM25 GbE or 100 GbENo (guest RDMA is not supported)VM traffic, SDN

RDMA Technologies Supported:

  • RoCEv2 (RDMA over Converged Ethernet v2) - Preferred; requires PFC and ETS on every port including the switches
  • iWARP - Alternative for environments without DCB; the choice Learn gives for teams that don't manage ToR switches

RDMA adapters only work with adapters that use the same RDMA protocol, InfiniBand isn't supported, and Learn's RDMA vendor table lists Broadcom and Nvidia as RoCE only, Intel and Marvell (Qlogic) as iWARP and RoCE (some Intel models). Jumbo frames: Learn recommends an MTU of 9216 bytes on the physical switches for RDMA storage traffic.


Firmware Baseline Requirements​

Azure Local Cloud Standard Firmware Versions​

ComponentMinimum VersionTarget VersionNotes
Dell BIOS2.0.0Latest stableCheck Dell support matrix
iDRAC Firmware7.0.0Latest stableiDRAC 9 required
NIC FirmwareVaries by modelLatest validatedCheck Azure Local catalog
RAID ControllerVaries by modelLatest stablePERC/HBA firmware
Dell SBE Package4.2.25124.2.2512.1616+Solution Builder Extension. The package is a requirement: download it before you start (see the SBE package). Only the build-time side-load is opt-in

Dell Gold Image​

Azure Local Cloud standard Dell Gold Image specifications:

ComponentVersionNotes
Windows Server Build2510Azure Local OS (value from earlier engagements; the 2610 release runs OS build 26100.33650, so confirm the gold image for the 2610 media with Dell)
SBE Version4.2.2512.1616Dell Solution Builder Extension
Dell Solution Version12.2510.0.3165Integrated solution package
Azure Local Build2601Running version after Arc registration (earlier engagement value; the latest release is 12.2610.1004.50, see Releases and Support Lifecycle)

Firmware Validation​

Validate firmware versions match across all cluster nodes:

# Check BIOS version consistency
$discovery = Get-Content discovery/idrac-inventory.json | ConvertFrom-Json

foreach ($server in $discovery.servers.PSObject.Properties.Value) {
Write-Host "Server: $($server.service_tag)"
Write-Host " BIOS: $($server.firmware.bios_version)"
Write-Host " iDRAC: $($server.firmware.idrac_version)"
}

Hardware Discovery Process​

Overview​

Hardware discovery automates collection of Dell server specifications via iDRAC Redfish API, enabling:

  • Accurate hardware inventory for deployment planning
  • Validation that hardware meets Azure Local requirements
  • Documentation of firmware versions and configurations
  • Change tracking for hardware lifecycle management

Primary Script: Invoke-HardwareDiscovery.ps1 (Phase 04, Task 02)
Output: one <ServiceTag>.json per server and a discovery-summary.json, in the discovery folder

Prerequisites​

iDRAC Access Requirements:

  • iDRAC 9 or later with Redfish API enabled
  • Network connectivity to iDRAC management interface (HTTPS/443)
  • iDRAC administrator credentials

Verify iDRAC Accessibility:

# Test network connectivity
Test-NetConnection -ComputerName "10.10.10.11" -Port 443

# Verify Redfish API endpoint
Invoke-RestMethod -Uri "https://10.10.10.11/redfish/v1/" -SkipCertificateCheck

What Gets Discovered​

CategoryDetails Captured
SystemModel, service tag, asset tag, BIOS version
CPUModel, core count, thread count, max speed
MemoryTotal capacity, DIMM count, speed, type
StorageNVMe/SSD/HDD count, capacity, controller firmware
NetworkAdapter model, MAC addresses, firmware version
FirmwareBIOS, iDRAC, NIC, controller versions

Running Discovery​

All servers (the iDRAC address of each server comes from nodes[].bmc.ip_address in infrastructure.yml):

cd C:\git\azurelocal-toolkit

# The BMC login comes from hardware.bmc (or nodes[].bmc) of infrastructure.yml. The password is a secret reference.
# The script never prompts. To use another login, pass -Credential.
.\scripts\deploy\04-cluster-deployment\phase-01-hardware-provisioning\task-02-hardware-discovery-via-dell-redfish-api\powershell\Invoke-HardwareDiscovery.ps1 -InfrastructureFile .\infrastructure.yml

One server:

.\scripts\deploy\04-cluster-deployment\phase-01-hardware-provisioning\task-02-hardware-discovery-via-dell-redfish-api\powershell\Invoke-HardwareDiscovery.ps1 -InfrastructureFile .\infrastructure.yml -TargetNode "<node-name>"

The script reads each BMC through the standard Redfish API (read only) and writes one JSON file per server, so you can keep the files of each run to track firmware changes.

Validate Hardware Requirements​

After discovery, validate hardware meets Azure Local requirements:

  1. Open discovery-summary.json and the <ServiceTag>.json file of each server.
  2. Compare each server with the minimums in the tables above: CPU cores, memory, drives with their media type (NVMe, SSD or HDD) and role (cache or capacity), and network ports with their MAC addresses.
  3. Write down every gap. Fix it before the hardware goes to the next phase.

Node Inventory Worksheet (Per-Site)​

Site Hardware Summary​

FieldValue
Site Name/ID________________________
Number of Nodes☐ 2 ☐ 3 ☐ 4 ☐ 8 ☐ 16
Node Model________________________ (e.g., Dell AX-7525)
Cluster Configuration☐ 2-node ☐ 3-node ☐ 4+ node

Node Details​

Complete for each node in the cluster:

Node 1​

FieldValue
Hostname________________________ (e.g., CONAX01)
Service Tag________________________
Asset Tag________________________

Compute:

ComponentSpecification
CPU Model________________________
CPU Cores______
CPU Speed______ GHz
RAM Total______ GB
DIMM Configuration________________________

Storage:

Drive TypeModelCapacityCountPurpose
Boot (BOSS/M.2)________________ GB__OS
NVMe (Cache)________________ GB__S2D Cache
SSD (Capacity)________________ GB__S2D Capacity
HDD (Capacity)________________ GB__S2D Capacity

Network:

AdapterModelPortsSpeedRDMAPurpose
NIC 1__________________ GbE☐ Yes ☐ No________
NIC 2__________________ GbE☐ Yes ☐ No________
NIC 3__________________ GbE☐ Yes ☐ No________
NIC 4__________________ GbE☐ Yes ☐ No________

Firmware:

ComponentCurrent VersionTarget VersionStatus
BIOS________________________☐ Current ☐ Update needed
iDRAC________________________☐ Current ☐ Update needed
NIC Firmware________________________☐ Current ☐ Update needed
RAID Controller________________________☐ Current ☐ Update needed

Node 2​

(Repeat the Node 1 table structure)

FieldValue
Hostname________________________
Service Tag________________________
Asset Tag________________________

(Continue for additional nodes)


iDRAC Access and Credentials​

NodeiDRAC IPUsernamePassword LocationAccess Verified
Node 1____________________Key Vault: ________☐ Yes ☐ No
Node 2____________________Key Vault: ________☐ Yes ☐ No
Node 3____________________Key Vault: ________☐ Yes ☐ No
Node 4____________________Key Vault: ________☐ Yes ☐ No

iDRAC Verification:

  • iDRAC firmware version matches baseline: ☐ Yes ☐ No
  • iDRAC web interface accessible: ☐ Yes ☐ No
  • Redfish API enabled and accessible: ☐ Yes ☐ No
  • Virtual console (KVM) functional: ☐ Yes ☐ No
  • Virtual media mount tested: ☐ Yes ☐ No

NIC Mapping and Labeling​

Document the physical NIC identification for each node:

SlotPortMAC AddressPCI AddressPurposeVLAN(s)
Embedded1__:__:__:__:__:______Management____
Embedded2__:__:__:__:__:______Management____
Slot 11__:__:__:__:__:______Storage 1____
Slot 12__:__:__:__:__:______Storage 2____
Slot 21__:__:__:__:__:______ComputeTrunk
Slot 22__:__:__:__:__:______ComputeTrunk

RDMA Configuration:

SettingValue
RDMA Technology☐ RoCEv2 ☐ iWARP ☐ N/A
RDMA NICs per Node☐ 2 ☐ 4 ☐ Other: ____
RDMA Network Isolation☐ Dedicated VLANs ☐ Separate physical NICs
DCB/PFC Configured☐ Yes ☐ No

Hardware Assessment Checklist​

Pre-Deployment Validation​

  • All nodes are same model or validated compatible
  • All nodes have identical hardware configuration
  • Firmware versions match across all nodes
  • Firmware meets minimum baseline requirements
  • CPU cores meet minimum requirements (16+)
  • RAM meets minimum requirements (128 GB+)
  • Storage drives meet minimum requirements (2+ NVMe)
  • Network adapters are RDMA-capable (for storage)
  • iDRAC accessible from deployment workstation
  • Service tags documented
  • Hardware warranty verified and documented

Discovery Outputs​

  • discovery/idrac-inventory.json generated
  • Hardware validation script run with all checks passing
  • Firmware update plan created (if updates needed)
  • NIC mapping documented for all nodes
  • RDMA configuration plan documented

Fibre Channel HBA Requirements (SAN Deployments)​

This section applies only to disaggregated SAN deployments. Skip if using Storage Spaces Direct.

Disaggregated Azure Local clusters require Fibre Channel Host Bus Adapters (HBAs) in each node to connect to the external SAN array. HBAs must be validated for the Azure Local node model in use.

HBA Specifications​

RequirementDetails
Ports per nodeMinimum 2 (one per fabric for redundancy)
Dual-fabricTwo independent FC switches strongly recommended
Driver supportWindows Server driver available from vendor
CertificationValidated against Microsoft Azure Local hardware catalog
Consult your hardware vendor

Azure Local nodes are validated with specific HBA models. Consult your server vendor's Azure Local configuration guide for the supported HBA list. The HBA driver must be installed before Arc registration — see Phase 03 Task 12.

FC Switch Port Planning​

Each node contributes HBA ports to both fabrics. Use the following formula to determine the number of switch ports required:

Ports per fabric = (Number of nodes × HBA ports per node per fabric) + SAN array target ports

Example: 4-node cluster, 1 HBA port per node per fabric, 2 SAN target ports per fabric:

  • Ports per fabric = (4 × 1) + 2 = 6 FC switch ports per fabric

Pre-Installation Checklist​

  • HBA model validated for the Azure Local node model
  • FC switch ports allocated per formula above
  • Vendor driver package downloaded
  • SAN array FC target port WWPNs documented
  • Dual-fabric FC switch inventory confirmed

References:


Next Steps​

After completing hardware requirements documentation:

  1. For multi-site deployments, see Multi-Site Planning
  2. Proceed to Stage 11 - Hardware Provisioning
  3. Review Site Assessment - Ensure Site Assessment is complete