• Ensure that the network configuration is in order.
• Ensure good Internet connectivity on the nodes.
• Ensure that your Azure subscription is registered with the required resource providers. You must be an owner or contributor on your subscription to register the following resource RPs:
  • Microsoft.HybridCompute
  • Microsoft.GuestConfiguration
  • Microsoft.HybridConnectivity
  • Microsoft.AzureStackHCI

For more information, see Register your servers and assign permissions for Azure Stack HCI, version 23H2 deployment.

Set up an active directory environment before deploying an Azure Stack HCI cluster. The following document can be used to prepare your active directory environment: Prepare Active Directory for Azure Stack HCI, version 23H2 deployment.

#Uninstall unwanted Az module versions

Uninstall-Module -Name Az.Accounts -RequiredVersion 3.0.0 -Force

Uninstall-Module -Name Az.Accounts -RequiredVersion 2.19.0 -Force

Uninstall-Module -Name Az.Resources -RequiredVersion 6.16.2 -Force

Uninstall-Module -Name Az.ConnectedMachine -RequiredVersion 0.7.2 -Force

Uninstall-Module -Name Az.ConnectedMachine -RequiredVersion 0.8.0 -Force

#Install NuGet package provider
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
 
#Register PSGallery as a trusted repo
Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
 
#Install Arc registration script from PSGallery 
Install-Module AzsHCI.ARCinstaller -Force
 
#Install required PowerShell modules in your node for registration
Install-Module Az.Accounts -RequiredVersion 2.13.2
Install-Module Az.Resources -RequiredVersion 6.12.0
Install-Module Az.ConnectedMachine -RequiredVersion 0.5.2
 
#Define the subscription where you want to register your server as Arc device
$Subscription = "<subscription ID>"
 
#Define the resource group where you want to register your server as Arc device
$RG = "<resource group name>"
 
#Define the tenant you will use to register your server as Arc device
$Tenant = "<Tenant ID>"
  
#Connect to your Azure account and Subscription
Connect-AzAccount -SubscriptionId $Subscription -TenantId $Tenant -DeviceCode

Log in to Device Code and enter the code presented by the command above.

Return to the PowerShell window where you will see that the Connect-AzAccount operation is completed.

Enter the Arc registration commands in the PowerShell window on every server:

#Get the Access Token for the registration
$ARMtoken = (Get-AzAccessToken).Token
 
#Get the Account ID for the registration
$id = (Get-AzContext).Account.Id
 
#Invoke the registration script.
Invoke-AzStackHciArcInitialization -SubscriptionID $Subscription -ResourceGroup $RG -TenantID $Tenant -Region eastus -Cloud "AzureCloud" -ArmAccessToken $ARMtoken -AccountID $id

The registration process takes 5 to 15 minutes. During the process, the following screens appear:

Verify the Arc extension registration by reviewing the resource group in the Azure portal.

All server resources are listed in the resource group.

Verify that all Arc extensions are installed successfully on each node. Time taken for the extensions to install and reflect Succeeded on the Azure portal depends on the available bandwidth to Azure. Go to Resource Group > Node > Extensions.

The following is an example of LCM installed.

For more information about registering the servers to Azure arc, see Register servers with Azure Arc.