Azure Local Cluster Management Tool: What’s New Since Public Preview

Four months ago, I announced the Public Preview of the Azure Local Cluster Management Tool—a browser-based experience designed to simplify day-to-day operations across Azure Local clusters, virtual machines, storage, networking, updates, and AKS workloads.

Since that announcement, the preview has moved quickly. Feedback from operators managing Azure Local at scale has helped shape a broad set of improvements focused on update reliability, fleet navigation, operator safety, platform administration, and AKS operations. This post highlights the most significant changes.

More Reliable Fleet Update Management

Operating updates across a large Azure Local estate is now more predictable. The update experience provides clearer status information, selects the correct run, and brings the details needed for planning into one place.

• Real ARM error visibility: Failed and actively running updates now surface the actual ARM task error instead of stale health-check warnings or missing step details.
• Correct update-run selection: The tool selects the most recent active or failed run, eliminating mismatched steps, incorrect elapsed times, and confusing diagnostics.
• Feature and cumulative updates side by side: Both update lanes are visible at once, making update planning clearer.
• Consistent SBE visibility: SBE Version, SBE Family, and minimum SBE requirements are surfaced across fleet and per-cluster views.

Better Navigation for Large Fleets

For environments with 100, 300, or more clusters, finding the right systems and keeping the interface responsive matters. The fleet experience now includes:

• Wildcard and multi-cluster search: Search for patterns such as AZL-*, AZ-Region-CL0?, or enter multiple cluster names at once.
• Complete solution-version filtering: Every installed version across the fleet is selectable, rather than only the five most common versions.
• Pagination for large estates: Fleet tables support 25, 50, or 100 rows per page to keep the interface responsive.
• Saved views on Fleet Update Status: Saved views created in All Clusters are also available on the update page.

Reliability and Operator Safety

A significant part of the work since Public Preview has focused on making actions safer, results easier to interpret, and failures easier to troubleshoot.

• Verified update actions: Start-update commands are validated against current cluster state and reported as Accepted, Rejected, or Indeterminate.
• Duplicate-submission protection: Manual and scheduled update actions are serialized and guarded to reduce accidental duplicate requests.
• Live ARM reads: Fleet Update Status prefers live ARM data when available, avoiding misleading empty or outdated results from stale snapshots.
• Clearer diagnostics: Update actions and ARM or Azure Resource Graph decision points include correlation details to simplify troubleshooting.

Platform and Administration Enhancements

• Force Poll Now: Administrators can immediately refresh a cluster’s background data during an outage or after connectivity has been restored.
• Improved cluster onboarding: Duplicate-name handling is cleaner and consistent across the user interface and API.
• Schema-drift protection: Legacy AKS columns in older databases no longer interrupt upgrades.

AKS Improvements

AKS operations have also become more consistent across connected clusters:

• Cross-cluster workload restart: Restart workloads across all connected clusters from a single page.
• Safer workload operations: Improved workload selection, RBAC alignment, and clearer GitOps information make fleet-wide AKS administration easier to understand and operate.

What’s Next

The Public Preview continues to evolve around real operators, real fleets, and real operational challenges. The improvements above are a direct result of practical use and feedback, and that feedback will continue to shape what comes next.

If you are running Azure Local, now is a good time to revisit the tool, test the latest update and fleet-management improvements, and share the workflows or pain points you would like to see addressed next.