Azure Stack HCI Hardware Requirements and Setup Essentials

To set up Azure Stack HCI, you'll need a server with at least two processors, each with at least 4 physical cores, and a minimum of 32 GB of RAM.

Azure Stack HCI supports a variety of server models, but they must meet specific hardware requirements. The supported server models are listed on the Azure Stack HCI documentation website.

You'll also need a storage solution, such as a Storage Spaces Direct (S2D) configuration, which can be set up using a combination of hard disk drives (HDDs) and solid-state drives (SSDs).

The minimum storage requirements for Azure Stack HCI are 2 TB of storage, with a recommended minimum of 4 TB for production workloads.

To build an Azure Stack HCI cluster, you'll need a minimum of one server and a maximum of 16 servers. All servers must be the same manufacturer and model.

Each server must have a 64-bit processor from Intel Nehalem grade, AMD EPYC grade, or later, with second-level address translation (SLAT). A second-generation Intel Xeon Scalable processor is required for Intel Optane DC persistent memory support.

The processor must be at least 1.4 GHz and compatible with the x64 instruction set. You'll also need at least 32 GB of RAM per node to accommodate the server operating system, VMs, and other apps or workloads.

Here are the processor and RAM requirements in a concise list:

Ensure that virtualization support is turned on in the BIOS or UEFI on all servers.

To build a server for an Azure Stack HCI cluster, you'll need to start with a solid foundation. A standard cluster requires a minimum of one server and a maximum of 16 servers.

All servers should be the same manufacturer and model, and they must have 64-bit Intel Nehalem grade, AMD EPYC grade or later compatible processors with second-level address translation (SLAT). This is a crucial requirement.

A second-generation Intel Xeon Scalable processor is required to support Intel Optane DC persistent memory, and processors must be at least 1.4 GHz and compatible with the x64 instruction set.

For each server, make sure to have at least 32 GB of RAM to accommodate the server operating system, VMs, and other apps or workloads. This will ensure smooth performance.

In addition to RAM, allow 4 GB of RAM per terabyte (TB) of cache drive capacity on each server for Storage Spaces Direct metadata. This will help with data management.

Verify that virtualization support is turned on in the BIOS or UEFI. This is a critical step to ensure your servers can support virtualization.

To minimize potential issues, ensure all the servers are in the same time zone as your local domain controller. This will help with synchronization.

You can use any boot device supported by Windows Server, which now includes SATADOM. A 200 GB minimum size is recommended for the boot device.

For Hyper-V, see the system requirements for additional feature-specific requirements.

Storage Requirements are crucial for Azure Stack HCI to function optimally. Each server in the cluster should have the same types of drives and the same number of each type.

For instance, if you're using SATA drives, all servers should have SATA drives. It's also recommended, but not required, that the drives be the same size and model.

Drives can be internal to the server or in an external enclosure that is connected to just one server. To achieve drive symmetry, it's essential to ensure that every server has the same number and type of drives.

Each server in the cluster should have dedicated volumes for logs, with log storage at least as fast as data storage. Stretched clusters require at least two volumes: one for replicated data and one for log data.

SCSI Enclosure Services (SES) is required for slot mapping and identification. Each external enclosure must present a unique identifier (Unique ID).

Networking Requirements are a top priority when building an Azure Stack HCI cluster. A reliable high-bandwidth, low-latency network connection between each server node is essential.

You'll need to verify that at least one network adapter is available and dedicated for cluster management. This is a must-have for a smooth and efficient cluster setup.

Verify that physical switches in your network are configured to allow traffic on any VLANs you will use. This ensures that your network is ready for cluster management.

A stretched cluster requires a minimum of 4 servers (2 per site) and a maximum of 16 servers (8 per site). This ensures that your cluster is scalable and can handle the demands of your workload.

Each site must have the same number of servers and drives. This is crucial for maintaining data consistency and ensuring that your cluster operates smoothly.

Here are the key networking requirements to keep in mind:

To join an Azure Stack HCI system, you must have an Active Directory Domain Services (AD DS) domain available.

You can use any Active Directory domain, as there are no special domain functional-level requirements.

We recommend turning on the Active Directory Recycle Bin feature as a general best practice, if you haven't already.

Microsoft recommends purchasing Premier Solutions from their hardware partners for the best Azure Local experience. These partners offer a range of solutions that can be browsed in the Azure Local Catalog.

Some of the hardware partners available include ASUS, Blue Chip, DataON, Dell EMC, Fujitsu, HPE, Hitachi, Lenovo, NEC, primeLine Solutions, QCT, and Supermicro.

Azure Stack and Azure Stack HCI are two distinct options for bringing cloud capabilities to on-premises environments. Azure Stack is a hybrid cloud platform that enables organizations to deploy full Azure services on-premises.

Azure Stack HCI, on the other hand, is optimized for virtualized workloads. If you're looking for a hyper-converged infrastructure that blends cloud with on-premises control, Azure Stack HCI is the way to go.

To set up Azure Local, you'll need a few key things. First, you'll need to purchase one or more machines from the Azure Local Catalog, available from your preferred Microsoft hardware partner.

Make sure your Azure subscription is in good standing, as you'll need it to access Azure Local features. You'll also need operating system licenses for your workload VMs, such as Windows Server.

An internet connection is required for each machine, which must be able to connect via HTTPS outbound traffic to well-known Azure endpoints at least every 30 days. This ensures your system stays connected and up-to-date.

If you're planning to use SDN (Software-Defined Networking) with systems stretched across sites, you'll need a virtual hard disk (VHD) for the Azure Stack HCI OS to create Network Controller VMs.

Here's a quick rundown of the hardware and network requirements:

Azure Local is priced on a per core basis on your on-premises machines, so be sure to check the current pricing for more information.