Loading...

Registration and Arc extension improvements in Azure Stack HCI

Registration and Arc extension improvements in Azure Stack HCI

We are happy to let you know that we have improved the registration process for the HCI cluster and the management of Arc extensions. These changes were made based on feedback and survey results we received from our community.

 

Register cluster and associated Arc for server resources in same Resource Group

Previously, Azure Stack HCI registration required two Resource Groups, one for the cluster resource and another for Arc for server resources. However, now you can register both the Azure Stack HCI cluster and Arc for Server resources in the same Resource Group by passing the existing Resource Group information. This workflow is supported by both PowerShell and Windows Admin Center. For more detailed information, please see our documentation Register Azure Stack HCI with Azure - Azure Stack HCI | Microsoft Learn

unifiedrg (Time 0_02_33;24).png

 

Extension Management improvements

The Azure Stack HCI extension management has been upgraded to include more features. In addition to installing and removing extensions and showing basic status information, it now provides version and update information. It also allows users to enable/disable automatic upgrades, perform manual upgrades, and access troubleshooting workflows. If an upgrade fails, it even has an automatic rollback feature to the previously installed version. More information can be found in our documentation, Azure Arc extension management on Azure Stack HCI. - Azure Stack HCI | Microsoft Learn

 

extension management.png

 

Extensions that will be GAing in coming months:

  • Azure Monitor Agent extension
  • Azure Site Recovery Agent
  • Windows Admin Center
  • Telemetry and diagnostics [Azure-managed mandatory extension]
  • Life cycle manager [Azure-managed mandatory extension]
  • Remote Support [Azure-managed mandatory extension]

 

Azure-managed mandatory extensions

In the coming months, we'll be introducing mandatory extensions that will be managed by Azure. These mandatory extensions will enable us to independently deliver, manage, and maintain core capabilities without relying on operating system updates and releases. These extensions are crucial for the efficient functioning of our HCI systems, and to enhance the quality of Azure Stack HCI. You, as a user, will be able to control the behavior of these extensions through the Settings menu, as shown in the image below. The first mandatory extension we will introduce is TelemetryAndDiagnostics.

 

telemetryanddiagnostic settings.png

 

 

The mandatory extension will be installed after Azure Stack HCI registration. We will ask for user's consent to install mandatory extensions when you are registering a new Azure Stack HCI cluster. If you already have a cluster, we will ask for your consent through the Azure portal on the Azure Stack HCI resource "Overview" and "Extensions" pages.

 

We hope these improvements will make your experience smoother, quicker, and more productive. We value your feedback, so please feel free to leave a comment on this blog or contact me directly.

Published on:

Learn more
Azure Stack Blog articles
Azure Stack Blog articles

Azure Stack Blog articles

Share post:

Related posts

Azure SDK Release (March 2026)

Azure SDK releases every month. In this post, you find this month's highlights and release notes. The post Azure SDK Release (March 2026) appe...

2 days ago

Specifying client ID and secret when creating an Azure ACS principal via AppRegNew.aspx will be removed

The option to specify client ID and secret when creating Azure ACS principals will be removed. Users must adopt the system-generated client ID...

2 days ago

Azure Developer CLI (azd): Run and test AI agents locally with azd

New azd ai agent run and invoke commands let you start and test AI agents from your terminal—locally or in the cloud. The post Azure Developer...

10 days ago

Microsoft Purview compliance portal: Endpoint DLP classification support for Azure RMS–protected Office documents

Microsoft Purview Endpoint DLP will soon classify Azure RMS–protected Office documents, enabling consistent DLP policy enforcement on encrypte...

10 days ago

Introducing the Azure Cosmos DB Plugin for Cursor

We’re excited to announce the Cursor plugin for Azure Cosmos DB bringing AI-powered database expertise, best practices guidance, and liv...

11 days ago

Azure DevOps Remote MCP Server (public preview)

When we released the local Azure DevOps MCP Server, it gave customers a way to connect Azure DevOps data with tools like Visual Studio and Vis...

11 days ago

Azure Cosmos DB at FOSSASIA Summit 2026: Sessions, Conversations, and Community

The FOSSASIA Summit 2026 was an incredible gathering of developers, open-source contributors, startups, and technology enthusiasts from across...

12 days ago

Azure Cosmos DB at FOSSASIA Summit 2026: Sessions, Conversations, and Community

The FOSSASIA Summit 2026 was an incredible gathering of developers, open-source contributors, startups, and technology enthusiasts from across...

12 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy