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.
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
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.
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 moreRelated posts
Microsoft Purview compliance portal: Endpoint Data Loss Prevention – Endpoint DLP support classification of Azure RMS protected Office documents
Endpoint DLP can now classify Office files stored in Windows devices that have Azure RMS protection applied. Classification will be triggered ...
Introducing Microsoft Azure Face Liveness
AI Builder – Use your own generative AI model from Azure AI Foundry in Prompt builder in Copilot Studio
We are announcing the ability to use your own generative AI model from Azure AI Foundry in prompt builder. This feature has reached general av...
Azure SDK Release (August 2025)
Azure SDK releases every month. In this post, you'll find this month's highlights and release notes. The post Azure SDK Release (August 2025) ...
Azure Developer CLI (azd) – August 2025
This post announces the August release of the Azure Developer CLI (`azd`). The post Azure Developer CLI (azd) – August 2025 appeared fir...
Azurite: Build Azure Queues and Functions Locally with C#
Lets say you are a beginner Microsoft Azure developer and you want to : Normally, these tasks require an Azure Subscription. But what if I tol...
Data encryption with customer-managed key (CMK) for Azure Cosmos DB for MongoDB vCore
Built-in security for every configuration Azure Cosmos DB for MongoDB vCore is designed with security as a foundational principle. Regardless ...
Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines
Building on our previous post about implementing dev-to-prod promotion with GitHub Actions, this follow-up demonstrates the same “build ...
Azure DevOps OAuth Client Secrets Now Shown Only Once
We’re making an important change to how Azure DevOps displays OAuth client secrets to align with industry best practices and improve our overa...