Add Azure Local Node

Handian Sudianto 7,471 Reputation points
2026-09-14T14:01:21.14+00:00

When we want add another node to existing azure local with two node then the new node should have same SBE version or when adding the new node will update the SBE automatically?

In the article https://learn.microsoft.com/en-us/azure/azure-local/manage/add-server?view=azloc-2608&utm_source=chatgpt.com&tabs=azure-powershell there are two command,

  • Add-Server -Name "<new-node-name>" and
  • $HostIpv4 = "<IPv4 for the new node>" $Cred = Get-Credential Add-Server -Name "<Name of the new node>" -HostIpv4 $HostIpv4 -LocalAdminCredential $Cred

Is the 1st command only for preparation and 2nd to add the node to cluster?

Azure Local
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-09-14T14:01:40.6466667+00:00

    The new node should use the same solution version as the existing cluster. For versions 2503 and later, the OS image on the new node must match the solution version running on the existing cluster. The add-node process does not state that it automatically updates the new node to match before adding it.

    For the add operation itself:

    1. Prepare the new node first:
      • Install OS, drivers, and firmware.
      • Register the node with Arc using the same resource group, region, subscription, and tenant as the existing nodes.
      • Assign the required permissions.
    2. Then add the node from an existing cluster node.

    About the two Add-Server examples:

    • Add-Server -Name "<new-node-name>"
      • This is a simple example showing the cmdlet used to add a prepared node.
      • It is not described as a separate preparation-only step.
    •   $HostIpv4 = "<IPv4 for the new node>"
  $Cred = Get-Credential
  Add-Server -Name "<Name of the new node>" -HostIpv4 $HostIpv4 -LocalAdminCredential $Cred
      • This is the operational command sequence to add the incoming node from an existing node in the system.
      • It uses the new node’s IPv4 address and local administrator credentials.

    So, the first command is a simplified example of the add-node cmdlet, while the second is the fuller command sequence used to perform the add operation.

    After Add-Server runs:

    • Save the returned operation ID.
    • Monitor progress with Start-MonitoringActionplanInstanceToComplete.
    • Wait for storage rebalance to finish with Get-VirtualDisk | Get-StorageJob.
    • If needed, run Sync-AzureStackHCI so the node appears sooner in Azure portal.

    Also note:

    • Only one node can be added at a time in this release.
    • If the add operation fails, rerun it with Add-Server -Rerun.
    • Starting with release 2508, validation runs after Add-Server and returns failure details if a test fails.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Marcin Policht 108.1K Reputation points MVP Volunteer Moderator
    2026-09-14T18:47:52.83+00:00

    The new server should be at the required software and hardware configuration level for the existing Azure Local cluster before you add it. SBE is tied to the validated Azure Local solution and hardware configuration. The incoming node needs to satisfy the cluster's SBE and driver/firmware requirements. The add-server workflow performs prerequisite and compatibility checks, but it is not the same thing as updating the node's SBE package.

    Version disparities or mismatched SBE component integrity checks can cause pre-addition validations or deployment steps to fail.

    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.