What's new in Azure Stack HCI, version 23H2

The 2405 release train includes the following releases:

Features and improvements in 2405.1

This is primarily a bug fix release with a few improvements.

• Custom storage IPs for add and repair server scenarios: Starting this release, it is possible to add servers or repair servers to the Azure Stack HCI cluster using custom IPs for the storage intent network adapters.
• Improved outbound connectivity check: Starting this release, improvements were made to the outbound connectivity requirement validation in the environment checker.
• Reliabiltiy improvements were made in this release for partner health checks implemented in their Solution Builder Extensions.
• Rotation of Arc Resource Bridge (ARB) service principal credentials: Starting this release, you can rotate the service principal credentials used by ARB.
• Multiple bug fixes related to Updates were made in this release.

For more information on bug fixes, see the Fixed issues list.

Features and improvements in 2405

Here are the features and improvements in this release.

Deployment changes

• Active Directory integration - In this release, an issue related to the use of a large Active Directory that results in timeouts when adding users to the local administrator group, is fixed.

• New Azure Resource Manager (ARM) template - This release has a new ARM template for deployment that simplifies the resource creation dependencies. The new template creation also includes multiple fixes around the missing mandatory fields.

• Secret rotation improvements - In this release, improvements were made to the secret rotation flow.

  • The secret rotation PowerShell command Set-AzureStackLCMUserPassword now supports a new parameter to skip the confirmation message. This parameter is useful when automating secret rotation.
  • Reliability improvements were made around the services not restarting in a timely manner.

• SBE improvements include:

  • A new PowerShell command to update the Solution Builder Extension partner property values is provided at the time of deployment.
  • Fixing an issue that prevents the update service to respond to requests after a Solution Builder Extension only update run.

• Add server and Repair server fixes include:

  • An issue that prevents a node from joining Active Directory during the add server operation.
  • Enabling deployment when a disjoint namespace is used.

• Reliability enhancements include:

  • Changes for Network ATC when setting up the host networking configuration with certain network adapter types.
  • Changes when detecting the firmware versions for disk drives.

• This release contains a fix for a deployment issue that is encountered when setting the diagnostic level in Azure and the device.

For more information, see the Fixed issues list in 2405.

Updates changes

This release contains the following changes for updates:

• Starting this release, an adjusted naming schema is introduced for updates. This schema allows for the identification of feature versus cumulative updates.

• This release contains reliability improvements:

  • For the update notifications for health check results sent from the device to Azure Update Manager. In certain instances, the message size was too large and results weren't shown in the Update Manager.
  • For reporting the cluster update progress to the orchestrator.

• This release has bug fixes for various issues including:

  • A file lock issue that could cause update failures for the trusted launch VM agent (IGVM).
  • An issue that prevented the orchestrator agent from restarting during an update run.
  • A rare condition where the update service took a long time to discover or start an update.
  • An issue for Cluster-Aware Updating (CAU) interaction with the orchestrator when an update in progress is reported by CAU.

For more information, see the Fixed issues list in in 2405.

Environment checker changes

In this release, changes to the environment checker include several new checks:

• A new check is added to ensure the inbox drivers on the physical network adapters are not in use. The provided OEM or manufacturer latest drivers must be installed before deployment.
• A new check is added to ensure the link speed across physical network adapters on the same intent is identical.
• A new check is added to ensure RDMA is operational on the storage network adapters before deployment.
• A new check is added to validate the infrastructure IP addresses defined during deployment have outbound connectivity and can resolve the DNS.
• A new check is added to ensure the DNS server value is not empty on the management IP address.
• A new check is added to make sure that there is only 1 IP address on the management network adapter.
• A new check is added to ensure that the minimum bandwidth required for RDMA storage adapters is at least 10 Gb.
• Check that the uplink connectivity in any physical network adapters assigned to Network ATC intents is up.
• Improved the ability to handle adapters that do not expose the VLAN ID field correctly.

Observability changes

This release contains the following improvements to observability:

• When starting a log collection, a warning message now advises you to limit the log collection to 24 hours.
• Deployment logs are automatically collected by default.
• The newly added Test-observability feature validates whether the telemetry and diagnostic data can be successfully sent to Microsoft.

Arc VM management changes

• This release contains new documentation that provides guidance on VM image creation starting with a CentOS image or a Red Hat Enterprise Linux (RHEL) image. For more information, see:
  • Prepare CentOS Linux image for Azure Stack HCI virtual machines (preview).
  • Prepare Red Hat Enterprise image for Azure Stack HCI virtual machines (preview).

Azure portal, extensions, and resource provider changes

Here are the changes related to the Azure portal, extensions, and resource providers:

