Phase 04: Register Nodes with Azure Arc
Table of Contents
- Details
- Task 01 — Pre-Registration Environment Validation
- Task 02 — Register Cluster Nodes with Azure Arc
- Task 03 — Monitor Bootstrap Process
- Task 04 — Verify Arc Registration and Connectivity
Details
Objective: Register all cluster nodes with Azure Arc to enable Azure management plane integration and prepare for Azure Local cloud deployment.
Tasks:
- Run pre-registration environment validation from each node
- Register each node with Azure Arc
- Monitor bootstrap process and OEM image updates
- Verify Arc agent installation and connectivity
- Validate node status in Azure Portal
- Confirm Arc-enabled server management capabilities
Validation:
- All nodes appear in Azure Portal as Arc-enabled servers
- Arc agent services running on all nodes
- Azure management extensions deployed
- Nodes ready for Azure Local cluster deployment
Outcome: All cluster nodes registered with Azure Arc and visible in Azure Portal, enabling cloud-based deployment orchestration and management for Azure Local cluster deployment. Without Arc-enabled nodes, the cloud deployment orchestrator cannot communicate with the cluster. Arc also enables centralized monitoring, update management, and security posture management across hybrid infrastructure.
Arc deregistration requires OS reinstallation. Verify subscription and resource group settings before proceeding. Once registered, nodes cannot be moved between subscriptions without reinstalling the operating system.
Arc Registration Process Flow
When you run Invoke-AzStackHciArcInitialization, the following sequence occurs:
graph TD
A[Run Invoke-AzStackHciArcInitialization] --> B{OEM Image Check}
B -->|Current| E[Install Arc Agent]
B -->|Outdated| C[Download LCM Updates]
C --> D[System Reboot]
D --> E
E --> F[Register with Azure Arc]
F --> G[Install Required Extensions]
G --> H[Arc Registration Complete]
H --> I[Node Ready for Cluster Deployment]
OEM Image Validation
If you purchased Integrated System or Premier solution hardware from the Azure Local Catalog, the OS is typically preinstalled (OEM image). These images may be outdated and might not include the latest OS version or drivers.
During Arc registration, the system automatically:
- Detects outdated OEM image — Checks if the preinstalled OS meets minimum requirements
- Downloads Lifecycle Manager (LCM) updates — Retrieves required updates from Microsoft
- Applies updates and reboots — System restarts automatically (may occur multiple times)
- Resumes registration — After reboot, registration continues automatically
- Completes Arc enablement — Installs Arc agent and required extensions
| Status | Meaning |
|---|---|
Update: InProgress | System is downloading/applying updates before registration |
Succeeded | Node successfully registered with Azure Arc |
Failed | Registration failed—collect logs for troubleshooting |
The Arc registration script takes 20-30 minutes per node. If an OEM image update is triggered, add an additional 15-30 minutes for updates and reboots.
Steps Overview
| Step | Description | Duration | Link |
|---|---|---|---|
| 1 | Pre-Registration Validation | 10-15 min | Task 1 |
| 2 | Register Cluster Nodes with Azure Arc | 20-30 min/node | Task 2 |
| 3 | Monitor Bootstrap Process | 15-45 min | Task 3 |
| 4 | Verify Arc Registration and Connectivity | 15 min | Task 4 |
Registration Options
Each task provides two execution modes to accommodate different deployment scenarios:
| Mode | Best For | Execution Context |
|---|---|---|
| Direct | Individual node work, lab/test | Run commands on each node directly |
| Orchestrated | Production multi-node | Run from management server via variables.yml and PowerShell remoting |
For production multi-node deployments, use the Orchestrated tab in each task to register, monitor, and verify all nodes from a central management server.
Next Steps
After completing Arc registration, proceed to:
| Next Stage | Description |
|---|---|
| Phase 05: Cluster Deployment | Deploy the Azure Local cluster via Azure Portal |