MicrosoftDocs · learn-build-service-prod · Jan 27, 2026 · Jan 27, 2026 · Jan 27, 2026 · Jan 27, 2026
diff --git a/azure-local/manage/unregister-register-machine.md b/azure-local/manage/unregister-register-machine.md
@@ -4,7 +4,7 @@ description: Learn how to unregister and re-register Azure Local machines withou
 ms.topic: how-to
 ms.author: alkohli
 author: alkohli
-ms.date: 11/20/2025
+ms.date: 01/27/2026
 ms.subservice: hyperconverged
 ---
 
@@ -15,6 +15,8 @@ ms.subservice: hyperconverged
 
 This article provides guidance on how to unregister and re-register Azure Local machines without having to install the operating system (OS) again. This method uses PowerShell cmdlets and applies to registration with and without Azure Arc gateway.
 
+> [!IMPORTANT]
+> This guidance applies only to devices that haven't been deployed yet.
 
 ## About reregistration Azure Local machines
 

diff --git a/operator-nexus/.openpublishing.redirection.operator-nexus.json b/operator-nexus/.openpublishing.redirection.operator-nexus.json
@@ -102,7 +102,7 @@
     },
     {
       "source_path": "release-note-2404.2.md",
-      "redirect_url": "/azure/operator-nexus/release-notes-2404-2",
+      "redirect_url": "/azure/operator-nexus",
       "redirect_document_id": false
     },
     {
@@ -114,7 +114,7 @@
       "source_path": "concepts-ab-staged-commit-configuration-update-commit-workflow-v3.md",
       "redirect_url": "concepts-ab-staged-commit-configuration-update-commit-workflow",
       "redirect_document_id": false
-    },
+    },   
     {
       "source_path": "howto-use-ab-staged-commit-configuration-update-commit-workflow-v3.md",
       "redirect_url": "howto-use-ab-staged-commit-configuration-update-commit-workflow",

diff --git a/operator-nexus/TOC.yml b/operator-nexus/TOC.yml
@@ -542,10 +542,4 @@
       href: reference-operator-nexus-skus.md
     - name: Password By Key Vault Reference
       href: reference-key-vault-credential.md
-- name: Release Notes
-  items:
-    - name: 2024
-      expanded: false
-      items:
-        - name: 2404.2
-          href: release-notes-2404-2.md
+
diff --git a/operator-nexus/concepts-hardware-validation-overview.md b/operator-nexus/concepts-hardware-validation-overview.md
@@ -56,3 +56,15 @@ Up to date Azure Operator Nexus firmware specs, and N-1 and N-2 versions can be
 ## BIOS boot configuration update
 
 HWV verifies that the BIOS boot configuration meets the requirements for successful bootstrapping. If any settings are incorrect, HWV automatically updates them to match the required specifications.
+
+## Troubleshooting hardware validation failures
+
+If hardware validation fails during cluster deployment or a BMM Replace action, see [Troubleshoot hardware validation failure](./troubleshoot-hardware-validation-failure.md) for detailed troubleshooting procedures organized by validation category.
+
+## Related operations
+
+Hardware validation is automatically triggered during:
+- Initial cluster deployment
+- [BMM Replace actions](./howto-baremetal-functions.md#replace-a-bare-metal-machine)
+
+After hardware repairs are completed, you must run a Replace action to re-validate and provision the BMM.
diff --git a/operator-nexus/howto-baremetal-functions.md b/operator-nexus/howto-baremetal-functions.md
@@ -62,6 +62,22 @@ Use the following guidance to determine which action best fits your situation:
 | BMC credentials need manual rotation                 | Replace            |
 | Firmware reconciliation needed                       | Replace            |
 
+### Quick decision guide
+
+**Start here if you're unsure which action to use:**
+
+1. **Did you physically replace or repair hardware?** → Use [Replace](#replace-a-bare-metal-machine)
+2. **Is the machine unresponsive but hardware is healthy?** → Use [Restart](#restart-a-bare-metal-machine)
+3. **Do you need a clean OS installation without hardware changes?** → Use [Reimage](#reimage-a-bare-metal-machine)
+4. **Do you need to prevent new workloads temporarily?** → Use [Cordon](#make-a-bare-metal-machine-unschedulable-cordon)
+5. **Is the machine powered off and needs to come online?** → Use [Start](#start-a-bare-metal-machine)
+
+**For troubleshooting specific status conditions, see:**
+- [Warning status messages](./troubleshoot-bare-metal-machine-warning.md)
+- [Degraded status](./troubleshoot-bare-metal-machine-degraded.md)
+- [Provisioning failures](./troubleshoot-bare-metal-machine-provisioning.md)
+- [Hardware validation failures](./troubleshoot-hardware-validation-failure.md)
+
 ## Control plane node considerations
 
 Control plane nodes require extra caution when performing lifecycle actions. The platform implements special handling for control plane nodes to maintain cluster quorum and availability:
@@ -343,4 +359,6 @@ Code: None
 Message: Networking test(s) failed: [NIC.Slot.6-1-1_LinkStatus] expected: up; observed: Down; [Additional logs: Link failure detected on NIC.Slot.6-1-1; Unable to perform cabling check on PCI Slot 6]
 ```
 
-For more information about troubleshooting hardware validation failures, see [Troubleshoot Hardware Validation Failure](./troubleshoot-hardware-validation-failure.md).
+For complete hardware validation troubleshooting procedures organized by failure category (System Info, Drive Info, Network Info, Health Info, Boot Info), see [Troubleshoot Hardware Validation Failure](./troubleshoot-hardware-validation-failure.md).
+
+To understand what hardware validation checks and when it runs, see [Hardware Validation Overview](./concepts-hardware-validation-overview.md).
diff --git a/operator-nexus/release-notes-2404-2.md b/operator-nexus/release-notes-2404-2.md
diff --git a/operator-nexus/troubleshoot-bare-metal-machine-provisioning.md b/operator-nexus/troubleshoot-bare-metal-machine-provisioning.md
@@ -18,6 +18,9 @@ Provisioning uses the Preboot eXecution Environment (PXE) interface to load the
 
 [!INCLUDE [prerequisites-azure-cli-bare-metal-machine-actions](./includes/baremetal-machines/prerequisites-azure-cli-bare-metal-machine-actions.md)]
 
+1. For BMC diagnostic access: See [Manage emergency access to a Bare Metal Machine using the `az networkcloud cluster bmckeyset`](./howto-baremetal-bmc-ssh.md)
+1. For running diagnostic commands on control plane nodes: See [Troubleshoot Bare-Metal Machines by Using the run-read Command](./howto-baremetal-run-read.md)
+
 ## Bare Metal Machine roles
 
 For a specific version, roles are required to manage and operate the underlying Kubernetes cluster.
@@ -170,6 +173,8 @@ racadm --nocertwarn -r $IP -u $BMC_USR -p $BMC_PWD getsysinfo | grep "MAC Addres
 racadm --nocertwarn -r $IP -u $BMC_USR -p $BMC_PWD getsysinfo | grep "NIC.Embedded.1-1-1"  #Boot MAC
 ```
 
+For detailed BMC access procedures and additional diagnostic commands, see [Manage emergency access to a Bare Metal Machine using the `az networkcloud cluster bmckeyset`](./howto-baremetal-bmc-ssh.md).
+
 If the MAC address supplied to the cluster is incorrect, use the Bare Metal Machine `replace` action at [Bare Metal Machine actions](howto-baremetal-functions.md) to correct the addresses.
 
 ### Ping test BMC connectivity

diff --git a/operator-nexus/troubleshoot-bare-metal-machine-warning.md b/operator-nexus/troubleshoot-bare-metal-machine-warning.md
@@ -14,6 +14,12 @@ ms.reviewer: ekarandjeff
 
 This document provides basic troubleshooting information for Bare Metal Machine (BMM) resources that are reporting a _Warning_ message in the BMM detailed status message.
 
+## Prerequisites
+
+- Access to the Azure portal or Azure CLI
+- Permissions to view and manage Bare Metal Machine resources
+- For diagnostic commands: SSH access via BareMetalMachineKeySet (see [Manage emergency access to a Bare Metal Machine](./howto-baremetal-bmm-ssh.md))
+
 ## Symptoms
 
 The Detailed status message of the Bare Metal Machine (Operator Nexus) resource includes one or more of the following.
@@ -55,7 +61,8 @@ az networkcloud baremetalmachine run-read-command \
 - Replace `<ResourceGroup_Name>` with the name of the resource group containing the BMM resources.
 - Replace `rack1control01` with the name of a BMM resource for a healthy Kubernetes control plane node, from which to execute the `kubectl get` command.
 - Replace `rack1compute01` with the name of the affected BMM.
-- For more information about the `run-read-command` feature, see [BareMetal Run-Read Execution](./howto-baremetal-run-read.md).
+
+For more information about the `run-read-command` feature and available diagnostic commands, see [Troubleshoot Bare-Metal Machines by Using the run-read Command](./howto-baremetal-run-read.md).
 
 Review the `lastTransitionTime` and `message` fields for more information about the corresponding error condition, as shown in the following example output.
 

diff --git a/operator-nexus/troubleshoot-hardware-validation-failure.md b/operator-nexus/troubleshoot-hardware-validation-failure.md
@@ -16,6 +16,8 @@ HWV is run as part of a cluster deploy action and a bare metal `replace` action.
 HWV validates a Bare Metal Machine (BMM) by executing test cases against the baseboard management controller (BMC).
 The Azure Operator Nexus platform is deployed on Dell servers. Dell servers use the integrated Dell remote access controller (iDRAC), which is the equivalent of a BMC.
 
+For background information about hardware validation, when it runs, and what it checks, see [Azure Operator Nexus hardware validation overview](./concepts-hardware-validation-overview.md).
+
 [!INCLUDE [prerequisites-azure-cli-bare-metal-machine-actions](./includes/baremetal-machines/prerequisites-azure-cli-bare-metal-machine-actions.md)]
 
 1. Request access to the cluster's Log Analytics workspace (LAW).