• In this release, an issue was fixed that prevented from showing a failed deployment in the Cluster overview when the deployment was canceled.
• The Retry button in Azure portal is renamed to Resume as the deployment continues from the step that it failed.
• The new clusters deployed in this release have resource locks enabled to protect against accidental deletion.
• This release changes the behavior to not delete the Arc server resources when the Azure Stack HCI cluster resource is deleted.

AKS on Azure Stack HCI, version 23H2

For a list of the changes and improvements in AKS on Azure Stack HCI, version 23H2, see What's new in AKS on Azure Stack HCI, version 23H2.

The 2402 release train includes the following releases:

Features and improvements in 2402.4

This is primarily a bug fix release. See the Fixed issues list to understand the bug fixes.

Features and improvements in 2402.3

This is primarily a bug fix release. See the Fixed issues list to understand the bug fixes.

Features and improvements in 2402.2

This is primarily a bug fix release with a few enhancements. See the Fixed issues list to understand the bug fixes. Here's the list of enhancements:

• Region expansion - The following new regions are now supported on your Azure Stack HCI: Southeast Asia, India Central, Canada Central, Japan East, and South Central US. For more information, see Azure Stack HCI supported regions.
• Deployment changes - A permission check was added to the Azure portal deployment experience to check for sufficient permissions. For more information, see Deploy via Azure portal.
• Update changes - A notification banner was included in the update experience that informs you when the new updates are available. For more information, see Update your Azure Stack HCI via the Azure Update Manager.

Features and improvements in 2402.1

This is primarily a bug fix release. See the Fixed issues list to understand the bug fixes.

Features and improvements in 2402

This section lists the new features and improvements in the 2402 release of Azure Stack HCI, version 23H2.

New built in security role

This release introduces a new Azure built-in role called Azure Resource Bridge Deployment Role, to harden the security posture for Azure Stack HCI, version 23H2. If you provisioned a cluster before January 2024, then you must assign the Azure Resource Bridge Deployment User role to the Arc Resource Bridge principal.

The role applies the concept of least amount of privileges and must be assigned to the service principal: clustername.arb before you update the cluster.

To take advantage of the constraint permissions, remove the permissions that were applied before. Follow the steps to Assign an Azure RBAC role via the portal. Search for and assign the Azure Resource Bridge Deployment role to the member: <deployment-cluster-name>-cl.arb.

An update health check is also included in this release that confirms that the new role is assigned before you apply the update.

Changes to Active Directory preparation

Beginning this release, the Active Directory preparation process is simplified. You can use your own existing process to create an Organizational Unit (OU), a user account with appropriate permissions, and with Group policy inheritance blocked for the Group Policy Object (GPO). You can also use the Microsoft provided script to create the OU. For more information, see Prepare Active Directory.

Region expansion

Azure Stack HCI, version 23H2 solution is now supported in Australia. For more information, see Azure Stack HCI supported regions.

New documentation for network considerations

We're also releasing new documentation that provides guidance on network considerations for the cloud deployment of Azure Stack HCI, version 23H2. For more information, see Network considerations for Azure Stack HCI.

The 2311 release train includes the following releases:

Features and improvements in 2311.5

This is primarily a bug fix release. See the Fixed issues list to understand the bug fixes.

Features and improvements in 2311.4

This is primarily a bug fix release. See the Fixed issues list to understand the bug fixes.

Features and improvements in 2311.3

A new Azure built-in role called Azure Resource Bridge Deployment Role is available to harden the security posture for Azure Stack HCI, version 23H2. If you provisioned a cluster before January 2024, then you must assign the Azure Resource Bridge Deployment User role to the Arc Resource Bridge service principal.

The role applies the concept of the least amount of privileges and must be assigned to the Azure resource bridge service principal, clustername.arb, before you update the cluster.

You must remove the previously assigned permissions to take advantage of the constraint permission. Follow the steps to Assign an Azure RBAC role via the portal. Search for and assign the Azure Resource Bridge Deployment role to the member: <deployment-cluster-name>-cl.arb.

Additionally, this release includes an update health check that confirms the assignment of the new role before applying the update.

Features and improvements in 2311.2 GA

This section lists the new features and improvements in the 2311.2 General Availability (GA) release for Azure Stack HCI, version 23H2.

In this generally available release of the Azure Stack HCI, version 23H2, all the features that were available with the 2311 preview releases are also now generally available. In addition, the following improvements and enhancements are available:

Deployment changes

With this release:

• Deployment is supported using existing storage accounts.
• A failed deployment can be run using the Rerun deployment option that becomes available in the cluster Overview page.
• Network settings such as storage traffic priority, cluster traffic priority, storage traffic bandwidth reservation, jumbo frames, and RDMA protocol can all be customized.
• Validation must be started explicitly via the Start validation button.

For more information, see Deploy via Azure portal.

Add server and repair server changes

