Azure HCI single node deployment

Question

Hi,

Trying to deploy Azure Single node HCI. Server installed and registered with Azure-ARC in US-EAST2. Cluster created in PowerShell and trying to create a instance in azure portal. While creating a instance in EAST-US the serve not showing. But the same server available in the Azure ARC Resources.

Looking for help to solve this issue.

Answer 1

Hello eGAzureAccount,

Thank you for posting your question in the Microsoft Q&A forum. 

When deploying Azure Stack HCI (Single Node), if your server appears in Azure Arc but not in the Azure Portal (East US) during instance creation, the issue typically stems from region mismatch, synchronization delays, or registration inconsistencies. Below are the key steps to diagnose and resolve this: 

1. Verify Azure Region Alignment 

• Ensure your Azure Stack HCI cluster is registered in the same Azure region (East US) where you are trying to create the instance.  Check via PowerShell:  Get-AzureStackHCI   
• Confirm the AzureResourceGroup and AzureRegion match your deployment target. 

2. Check Azure Resource Provider Registration 

• The Microsoft.AzureStackHCI resource provider must be registered in your subscription:  Register-AzResourceProvider -ProviderNamespace Microsoft.AzureStackHCI   
• Validate in the Azure Portal:  Subscriptions → Your Subscription → Resource Providers → Microsoft.AzureStackHCI (should be "Registered"). 

3. Force Sync Between Azure Arc and HCI 

• Manually sync the node with Azure:  Sync-AzureStackHCI   
• Wait 10-15 minutes for Azure Portal propagation. 

4. Validate Network & Permissions 

• Ensure the HCI node has outbound internet access (ports 443, 80) to Azure. 
• Confirm the service principal used for registration has Contributor rights on the target resource group. 

5. Check for Hidden Resources - In the Azure Portal, search for:  "Azure Stack HCI" under All Resources (not just the HCI blade). 

Use Azure CLI to locate the cluster:  az stack-hci cluster list   

6. Re-register if Necessary - If the issue persists, re-register the cluster: Unregister-AzureStackHCI    Register-AzureStackHCI -SubscriptionId "YOUR_SUB_ID" -ResourceGroupName "HCI-RG" -Region "eastus"   

If the above answer helped, please do not forget to "Accept Answer" as this may help other community members to refer the info if facing a similar issue. Your contribution to the Microsoft Q&A community is highly appreciated.