Microsoft announced Azure Arc as a way to extend Azure management and services to infrastructure outside Azure, including on-premises and other clouds. The announcement positioned Arc as a hybrid approach built around consistent governance and management tools across locations.
At Microsoft Build 2020, Microsoft expanded Arc’s scope by putting Azure Arc-enabled Kubernetes into public preview. This milestone focused on letting organizations connect and manage Kubernetes clusters running in data centers, edge locations, and other clouds from Azure.
Microsoft’s Ignite 2020 “Book of News” described Azure Arc-enabled data services as being in public preview, including support for running Azure SQL Managed Instance and Azure Database for PostgreSQL Hyperscale on customer infrastructure. This framed Arc as more than inventory and policy—it also aimed to bring Azure’s managed-data experience to Kubernetes anywhere.
Microsoft moved Azure Arc-enabled servers to general availability for managing Windows and Linux servers outside Azure. This provided a practical foundation for hybrid operations by bringing non-Azure machines into Azure for inventory, tagging, and policy-based governance.
Azure Arc-enabled Kubernetes became generally available, enabling production use for attaching CNCF-conformant Kubernetes clusters to Azure for centralized management. This was a major step toward multi-cloud consistency for container platforms by using Azure Resource Manager concepts (like RBAC and tagging) across clusters.
As Arc matured, Microsoft emphasized GitOps-based configuration management for Kubernetes connected to Azure Arc. GitOps is an approach where desired configuration is stored in Git and applied automatically, helping teams standardize deployments across many clusters in different locations.
Azure Arc-enabled SQL Managed Instance reached general availability, allowing customers to run Azure’s SQL Managed Instance service on their own Kubernetes clusters (on-premises or other clouds). This milestone linked Arc’s hybrid control plane with a key data platform service, supporting scenarios like data residency and low-latency local processing.
At Microsoft Ignite 2021, Microsoft announced additional Azure Arc previews aimed at managing resources beyond individual servers and Kubernetes clusters, including lifecycle management for VMs on VMware vSphere and Azure Stack HCI from the Azure portal. This signaled a shift toward treating non-Azure infrastructure as manageable, Azure-governed “resources.”
Microsoft introduced SQL Server enabled by Azure Arc, aiming to bring inventory, governance, and security features to SQL Server deployments without requiring migration to Azure. The announcement tied Arc to the SQL Server 2022 era and included a consumption-based billing model for certain Arc-enabled SQL capabilities.
Microsoft continued shipping frequent Arc-enabled SQL updates, such as improvements for encryption management (for example, managing transparent data encryption settings using Azure CLI). These releases reflected Arc’s role as an ongoing hybrid operations layer, not a one-time onboarding tool.
Microsoft announced new options for Extended Security Updates (ESU) enabled by Azure Arc for Windows Server 2012/R2 and SQL Server 2012, delivered through the Azure portal. This connected Arc’s hybrid inventory and policy model with a concrete security and compliance outcome: keeping legacy systems patched while modernizing operations.
Microsoft announced general availability of VMware vSphere enabled by Azure Arc, allowing organizations to manage VMware resources through Azure and to onboard VMware VMs at scale for Azure management and security services. This marked a clear hybrid/multi-cloud integration milestone by extending Arc’s reach into a widely used non-Microsoft virtualization platform.
Microsoft Azure Arc: launch and hybrid/multi-cloud integration milestones (2019–2023)