Task 04: Verify Arc Registration and Connectivity
DOCUMENT CATEGORY: Runbook SCOPE: Verify that Azure Arc registration is successful and connectivity is establis... PURPOSE: Verify that Azure Arc registration is successful and connectivity is established for all cluster nodes MASTER REFERENCE: Register Azure Local with Azure Arc
Status: Active
Runbook Phase 04 — Arc Registration Azure LocalStatus: Production-ready
Overview
After Arc registration and bootstrap complete, verify that all cluster nodes are properly registered, connected, and ready for Azure Local cluster deployment.
Prerequisites
| Requirement | Details |
|---|---|
| Arc registration | Completed via Task 02 |
| Bootstrap status | Succeeded on all nodes (Task 03) |
| Azure modules | Az.Accounts, Az.ConnectedMachine |
| Node access | WinRM to all cluster nodes |
Values from infrastructure.yml
The values for this task come from infrastructure.yml (schema 5). Every key, with its type, default and example, is in the variables reference.
Verification
- Direct (per node)
- Orchestrated Script
- Azure CLI
Run on each cluster node to verify the local Arc agent:
# Check Arc agent service
Get-Service himds | Format-Table Name, Status, StartType
# Show Arc agent registration details
& "$env:ProgramFiles\AzureConnectedMachineAgent\azcmagent.exe" show
# Test endpoint connectivity through Arc Gateway
& "$env:ProgramFiles\AzureConnectedMachineAgent\azcmagent.exe" check
PowerShell
No PowerShell script of its own in this task folder.
Invoke-ArcVerification-Orchestrated.ps1is a placeholder: it printsNOT IMPLEMENTED, changes nothing and exits with code 3. The earlierConfirm-ArcRegistration.ps1andConfirm-ArcRegistration-Orchestrated.ps1are removed. The scripts below read the Arc machines, and the Azure CLI tab has a script that checks them in Azure.
Script
| Script | What it does |
|---|---|
scripts/deploy/04-cluster-deployment/phase-03-os-configuration/Invoke-AzureLocalOsConfiguration.ps1 | In Plan mode the ArcRegistration step reports, per machine, whether its Arc machine exists and is Connected. It changes nothing. |
scripts/deploy/04-cluster-deployment/phase-05-cluster-deployment/Invoke-AzureLocalArmDeployment.ps1 | In -Mode Plan it runs the checks before Validate, read only. ArcMachinesConnected: each Arc machine exists, is Connected and is in the instance's resource group. ArcMachineNaming: each Arc machine is named after the host. |
Run
./Invoke-AzureLocalOsConfiguration.ps1 -InfrastructureFile ./infrastructure.yml -Step ArcRegistration
./Invoke-AzureLocalArmDeployment.ps1 -InfrastructureFile ./infrastructure.yml -OsConfigurationReport ./osconfig-report -Mode Plan -ReportDirectory ./arm-plan
Azure CLI
When to use: Check the task from a host that has the Azure CLI and not the Az PowerShell modules. The script is PowerShell 7 that calls
azand only reads Azure.
Script
| Script | What it does |
|---|---|
scripts/deploy/04-cluster-deployment/phase-04-arc-registration/task-04-verify-arc-registration-and-connectivity/azurecli/Test-ArcRegistration.azcli.ps1 | Verifies in Azure with the Azure CLI that the Azure Local machines of nodes[] are registered with Azure Arc and connected. Read only. Supports -WhatIf (lists the checks and runs none). |
Requires: PowerShell 7 and the Azure CLI, signed in with az login --tenant <azure.tenant_id>. Needs the Azure CLI extension connectedmachine (az extension add --name connectedmachine); the script does not install it.
It checks that each machine exists in azure.resource_group, that its status is Connected, and that the extensions of the Azure Local registration are Succeeded (they install some time after the registration, so run it again when one is still Creating). -TargetNode limits the checks to some nodes. Whether the machines reach the Arc endpoints runs on the machines and is not an Azure CLI task.
Run
./Test-ArcRegistration.azcli.ps1 -InfrastructureFile ./infrastructure.yml -WhatIf
./Test-ArcRegistration.azcli.ps1 -InfrastructureFile ./infrastructure.yml
Expected Results
| Check | Expected |
|---|---|
himds service | Running on every node |
azcmagent show → Agent Status | Connected |
azcmagent check | All endpoints reachable |
Get-AzConnectedMachine → Status | Connected for every node |
| Arc Gateway | Resource ID populated (if using gateway) |
Alternatives
The procedures in this task use the methods shown in the tabs above. The toolkit is PowerShell 7 only and has no Bash scripts. A few tasks that act on Azure also have an Azure CLI script written in PowerShell. The script status page of the toolkit lists which task has which script.
Navigation
| Previous | Up | Next |
|---|---|---|
| ← Task 03: Monitor Bootstrap Process | Phase 04: Arc Registration | --- |
Troubleshooting
| Symptom | Resolution |
|---|---|
himds service stopped | Start-Service himds — if it fails, check C:\ProgramData\AzureConnectedMachineAgent\Log\himds.log |
azcmagent show → Disconnected | Run azcmagent connect again or check network/proxy |
azcmagent check fails endpoints | Verify firewall rules allow *.guestconfiguration.azure.com, *.his.arc.azure.com |
Node missing from Get-AzConnectedMachine | Re-run Task 02 registration for that node |
| Extensions not provisioned | Extensions are deployed during cluster deployment — not required at this stage |
Azure Portal Verification
For manual confirmation:
- Navigate to Azure Arc → Machines in the Azure Portal
- Filter by resource group from
infrastructure.yml - Confirm all nodes show Connected status
- Click each node → Properties → verify subscription, resource group, and region
- If using Arc Gateway: Networking → Gateway configuration → verify gateway resource ID
Navigation: ← Task 03: Monitor Bootstrap | ↑ Phase 04 Index | → Phase 05: Cluster Deployment
Version Control
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0.0 | 2025-03-25 | Azure Local Cloud | Initial release |