Azure Stack HCI deployment overview (preview)

Applies to: Azure Stack HCI, Supplemental Package

This article is the first in the series of deployment articles that describe how to deploy Azure Stack HCI using a new deployment tool and methods.

You can deploy Azure Stack HCI using a new or existing config file interactively or via PowerShell.

Important

This feature is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

About deployment methods

You can deploy Azure Stack HCI using one of the following methods:

• Interactive: Deploy using a new config file interactively. The interactive flow provides a guided, step-by-step experience that helps you create a new configuration file which is then used to deploy and register the cluster. This method should be used when you deploy for the first time and is recommended for most customers.

• Existing configuration: Deploy using this option if you already have a configuration file from a prior deployment. This option is recommended when deploying multiple systems.

• PowerShell: Deploy using this option if you already have a configuration file. This option is recommended for the partners and when deploying systems at-scale.

Deployment sequence

Follow this process sequence to deploy Azure Stack HCI in your environment:

• Select one of the validated network topologies to deploy.
• Read the prerequisites for Azure Stack HCI.
• Follow the deployment checklist.
• Prepare your Active Directory environment.
• Install Azure Stack HCI version 22H2 on each server.
• Install and run the deployment tool interactively with a new configuration file or using an existing configuration file.
• If preferred, you can deploy using PowerShell.
• After deployment, validate deployment.
• If needed, troubleshoot deployment.

Validated network topologies

Important

We recommend that you use one of the validated network topologies for optimum results.

The following network topologies were tested and validated for this release:

• A single physical server connected to a network switch. This is sometimes referred to as a single-node cluster.

• Two physical servers with direct (switchless) storage network connections to an L2 switch.

  Configuration 1: The following diagram shows two physical servers with a directly connected (switchless) storage network and a single TOR switch.

  

• Two physical servers with direct (switchless) storage network connections to redundant L3 switches.

  Configuration 2: The following diagram shows two physical servers with a directly connected (switchless) storage network and redundant TOR switches.

  

• Four physical servers with storage network connections to an L2-switch.

  Configuration 3: The following diagram shows four physical servers using a non converged network and with storage network connections to L2 switches.

  

• Four physical servers deployed using a fully-converged network for compute, storage, and management and with redundant TOR switches.

  Configuration 4: The following diagram shows four physical servers using a fully converged network (for compute, management, and storage) and with storage network connections to redundant L3 switches.

  

Next steps

• Read the prerequisites for Azure Stack HCI.