Editar

Partilhar via

About updates for Azure Local, version 23H2

  • Artigo

Applies to: Azure Local, version 23H2

Important

Azure Stack HCI is now part of Azure Local. Product documentation renaming is in progress. Textual changes are complete, and visual updates will be finalized soon. Learn more.

This article describes the new update feature for this release of Azure Local, the benefits of the feature, and how to keep various components of your solution up to date.

Important

Azure Local, version 22H2 will reach end of service by May 2025. After that, you won't receive monthly security and quality updates that provide protection from the latest security threats. To continue receiving updates, we recommend updating your operating system to version 23H2.

If you're currently running an Azure Local, version 22H2 stretch cluster or managing Azure Local via System Center - Virtual Machine Manager, review the Supported workloads and configurations table for update timelines.

About the updates

Staying up to date with recent security fixes and feature improvements is important for all pieces of the Azure Local solution. The latest release introduces new features and components in addition to the OS, including the orchestrator (Lifecycle Manager).

The approach in this release provides a flexible foundation to integrate and manage various aspects of the Azure Local solution in one place. The orchestrator for updates is first installed during deployment and enables the new deployment experience including the management of the Azure Stack HCI operating system (OS), core agents and services, and the solution extension.

Here's an example of a new system deployment using the updates in this release:

Screenshot of ways to deploy and update your solution.

In this solution the Azure Stack HCI OS, agents and services, drivers, and firmware are automatically updated.

Some new agents and services can't be updated outside the orchestrator and availability of those updates depends on the specific feature. You might need to follow different processes to apply updates depending on the services you use.

Benefits

This new approach:

  • Simplifies update management by consolidating update workflows for various components into a single experience.

  • Keeps the system in a well-tested and optimal configuration.

  • Helps avoid downtime and effects on workloads with comprehensive health checks before and during an update.

  • Improves reliability with automatic retry and the remediation of known issues.

  • Whether managed locally or via the Azure portal, the common back-end drives a consistent experience.

Lifecycle cadence

The Azure Local follows the Modern Lifecycle policy. The Modern Lifecycle policy defines the products and services that are continuously serviced and supported. To stay current with this policy, you must stay within six months of the most recent release. To learn more about the support windows, see Azure Local release information.

Microsoft might release the following types of updates for the Azure Local:

Update Type Typical Cadence Description
Monthly Updates Monthly Monthly updates primarily contain quality and reliability improvements. They might include OS Latest Cumulative Updates ¹. Some updates require host system reboots, while others don't.
Baseline Updates Quarterly  Baseline updates include new features and improvements. They typically require host system reboots and might take longer.
Hotfixes As needed Hotfixes address blocking issues that could prevent regular monthly or baseline updates. To fix critical or security issues, hotfixes might be released sooner than monthly.
Solution Builder Extension As needed Solution Builder Extension² provides driver, firmware, and other partner content specific to the system solution used. They might require host system reboots.

¹ Quality updates released based on packages that contain monthly updates. These updates supersede the previous month's updates and contain both security and non-security changes.

² The Original Equipment Manufacturer determines the frequency of Solution Builder Extension updates.

Sometimes you might see updates to the latest patch level of your current baseline. If a new baseline is available, you might see the baseline update itself or the latest patch level of the baseline. Your system must stay within six months of the most recent baseline to consider it supported. For more information and a visualization of supported releases, see About Azure Local, version 23H2 releases.

The next sections provide an overview of components, along with methods and interfaces for updating your solution.

What's in the update package?

Solution updates managed by this feature contain new versions of the Azure Stack HCI OS, core agents and services, and the solution extension (depending on your system's hardware). Microsoft bundles these components into an update release and validates the combination of versions to ensure interoperability.

  • Operating System: These updates help you stay productive and protected. They provide users and IT administrators with the security fixes they need and protect devices so that unpatched vulnerabilities can't be exploited.

  • Agents and services: The orchestrator updates its own agents to ensure it has the recent fixes corresponding to the update. Azure Connected Machine agent and Arc Resource Bridge and its dependencies, get updated automatically to the latest validated version when Azure Local is updated.

  • Solution Builder Extension: Hardware vendors might choose to integrate with this feature to enhance the update management experience for their customers.

    • If a hardware vendor integrates with our update validation and release platform, the solution extension content includes the drivers and firmware, and the orchestrator manages the necessary system reboots within the same maintenance window. You can spend less time searching for updates and experience fewer maintenance windows.

This solution is the recommended way to update your Azure Local.

Note

Customer workloads aren't covered by this update solution.

User interfaces for updates

There are two interfaces you can use to apply available updates.

  • PowerShell (Command line)
  • The Azure portal

PowerShell

The PowerShell procedures apply to both single-node and multi-node systems that run with the orchestrator installed. For more information, see Update your Azure Local, version 23H2 via PowerShell.

The Azure portal

You can install Azure Local updates using the Azure Update Manager in the Azure portal. For more information, see Use Azure Update Manager to update your Azure Local, version 23H2.

Unsupported interfaces for updates

When you install updates for Azure Local, version 23H2 don't use the following interfaces:

  • SConfig
  • Windows Admin Center
  • Azure Update Manager from the Machines pane in the Azure portal
  • Updates pane from the machine (Machine-Azure Arc) resource page in the Azure portal
  • Manual runs of Cluster-Aware Updating

Using these interfaces can install out-of-band updates, which aren't supported within the lifecycle and may cause various issues on the system. Additionally, billing for update operations like periodic assessment, checking for updates, using the scheduler, and installing updates on the machine resource (Machine-Azure Arc) may occur.

Next steps

Learn to Understand update phases.

Learn how to Troubleshoot updates.