Your Browser is Out of Date

Nytro.ai uses technology that works best in other browsers.
For a full experience use one of the browsers below
Portal-based Deployment and Operations Guide for Single-node Cluster
Revision history Single-node clusters
Single-node clusters
Single-node configuration
Operating system deployment
Manual operating system deployment Factory-installed operating system deployment
Configure host networking
Registry settings
Change the hostname
Registering a Partner Admin Link (PAL) for Azure related solutions
Add a PAL through the Azure portal by using Azure PowerShell Add a PAL through the Azure portal using the subscription user ID Dell Technologies Partner IDs for Partner Admin Link
Install Windows Admin Center
Install OpenManage Integration with Microsoft Windows Admin Center
Install roles and features
Configuration to prepare nodes
Verify and update firmware and software compliance
Configuring firewall settings
Cluster deployment prerequisites
Review Requirements Prepare Active Directory Stage SBE package for installation Register Servers with Azure Arc Assign deployment user roles
Deploy Azure Stack HCI version 23H2
Deploy a single-node cluster using Azure portal Deploy Azure Stack HCI using Microsoft ARM template
Best practices and recommendations
Updating the page file settings Update the hardware timeout for the Spaces port Antivirus exclusions
Update Azure Stack HCI clusters using SBE package
Prerequisites SBE package update using PowerShell SBE package update using Azure portal
Dell OpenManage Integration with Windows Admin Center
Overview Managing Microsoft HCI-based clusters Validate and remediate Azure Stack HCI clusters View HCI compliance summary
Onboard Dell policies to Azure Arc from Windows Admin Center

Deploy Azure Stack HCI version 23H2

Home > Integrated Products > Microsoft HCI Solutions from Dell Technologies > Guides 23H2 and later > Portal-based Deployment and Operations Guide for Single-node Cluster > Deploy Azure Stack HCI version 23H2

