Azure Local update readiness check critical

Question

Azure Local update readiness check critical

Alex Boisvert 0

We have recently deployed a 4 node Azure Local cluster, I saw there were updates available on the portal but the update readiness returns critical status and on the "view details" page it only says to contact support, which directs me to this Q&A page
I have a warning that the azure connected machine agent is not the expected version and it also says to contact support for this

Sujitha Lakkireddy 85 Reputation points Microsoft External Staff Moderator

2026-08-06T16:33:30.9+00:00
Hi Alex Boisvert,

Thank you for choosing Microsoft Q&A forum.

For Azure Local, please avoid manually updating the Azure Connected Machine Agent on the cluster nodes unless Microsoft Support/Product Group specifically recommends it for this case.

Azure Local updates are managed through the Lifecycle Manager/orchestrator. The Azure Local solution update package can include the OS, core agents and services, Azure Connected Machine Agent, Arc resource bridge dependencies, solution extensions, drivers, and firmware. These components are updated to a validated version through the Azure Local update workflow. Out-of-band updates for individual Azure Local components are not supported and may cause compatibility issues.

A Critical status in Update readiness means the update is blocked until the failing readiness check is remediated. If the portal only shows “Contact support,” please collect the detailed readiness check output from one of the Azure Local nodes by running the following commands in an elevated PowerShell session:

Get-SolutionUpdateEnvironment

Then run:

$FullResults = Get-SolutionUpdateEnvironment -FullHealthCheckDetails

$Failures = $FullResults.HealthCheckResult | Where-Object {

$.Status -ne "SUCCESS" -and $.Severity -ne "INFORMATIONAL"

}

$Failures | Format-List *

Please review/share the following fields from the output(in private message):

Title

Status

Severity

Description

Remediation

AdditionalData

FailedMachines, if present

CurrentVersion

PackageVersions

State

HealthState

If any remediation is listed in the PowerShell output, apply that remediation first, then go back to Azure Update Manager and run Check again/Try again. If this was part of a failed update run, resume the update after the readiness check passes.

Regarding the warning that the Azure Connected Machine Agent is not the expected version, this should normally be remediated through the Azure Local solution update path, not by manually installing the latest Arc agent. Azure Local uses validated component versions, so the “latest” public Azure Arc agent version may not always be the expected validated version for that Azure Local release.

References:

Troubleshoot solution updates for Azure Local:

https://learn.microsoft.com/en-us/azure/azure-local/update/update-troubleshooting-23h2

About updates for Azure Local:

https://learn.microsoft.com/en-us/azure/azure-local/update/about-updates-23h2

Manage Azure Connected Machine Agent versions:

https://learn.microsoft.com/en-us/azure/azure-arc/servers/manage-agent

Azure Connected Machine Agent release notes:

https://learn.microsoft.com/en-us/azure/azure-arc/servers/agent-release-notes

1 answer

Your answer

Answer 1

Alex Boisvert 0

I'm trying to run the powershell commands but I get errors at the line:
$.Status -ne "SUCCESS" -and $.Severity -ne "INFORMATIONAL"

Alex Boisvert 0 Reputation points

2026-08-07T14:43:05.27+00:00

$.Status : The term '$.Status' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Sujitha Lakkireddy 85 Reputation points Microsoft External Staff Moderator

2026-08-07T15:12:06.8466667+00:00

Hi Alex Boisvert,

The error is most likely because the PowerShell automatic variable $_ was not copied or rendered correctly.

Please make sure the command uses $.Status and $.Severity, including the underscore character after the dollar sign.

Use this exact command in an elevated PowerShell session:

$FullResults = Get-SolutionUpdateEnvironment -FullHealthCheckDetails

$Failures = $FullResults.HealthCheckResult | Where-Object {

$.Status -ne "SUCCESS" -and $.Severity -ne "INFORMATIONAL"

}

$Failures | Format-List *

In PowerShell, $_ represents the current object being processed in the pipeline. So in this command:

$_.Status

means “check the Status property of the current health check result,” and:

$_.Severity

means “check the Severity property of the current health check result.”

If the command is copied from a webpage or Q&A thread without a code block, the underscore may be interpreted as formatting and the command can break. Please copy the command from the code block above or type $_ manually.

You can also try this one-line version:

$FullResults = Get-SolutionUpdateEnvironment -FullHealthCheckDetails; $Failures = $FullResults.HealthCheckResult | Where-Object { $.Status -ne "SUCCESS" -and $.Severity -ne "INFORMATIONAL" }; $Failures | Format-List *

After running it, please share the output that includes Title, Status, Severity, Description, Remediation, AdditionalData, and FailedMachines if present(in private message)
Alex Boisvert 0 Reputation points

2026-08-07T15:31:35.6166667+00:00

The undercore was indeed missing, the command runs correctly with it

I don't seem to be able to send you a private message, I think you have to initiate the private conversation first