TL;DR: Microsoft publishes a PowerShell module called Support.AksArc that runs an authoritative set of health checks against MOC, Arc Resource Bridge, and AKS Arc on an Azure Local cluster, and can auto-remediate many of the common failures. Install and run it on each node in the cluster: run Test-SupportAksArcKnownIssues first to scan, then Invoke-SupportAksArcRemediation to fix what it finds. Use this before opening a support ticket for solution upgrade failures, MOC service crashes, or an offline Arc Resource Bridge.

Recommended action:

The module must be installed on every node in the Azure Local cluster, and the diagnostic and remediation cmdlets must be run locally on each node — not from a remote PowerShell session, and not from a single node against the rest of the cluster. Repeat steps 1–5 on every node before concluding the cluster is healthy.

  1. From an admin workstation, open a remote PowerShell session to a cluster node using your deployment user credentials:

    $cred = Get-Credential
Enter-PSSession -ComputerName "<Azure Local node IP>" -Credential $cred

  2. On that node, install or update the module from the PowerShell Gallery:

    Install-Module -Name Support.AksArc
Import-Module Support.AksArc -Force

    If it's already installed, refresh it:

    Update-Module -Name Support.AksArc
Remove-Module -Name Support.AksArc
Import-Module -Name Support.AksArc

  3. Exit the remote session (Exit-PSSession) and run the cmdlets directly on the node — for example by signing in via console, RDP, or a fresh local PowerShell on the node itself. The module's commands must run locally, not inside Enter-PSSession. List the available cmdlets:

    Get-Command -Module Support.AksArc

  4. Run the diagnostic health check:

    Test-SupportAksArcKnownIssues

    The output is a table of named tests, each with Passed or Failed plus a one-line message. Typical checks include Failover Cluster service responsiveness, MOC Cloud/Node/Host Agent presence and health, MOC patch level, certificate expiration, and stuck VMs or gallery images.

  5. If any test fails, run the remediation cmdlet to attempt an automated fix:

    Invoke-SupportAksArcRemediation

    Re-run Test-SupportAksArcKnownIssues afterward to confirm the failed test now passes.

  6. Repeat steps 1–5 on each remaining node in the cluster. Some checks (agent health, certificate state, patch level) are evaluated per node, and a passed result on one node does not imply the same on the others.

When to use this:

Run the module before opening a support ticket if you're seeing any of the following symptoms on a cluster registered with Azure and running 2311 or higher:

  • A solution upgrade fails during the MOC binaries stage.
  • A solution upgrade fails during the Arc Resource Bridge stage.
  • The MOC service won't stay online.
  • The Arc Resource Bridge is reporting offline.

In many cases the diagnostic surfaces the underlying cause (out-of-date MOC patch, expired cert, missing agent, stuck resource) and the remediation cmdlet resolves it without an engineer having to hand-investigate.

Why:

Support.AksArc is Microsoft's own diagnostic surface for the components that sit between Azure Local hardware and Azure (MOC, Arc Resource Bridge, AKS Arc). Microsoft updates the module's checks based on real incidents and telemetry, so it tends to catch the recurring failure modes faster than a manual investigation would. Because the remediation cmdlet implements the official fix paths, running it is preferred over hand-rolling the same fixes. The checks are evaluated against the local node, which is why the module has to be installed and run on each node for cluster-wide coverage.

Going forward:

Treat this as a routine first step for any MOC or Arc Resource Bridge issue, and run it on every node. Re-run Update-Module -Name Support.AksArc periodically (or before each diagnostic pass) so you're getting Microsoft's latest checks. If the module reports all-passed on every node but the symptom persists, that's the right point to open a support ticket — and including the Test-SupportAksArcKnownIssues output from each node in the ticket will save back-and-forth.

Optional details:

The module is published on the PowerShell Gallery at Support.AksArc. The cluster must be registered with Azure for the module to evaluate the Arc Resource Bridge state correctly. Microsoft's authoritative documentation, including the latest set of checks, lives at Use the Support Tool to troubleshoot and fix AKS Arc related issues.