• Bug fixes in the Add server and Repair server scenarios. For more information, see the Fixed issues in 2311.2.

Arc VM management changes

In this release:

• Guest management is available via Azure CLI. For more information, see Enable guest management.
• Proxy is supported for Arc VMs. For more information, see Set up proxy for Arc VMs on Azure Stack HCI.
• Storage path selection is available during the VM image creation via the Azure portal. For more information, see Create a VM image from Azure Marketplace via the Azure portal.

Migration of Hyper-V VMs to Azure Stack HCI (preview)

You can now migrate Hyper-V VMs to Azure Stack HCI using Azure Migrate. This feature is currently in Preview. For more information, see Migration of Hyper-V VMs using Azure Migrate to Azure Stack HCI (preview).

Monitoring changes

In the Azure portal, you can now monitor platform metrics of your cluster by navigating to the Monitoring tab on your cluster's Overview page. This tab offers a quick way to view graphs for different platform metrics. You can select any graph to open it in Metrics Explorer for a more in-depth analysis. For more information, see Monitor Azure Stack HCI through the Monitoring tab.

Security via Microsoft Defender for Cloud (preview)

You can now use Microsoft Defender for Cloud to help improve the security posture of your Azure Stack HCI environment and protect against existing and evolving threats. This feature is currently in Preview. For more information, see Microsoft Defender on Cloud for Azure Stack HCI (Preview).

Supported workloads

Starting with this release, the following workloads are generally available on Azure Stack HCI:

• Azure Kubernetes Service (AKS) on Azure Stack HCI. For more information, see Create Kubernetes clusters.

  In addition, AKS on HCI has a new CLI extension and Azure portal experience, Support for logical networks, Support for taints and labels, Support for upgrade via Azure CLI, Support for Nvidia A2 and more. For details, see What's new in AKS on Azure Stack HCI, version 23H2.

• Azure Virtual Desktops (AVD) on Azure Stack HCI. For more information, see Deploy AVD on Azure Stack HCI.

Features and improvements in 2311

This section lists the new features and improvements in the 2311 release of Azure Stack HCI, version 23H2. Additionally, this section includes features and improvements that were originally released for 2310 starting with cloud-based deployment.

Cloud-based deployment

For servers running Azure Stack HCI, version 23H2, you can perform new deployments via the cloud. You can deploy an Azure Stack HCI cluster in one of the two ways - via the Azure portal or via an Azure Resource Manager deployment template.

For more information, see Deploy Azure Stack HCI cluster using the Azure portal and Deploy Azure Stack HCI via the Azure Resource Manager deployment template.

Cloud-based updates

This new release has the infrastructure to consolidate all the relevant updates for the OS, software agents, Azure Arc infrastructure, and OEM drivers and firmware into a unified monthly update package. This comprehensive update package is identified and applied from the cloud through the Azure Update Manager tool. Alternatively, you can apply the updates using the PowerShell.

For more information, see Update your Azure Stack HCI cluster via the Azure Update Manager and Update your Azure Stack HCI via the PowerShell.​

Cloud-based monitoring

Respond to health alerts

This release integrates the Azure Monitor alerts with Azure Stack HCI so that any health alerts generated within your on-premises Azure Stack HCI system are automatically forwarded to Azure Monitor alerts. You can link these alerts with your automated incident management systems, ensuring timely and efficient response.

For more information, see Respond to Azure Stack HCI health alerts using Azure Monitor alerts.

Monitor metrics

This release also integrates the Azure Monitor metrics with Azure Stack HCI so that you can monitor the health of your Azure Stack HCI system via the metrics collected for compute, storage, and network resources. This integration enables you to store cluster data in a dedicated time-series database that you can use to analyze data from your Azure Stack HCI system.

For more information, see Monitor Azure Stack HCI with Azure Monitor metrics.

Enhanced monitoring capabilities with Insights

With Insights for Azure Stack HCI, you can now monitor and analyze performance, savings, and usage insights about key Azure Stack HCI features, such as ReFS deduplication and compression. To use these enhanced monitoring capabilities, ensure that your cluster is deployed, registered, and connected to Azure, and enrolled in monitoring. For more information, see Monitor Azure Stack HCI features with Insights.

Azure Arc VM management

Beginning this release, the following Azure Arc VM management capabilities are available:

