Azure Update Manager: Not Reflecting Cluster Update Status Since 7/31/2026

Question

Azure Update Manager: Not Reflecting Cluster Update Status Since 7/31/2026

Andrew D 0

Problem description

I am experiencing an issue where Azure Update Manager and the Azure portal are not reflecting the update status of my Azure Stack HCI cluster since July 31, 2026. The cluster continues to report successful update activity locally via PowerShell, and the environment appears healthy and connected, but the portal shows outdated information.

Environment

Azure Update Manager, Azure Stack HCI, East US region, three-node cluster, Azure Local deployment.

What I've already tried

I validated the cluster state directly on the nodes using PowerShell, confirming successful updates and a healthy environment. I compared local PowerShell state with the Azure portal, noting the disparity since late July 2026. I reviewed the cluster activity log and attempted to restart the Cloud Management cluster group twice, but the Azure portal still does not reflect the current update state. I also checked the environment details with PowerShell commands such as Get-SolutionUpdate, Get-SolutionUpdateEnvironment, and Get-AzureStackHci, which indicated success and recent updates.

Current status

I am seeking guidance on how to reinitialize the cloud publishing component or troubleshoot the synchronization issue to ensure the Azure portal accurately reflects the cluster's update status. I plan to install update 11.2510.1002.93 via PowerShell and want to confirm if the cluster should be left in its current state beforehand. Additionally, I would like advice on whether to proceed with the update while the synchronization issue is being investigated.

Andrew D 0 Reputation points

2026-11-05T13:56:12.6733333+00:00

Update (11/5/2026): I installed 11.2510.1002.93 via PowerShell on 11/4. It completed successfully, HealthState is Success, and 12.2510 (24H2) now shows as Ready on the cluster.

The Azure portal still shows the cluster at 10.2503.0.13 with the 2025.04 update as Failed and the last health check on 7/31/2026, more than 12 hours after the update completed. "Check for updates" is disabled in the portal.

Sync-AzureStackHCI succeeds and the cluster shows Connected. The Activity log shows clusters/write and arcSettings/write succeeding twice daily, but no updates, updateSummaries, or updateRuns writes at any point since at least late October, including after two completed updates. The Cloud Management cluster group has been restarted twice with no change.

Has anyone seen the update-state publishing path stop while other cluster-to-Azure sync keeps working? Is there a supported way to reinitialize it?

Your answer

Andrew D 0 Reputation points

2026-11-05T13:56:12.6733333+00:00

Update (11/5/2026): I installed 11.2510.1002.93 via PowerShell on 11/4. It completed successfully, HealthState is Success, and 12.2510 (24H2) now shows as Ready on the cluster.

The Azure portal still shows the cluster at 10.2503.0.13 with the 2025.04 update as Failed and the last health check on 7/31/2026, more than 12 hours after the update completed. "Check for updates" is disabled in the portal.

Sync-AzureStackHCI succeeds and the cluster shows Connected. The Activity log shows clusters/write and arcSettings/write succeeding twice daily, but no updates, updateSummaries, or updateRuns writes at any point since at least late October, including after two completed updates. The Cloud Management cluster group has been restarted twice with no change.

Has anyone seen the update-state publishing path stop while other cluster-to-Azure sync keeps working? Is there a supported way to reinitialize it?