About Azure Stack HCI, version 23H2 deployment
Applies to: Azure Stack HCI, version 23H2
This article is the first in the series of deployment articles that describe how to deploy Azure Stack HCI, version 23H2. This article applies to both single and multi-node deployments. The target audience for this article is IT administrators who are responsible for deploying Azure Stack HCI in their organization.
Azure Stack HCI, version 23H2 is the latest GA version, which doesn't support upgrade from version 22H2. Begin with a new 2311 deployment, update to 2311.2, and strictly follow version 23H2 deployment instructions. Don't mix steps from version 22H2 and version 23H2.
About deployment methods
In this release, you can deploy Azure Stack HCI using one of the following methods:
Deploy from Azure portal: Select this option to deploy an Azure Stack HCI cluster using Azure portal. You can choose from three deployment methods: New configuration, Template spec, and QuickStart template. The deployment flow guides you through the steps to deploy your Azure Stack HCI cluster.
For more information, see Deploy via Azure portal.
Deploy from an Azure Resource Manager(ARM) template: Select this option to deploy an Azure Stack HCI cluster using an ARM Deployment Template and the corresponding Parameters file. An ARM template is a JSON file containing customized template expressions where you can define dynamic values and logic that determine the Azure resources to deploy.
For more information, see Deploy via ARM template.
Follow this sequence to deploy Azure Stack HCI in your environment:
|Select validated network topology
|Identify the network reference pattern that corresponds to the way your servers are cabled. You will define the network settings based on this topology.
|Read the requirements and complete the prerequisites
|Review the requirements and complete all the prerequisites and a deployment checklist before you begin the deployment.
|Step 1: Prepare Active Directory
|Prepare your Active Directory (AD) environment for Azure Stack HCI deployment.
|Step 2: Download Azure Stack HCI, version 23H2 OS
|Download Azure Stack HCI, version 23H2 OS ISO from Azure portal
|Step 3: Install OS
|Install Azure Stack HCI operating system locally on each server in your cluster.
|(Optional) Configure the proxy
|Optionally configure proxy settings for Azure Stack HCI if your network uses a proxy server for internet access.
|Step 4: Register servers with Arc and assign permissions
|Install and run the Azure Arc registration script on each of the servers that you intend to cluster.
Assign required permissions for the deployment.
|Step 5A: Deploy the cluster via Azure portal
|Use the Azure portal to select Arc servers to create Azure Stack HCI cluster. Use one of the three deployment methods described previously.
|Step 5B: Deploy the cluster via ARM template
|Use the ARM Deployment Template and the Parameter file to deploy Azure Stack HCI cluster.
Validated network topologies
When you deploy Azure Stack HCI from Azure portal, the network configuration options vary depending on the number of servers and the type of storage connectivity. Azure portal guides you through the supported options for each configuration.
Before starting the deployment, we recommend you check the following table that shows the supported and available options.
Supported network topologies
|One node - no switch for storage
|One node - with network switch for storage
|Two nodes - no switch for storage
|Two nodes - with network switch for storage
|Three nodes - with no switch for storage
No update or repair support
|Three nodes - with network switch for storage
|Four to 16 nodes - with no network switch for storage
|Four to 16 nodes - with network switch for storage
The two network topology options are:
No switch for storage. When you select this option, your Azure Stack HCI system uses crossover network cables directly connected to your network interfaces for storage communication. The current supported switchless deployments from the portal are one or two nodes.
Network switch for storage. When you select this option, your Azure Stack HCI system uses network switches connected to your network interfaces for storage communication. You can deploy up to 16 nodes using this configuration.
You can then select the network reference pattern corresponding to a validated network topology that you intend to deploy.
- Read the prerequisites for Azure Stack HCI.