• Simplified Arc Resource Bridge deployment. The Arc Resource Bridge is now deployed as part of the Azure Stack HCI deployment. For more information, see Deploy Azure Stack HCI cluster using the Azure portal.
• New RBAC roles for Arc VMs. This release introduces new RBAC roles for Arc VMs. For more information, see Manage RBAC roles for Arc VMs.
• New Azure consistent CLI. Beginning this preview release, a new consistent command line experience is available to create VM and VM resources such as VM images, storage paths, logical networks, and network interfaces. For more information, see Create Arc VMs on Azure Stack HCI.
• Support for static IPs. This release has the support for static IPs. For more information, see Create static logical networks on Azure Stack HCI.
• Support for storage paths. While default storage paths are created during the deployment, you can also specify custom storage paths for your Arc VMs. For more information, see Create storage paths on Azure Stack HCI.
• Support for Azure VM extensions on Arc VMs on Azure Stack HCI. Starting with this preview release, you can also enable and manage the Azure VM extensions that are supported on Azure Arc, on Azure Stack HCI Arc VMs created via the Azure CLI. You can manage these VM extensions using the Azure CLI or the Azure portal. For more information, see Manage VM extensions for Azure Stack HCI VMs.
• Trusted launch for Azure Arc VMs. Azure Trusted Launch protects VMs against boot kits, rootkits, and kernel-level malware. Starting this preview release, some of those Trusted Launch capabilities are available for Arc VMs on Azure Stack HCI. For more information, see Trusted launch for Arc VMs.

AKS on Azure Stack HCI, version 23H2

Starting with this release, you can run Azure Kubernetes Service (AKS) workloads on your Azure Stack HCI system. AKS on Azure Stack HCI, version 23H2 uses Azure Arc to create new Kubernetes clusters on Azure Stack HCI directly from Azure. For more information, see What's new in AKS on Azure Stack HCI, version 23H2.

The following Kubernetes cluster deployment and management capabilities are available:

• Simplified infrastructure deployment on Azure Stack HCI. In this release, the infrastructure components of AKS on Azure Stack HCI 23H2 including the Arc Resource Bridge, Custom Location, and the Kubernetes Extension for the AKS Arc operator, are all deployed as part of the Azure Stack HCI deployment. For more information, see Deploy Azure Stack HCI cluster using the Azure portal (preview).
• Integrated infrastructure upgrade on Azure Stack HCI. The whole lifecycle management of AKS Arc infrastructure follows the same approach as the other components on Azure Stack HCI 23H2. For more information, see Infrastructure component updates for AKS on Azure Stack HCI (preview).
• New Azure consistent CLI. Starting with this preview release, a new consistent command line experience is available to create and manage Kubernetes clusters.
• Cloud-based management. You can now create and manage Kubernetes clusters on Azure Stack HCI with familiar tools such as Azure portal and Azure CLI. For more information, see Create Kubernetes clusters using Azure CLI.
• Support for upgrading a Kubernetes cluster using Azure CLI. You can use Azure CLI to upgrade the Kubernetes cluster to a newer version and apply the OS version updates. For more information, see Upgrade an Azure Kubernetes Service (AKS) cluster (preview).
• Support for Azure Container Registry to deploy container images. In this release, you can deploy container images from a private container registry using Azure Container Registry to your Kubernetes clusters running on Azure Stack HCI. For more information, see Deploy from private container registry to on-premises Kubernetes using Azure Container Registry and AKS Arc.
• Support for managing and scaling the node pools. For more information, see Manage multiple node pools in AKS Arc.
• Support for Linux and Windows Server containers. For more information, see Create Windows Server containers.

Security capabilities

The new installations with this release of Azure Stack HCI start with a secure-by-default strategy. The new version #has a tailored security baseline coupled with a security drift control mechanism and a set of well-known security features enabled by default. This release provides:

• A tailored security baseline with over 300 security settings configured and enforced with a security drift control mechanism. For more information, see Security baseline settings for Azure Stack HCI.
• Out-of-box protection for data and network with SMB signing and BitLocker encryption for OS and Cluster Shared Volumes. For more information, see BitLocker encryption for Azure Stack HCI.
• Reduced attack surface as Windows Defender Application Control is enabled by default and limits the applications and the code that you can run on the core platform. For more information, see Windows Defender Application Control for Azure Stack HCI.

Support for web proxy

This release supports configuring a web proxy for your Azure Stack HCI system. You perform this optional configuration if your network uses a proxy server for internet access. For more information, see Configure web proxy for Azure Stack HCI.

Removal of GMSA accounts

In this release, the Group Managed Service Accounts (gMSA) created during the Active Directory preparation are removed. For more information, see Prepare Active Directory.

Capacity management

In this release, you can add and remove servers, or repair servers from your Azure Stack HCI system via the PowerShell.

For more information, see Add server and Repair server.

ReFS deduplication and compression

This release introduces the Resilient File System (ReFS) deduplication and compression feature designed specifically for active workloads, such as Azure Virtual Desktop (AVD) on Azure Stack HCI. Enable this feature using Windows Admin Center or PowerShell to optimize storage usage and reduce cost.

For more information, see Optimize storage with ReFS deduplication and compression in Azure Stack HCI.