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
Azure Toolkit for IntelliJ: Introducing the enhanced Java Code Quality Analyzer!
Discover the latest updates to the Azure Toolkit for IntelliJ, featuring an enhanced Java Code Quality Analyzer to help you write cleaner, saf...
Azure Boards + GitHub: Recent Updates
Over the past several months, we’ve delivered a series of improvements to the Azure Boards + GitHub integration. Whether you’re tracking...
Introducing the Azure MCP Server
This post introduces the Azure MCP Server, bringing the power of the cloud to your AI agents. The post Introducing the Azure MCP Server appear...
Azure OpenAI Service now authorized for all U.S. Government data classification levels
In the coming years, artificial intelligence will continue to be foundational to technical innovations for national security missions. Already...
GPT-4.1 is now available at Azure AI Foundry
Azure AI Foundry and AOAI (Azure OpenAI Services) keeps on getting better all the time! The latest addition in Azure AI Foundry (as of April 1...
Introducing Region Selection in Azure Cosmos DB Data Explorer for NoSQL Accounts
You asked—we delivered! Users can now manually select the region Data Explorer sends requests to! When you use Entra Authentication with NoSQL...
Microsoft Attempts to Fix Microsoft Graph PowerShell SDK Problem with Azure Automation
V2.26 and V2.26.1 of the Microsoft Graph PowerShell SDK were low-quality, buggy disasters. Microsoft aims to fix the problem in the next versi...