Deploy Azure Stack HCI version 23H2

  • Deploy Azure Stack HCI using Microsoft ARM template

    Before you can deploy Azure Stack HCI version 23H2 using the Microsoft Azure Resource Manager (ARM) template, you must complete the following deployment prerequisites:

    • Create a service principle and service secret.
    • Create a client secret.
    • Get the object ID for Azure Stack HCI Resource Provider.
    • Create a storage account.
    • Get the Arc node resource ID.

    Procedures are correct at publication but are subject to change without notice. For the most up-to-date details, see Deploy an Azure Stack HCI, version 23H2 via Azure Resource Manager deployment template > Prerequisites.


    Prerequisites before deploying Azure Stack HCI using Microsoft ARM template

    Before using the Microsoft Azure Resource Manager (ARM) template to deploy Azure Stack HCI, complete the following prerequisite procedures:

    • Create a service principal
    • Create a client secret
    • Get the object ID for Azure Stack HCI Resource Provider
    • Create a storage account
    • Get the Arc node resource ID

    Create a service principal

    Before using the Microsoft Azure Resource Manager (ARM) template to deploy Azure Stack HCI, you must create a service principal.

    To create a service principal and assign Azure Resource Bridge Deployment Role, do the following:
    1. Log in to the Azure portal. Go to Identity > Applications > App registrations and select New registration.
    2. Enter a Name for the application, select a Supported account type, and then click Register.
    3. When the service principal is created, go to Enterprise applications. Search for the application ID and select the application name created in step 1.
    4. Copy the Application ID and Object ID.
      Application ID is used in the Arb Deployment App ID field and Object ID is used in the Arb Deployment SPN Object ID field.

    Create a client secret

    Before using the Microsoft Azure Resource Manager (ARM) template to deploy Azure Stack HCI, you must create a client secret.

    To create a client secret, do the following:
    1. Go to the service principal that was created in the previous task.
    2. Go to Certificates & secrets > Client secrets, and then click New Client Secret.
    3. Enter a description, and then select an expiry date from the list. Click Add.
    4. To copy the client secret Value, click the copy icon beside the field.
      Figure 16. Client secret value
      client secret value is only visible immediate after creating the client secret
      Note: The client secret value can only be viewed immediately after creating the client secret.

      The client secret value is used later in the ARM template for the deployment.

    Get the object ID for the Azure Stack HCI Resource Provider

    Before deploying Azure Stack HCI , version 23H2, using the Microsoft ARM template, you must get the object ID for the Azure Stack HCI Resource Provider.

    To get the object ID for the Azure Stack HCI Resource Provider, do the following:
    1. In the Azure portal, search for and then select Microsoft Entra ID.
    2. From the Overview tab, search for and then select Microsoft.AzureStackHCI Resource Provider.
    3. Copy the Object ID, as shown in the following figure.
      Figure 17. Object ID
      Screenshot showing a red box around the Object ID field.
      Object ID is entered in HCI Resource Provider Object ID in the ARM template.

    Create a Storage Account

    Before deploying Azure Stack HCI , version 23H2, using the Microsoft ARM template, you must create a storage account.

    To create a storage account, do the following:
    1. From the Azure portal home page, go to Create a resource > Search for Storage account > Select storage account, and then click Create.
    2. In the Create a storage account window, from the lists, select the Subscription and Resource group, and then click Review + create.
      Figure 18. Creating the resource group
      Create a resource group
    3. In the Review + create window, click Create.
      Figure 19. Creating the storage account
      Review the storage account details and then create the storage account
    4. Go to the newly created storage account. In Cluster Witness Storage Account Name, enter the storage account that will be used in the ARM template.

    Get the Arc node resource ID

    Before deploying Azure Stack HCI , version 23H2, using the Microsoft ARM template, you must get the Arc node resource ID.

    To get the Arc node resource ID, do the following:
    1. In the Azure portal, search for the resource group where nodes are registered.
    2. From Resource Group, select the node, select JSON view, and then copy the Resource ID of the node.
    3. To get the Resource ID for each node, repeat the previous steps.
      Figure 20. Resource ID
      resource ID in JSON view
      The resource IDs are entered in the Arc Node Resource IDs field in the ARM template.

    Deploy a cluster using the Microsoft ARM template

    Deploy an Azure Stack HCI cluster using the Microsoft Azure Resource Manager (ARM) template.

    Before deploying a cluster, ensure that all prerequisites are complete. See Deploy Azure Stack HCI using Microsoft ARM template.

    To deploy an Azure Stack HCI system using the ARM template, you must do the following:

    Note: Procedures are correct at publication but are subject to change without notice. For the most up-to-date details, see Deploy an Azure Stack HCI, version 23H2 via Azure Resource Manager deployment template.

    1. In the Azure portal, from Home, click Create a Resource.
    2. Click Template deployment (deploy using custom templates) .
    3. Under Start with a quickstart template or template spec, choose Quickstart template.
      Figure 21. Custom deployment - selecting a template
      choose the quick template option and then select the one you need
    4. From the Quickstart template list, choose azurestackhci/create-cluster, and then click Select template.
    5. From the Basics tab, select the resource group where the Arc-enabled servers are registered for the deployment.
    6. Select Region, and then, in Deployment Mode, select Validate.
    7. Enter the Key Vault Name and Cluster Name.
    8. Select Witness Type, and then enter Cluster Witness Storage Account Name.
      Note: For a two-node cluster, a witness is mandatory.

    9. Enter Local Admin and Azure Stack LCM Admin credentials.
    10. Enter the following data from information collected in previous steps:
      1. Arb Deployment App ID
      2. Arb Deployment App Secret
      3. Arb Deployment SPN Object ID
      4. Azure Stack HCI Resource Provider Object ID
    11. Enter the Arc Node Resource IDs that you collected in previous steps.
    12. Enter the Domain FQDN and Adou Path.
    13. Enter the following:
      1. Subnet Mask
      2. Default gateway
      3. Starting IP address
      4. Ending IP address
      5. DNS Servers IP
      Note: Azure Stack HCI deployment requires six IP addresses for the system and services.

    14. Under Physical Nodes Settings, enter the Hostname and IP addresses for the nodes, for example:
      [{"name":"NODE1","ipv4Address":"172.18.30.1"},{"name":"NODE2","ipv4Address":"172.18.30.2"}]
    15. Under Networking type, select the following:
      • For a single-server deployment, select SingleServerDeployment.
      • For a two- or more node cluster deployment, select SwitchedMultiServerDeployment.
      • For a two- or three-node switchless cluster deployment, select SwitchlessMultiServerDeployment.
    16. Under Networking Pattern, choose one of the following options:
      • Select Hyperconverged to Group all traffic: Choose this option if you are configuring a fully converged network topology.
      • Select ConvergedManagementCompute to Group management and compute traffic: Choose this option if you want to configure a network topology with storage traffic on physical network adapters.
    17. Set Storage Connectivity Switchless to True for switchless networking or to False for switched networking.
    18. Click Edit Parameters.
    19. Edit Network intent details based on the network topology that you are using for the deployment.
      The following script shows an example of the multi-node ConvergedManagementCompute network topology. 
      "intentList": {
            "value": [
              {
                "name": "Compute_Management",
                "trafficType": [
                  "Management",
                  "Compute"
                ],
                "adapter": [
                  "Integrated NIC 1 Port 1-1",
                  "Integrated NIC 1 Port 2-1"
                ],
                "overrideVirtualSwitchConfiguration": false,
                "virtualSwitchConfigurationOverrides": {
                  "enableIov": "",
                  "loadBalancingAlgorithm": ""
                },
                "overrideQosPolicy": true,
                "qosPolicyOverrides": {
                  "priorityValue8021Action_Cluster": "5",
                  "priorityValue8021Action_SMB": "3",
                  "bandwidthPercentage_SMB": "50"
                },
                "overrideAdapterProperty": true,
                "adapterPropertyOverrides": {
                  "jumboPacket": "1514",
                  "networkDirect": "Enabled",
                  "networkDirectTechnology": "iWARP"
                }
              },
              {
                "name": "Storage",
                "trafficType": [
                  "Storage"
                ],
                "adapter": [
                  "SLOT 5 Port 1",
                  "SLOT 5 Port 2"
                ],
                "overrideVirtualSwitchConfiguration": false,
                "virtualSwitchConfigurationOverrides": {
                  "enableIov": "",
                  "loadBalancingAlgorithm": ""
                },
                "overrideQosPolicy": true,
                "qosPolicyOverrides": {
                  "priorityValue8021Action_Cluster": "5",
                  "priorityValue8021Action_SMB": "3",
                  "bandwidthPercentage_SMB": "50"
                },
                "overrideAdapterProperty": true,
                "adapterPropertyOverrides": {
                  "jumboPacket": "9014",
                  "networkDirect": "Enabled",
                  "networkDirectTechnology": "iWARP"
                }
              }
            ]
          },
          "storageNetworkList": {
            "value": [
              {
                "name": "StorageNetwork1",
                "networkAdapterName": "SLOT 5 Port 1",
                "vlanId": "711"
              },
              {
                "name": "StorageNetwork2",
                "networkAdapterName": "SLOT 5 Port 2",
                "vlanId": "712"
              }
            ]
       },
    20. Save the parameters file. Leave all remaining parameters set to their default values.
    21. Select Review + create and then click Create.
      This step validates the deployment and creates the prerequisites that are required for the deployment.
    22. When validation is complete, click Redeploy.
    23. Select Edit parameters, load the parameter JSON file, and then click Save.
    24. Select the Resource Group.
    25. Change Deployment Mode from Validate to Deploy.
    26. To begin the deployment, select Review + create, and then click Create.
    27. To check the deployment progress, open a new browser window, go to the resource group, and then click the cluster resource. Go to Settings > Deployment and then click Refresh .
      Deployment can take between 2.5 and 3 hours.