What is Azure Arc?

Simplify hybrid IT with Azure Arc: manage, secure, and monitor servers, Kubernetes, and databases across cloud and on-premises.

What is Azure Arc?
What is Azure Arc?

Azure Arc is a set of Microsoft technologies that extends Azure management to servers, Kubernetes clusters and SQL Server instances that run outside Azure: in your own datacentre, at the edge, or in another cloud such as AWS or Google Cloud.

Once something is connected, it appears in the Azure portal as a resource, just like an Azure VM, so you can manage it with the same tools: Azure Policy, role-based access control (RBAC), Microsoft Defender for Cloud, Azure Monitor and Azure Update Manager.

In this post I'll explain what Azure Arc does, what it can manage, how it works and what it costs, then point you to my step-by-step guides for connecting your first server.

Azure Arc at a glance

  • What it is: a way to manage resources outside Azure with the same tools you use for Azure resources.
  • What it can manage: Windows and Linux servers, Kubernetes clusters, SQL Server, and VMs on VMware vSphere, System Center Virtual Machine Manager (SCVMM) and Azure Local.
  • How it connects: a lightweight agent that only makes outbound HTTPS connections to Azure.
  • What it costs: the core management features are free. You pay for the Azure services you choose to add.

What does Azure Arc actually do?

Most organisations don't run everything in Azure. Servers in a datacentre, workloads in another cloud and kit in branch offices each tend to come with their own tools for patching, monitoring and security, which is how you end up with several consoles and several versions of the truth.

Azure Arc gives those resources a representation in Azure Resource Manager, the management layer behind every Azure resource. It doesn't move or migrate anything. Your servers keep running exactly where they are; what changes is that you can now manage them with Azure tools. For example:

  • Want your on-premises servers to follow the same configuration rules as your Azure VMs? Assign the same Azure Policy to both.
  • Need Extended Security Updates for Windows Server 2016 machines you can't upgrade before support ends? Enrol them and pay for them through the Azure portal.
  • Want one list of every server you run, wherever it lives? Query it with Azure Resource Graph.

What can Azure Arc manage?

Azure Arc is a family of offerings rather than a single product. Which one you use depends on what you're connecting.

Azure Arc-enabled servers

Azure Arc-enabled servers lets you manage Windows and Linux machines that run outside Azure, whether they're physical servers, VMs on Hyper-V or VMware, or instances in AWS or Google Cloud. You install a lightweight agent, the Azure Connected Machine agent, and the server appears in the Azure portal in the resource group you chose. From there you can apply Azure Policy, patch it with Azure Update Manager, monitor it with Azure Monitor, protect it with Microsoft Defender for Cloud and add extensions to it, much as you would with an Azure VM.

This is where most people start, and it's how Extended Security Updates for Windows Server are delivered.

Azure Arc-enabled Kubernetes

Azure Arc-enabled Kubernetes lets you connect any CNCF-certified Kubernetes cluster, whether it runs on-premises, on Azure Local or in another cloud such as AWS or Google Cloud. Each connected cluster appears in Azure alongside your AKS clusters. You can then deploy configuration from Git using GitOps (with Flux v2 or Argo CD), apply Azure Policy, monitor the cluster with Azure Monitor and protect it with Microsoft Defender for Containers.

SQL Server enabled by Azure Arc

SQL Server enabled by Azure Arc (often called Azure Arc-enabled SQL Server) connects SQL Server instances that run outside Azure. Once the server is Arc-enabled, the Azure extension for SQL Server discovers the instances on it and you get a single inventory of your SQL estate, with the version, edition, core count and databases for each one.

From there you can run best practices assessments, protect instances with Microsoft Defender for Cloud, use Microsoft Entra authentication with SQL Server 2022 and later, pay for SQL Server on a pay-as-you-go basis through Azure, and buy Extended Security Updates for versions that are out of support. It supports SQL Server 2014 and later. Some features, such as best practices assessment, depend on your licence type or operating system.

💡 Want to see it in action? I walk through Arc-enabling SQL Server step by step in Unleashing the Power of Azure Arc: Enabling SQL Server Across Hybrid Environments.

Azure Arc-enabled data services

Azure Arc-enabled data services is different from SQL Server enabled by Azure Arc. Instead of connecting SQL Server instances you already have, it lets you run an Azure data service, SQL Managed Instance enabled by Azure Arc, on a Kubernetes cluster in your own environment or another cloud. You get cloud-style benefits such as regular updates and elastic scale, while the data stays where you need it.

It needs an Arc-enabled Kubernetes cluster and an Azure Arc data controller, so it's a bigger step than connecting the servers you already have.

VMware vSphere, System Center VMM and Azure Local

Arc-enabled servers works from inside the operating system. Azure Arc-enabled VMware vSphere and Azure Arc-enabled System Center Virtual Machine Manager (SCVMM) also connect to the virtualisation platform itself, through a component called the Azure Arc resource bridge. That adds things the agent can't do on its own: discovering and inventorying VMs without installing anything on them, and creating, resizing, starting, stopping and deleting VMs from Azure. You can also let application teams provision their own VMs, controlled by Azure RBAC. Azure Local (previously Azure Stack HCI) uses the same approach for the VMs it runs.

If you're not sure which you need, Microsoft's advice is to start with Arc-enabled servers and add a resource bridge later.

Which Azure Arc offering do I need?

If you want to... Use How it connects
Manage physical servers or VMs in your datacentre or another cloud Azure Arc-enabled servers The Azure Connected Machine agent on each machine
Manage Kubernetes clusters outside Azure Azure Arc-enabled Kubernetes Arc agents deployed into the cluster
Inventory, secure and license existing SQL Server instances SQL Server enabled by Azure Arc An Arc-enabled server plus the Azure extension for SQL Server
Run SQL Managed Instance on your own infrastructure Azure Arc-enabled data services An Arc-enabled Kubernetes cluster plus a data controller
Create and manage VMware, SCVMM or Azure Local VMs from Azure Arc-enabled VMware vSphere, Arc-enabled SCVMM or Azure Local The Azure Arc resource bridge

How does Azure Arc work?

For servers, everything starts with the Azure Connected Machine agent. When you install it, it registers the machine with Azure and creates a resource for it, with its own resource ID, in the subscription, resource group and region you choose.

The agent only makes outbound connections, over HTTPS on TCP port 443, so you don't need to open inbound ports to your servers. It can connect directly to the internet, through a proxy server, or privately using Azure Private Link, and Azure Arc gateway can reduce the number of endpoints you need to allow through your firewall. If you're not sure your network allows them, check before you onboard anything.

Once a server is connected, the agent sends Azure a heartbeat every five minutes. If the heartbeats stop, the server's status changes to Disconnected, usually within 15 to 30 minutes, and changes back automatically when they resume. A server that stays disconnected for 45 days can expire and needs reconnecting. If a server won't connect, my troubleshooting guide covers the checks I run first.

Azure services reach the server through extensions, such as the Azure Monitor Agent, which the Connected Machine agent installs and manages. Kubernetes works in a similar way: you deploy Arc agents into the cluster and they make an outbound connection to Azure.

Arc-enabled servers is only for machines outside Azure, so you don't install the agent on Azure VMs.

Why use Azure Arc?

You'll often hear the benefit of Azure Arc described as a "single control plane". In practice, that comes down to a few very practical jobs.

One inventory of everything you run

Every connected server, cluster and SQL Server instance is an Azure resource, so you can query them all with Azure Resource Graph. A few lines of KQL will answer questions like "How many servers are still running Windows Server 2016?" or "Which SQL Server instances are running on Linux?" across Azure, your datacentre and other clouds at once, and Resource Graph queries don't cost anything extra.

💡 New to Resource Graph? Getting started with Azure Resource Graph shows you how to write your first queries.

The same security and governance rules everywhere

You can use Azure Policy, Azure RBAC and Microsoft Defender for Cloud with Arc-enabled resources in the same way as with Azure resources. For example, you can assign the built-in policy that audits Linux machines allowing remote connections from accounts without passwords, include Arc-connected servers in its scope, and your on-premises and AWS Linux servers appear in the same compliance report as your Azure VMs.

Extended Security Updates for Windows Server 2016 and SQL Server

If you have servers you can't upgrade before they reach end of support, Azure Arc is how you buy Extended Security Updates (ESUs) for them outside Azure. Windows Server 2016 reaches end of support on 12 January 2027. You can already enrol Arc-enabled Windows Server 2016 machines in ESUs from the Azure portal, and billing starts on 13 January 2027. ESUs enabled by Azure Arc are billed monthly through Azure, with no product keys to manage, and provide Critical and Important security updates for up to three years. You'll need licences with Software Assurance (or licences through SPLA or a server subscription) and version 1.62 or later of the agent.

SQL Server works the same way. SQL Server 2016 reached end of support in July 2026, and SQL Server 2014 ESUs run until 12 July 2027. Both can be covered through SQL Server enabled by Azure Arc.

💡 Planning for SQL Server 2016? SQL Server 2016 End of Support: ESU dates, pricing and what to do next covers the ESU dates and what they cost each year.

Treat ESUs as a bridge to an upgrade, not a long-term plan. Windows Server 2012 and 2012 R2 ESUs have already ended, so those servers no longer receive security updates.

Windows Server Management enabled by Azure Arc

If your Windows Server licences have active Software Assurance or are subscription licences, or you use Windows Server pay-as-you-go through Azure Arc, Windows Server Management enabled by Azure Arc gives your Arc-enabled servers several Azure services at no extra cost. They include Azure Update Manager, Change Tracking and Inventory, Azure Machine Configuration, Windows Admin Center in Azure and Best Practices Assessment, though some need Windows Server 2016 or later. You have to attest that your servers are covered before the benefits apply, and Log Analytics data ingestion is still charged. Windows Server 2025 machines can also use hotpatching once they're Arc-enabled.

💡 I've covered the benefits and pay-as-you-go licensing in more detail in Advanced Windows Server Management Enabled by Azure Arc.

How much does Azure Arc cost?

Connecting resources to Azure Arc doesn't cost anything on its own. Microsoft doesn't charge for the core Arc control plane features: organising resources with management groups and tags, searching them with Azure Resource Graph, controlling access with Azure RBAC and automating with templates and extensions. Arc-enabled VMware vSphere and SCVMM add inventory and VM lifecycle operations at no extra cost too.

What you pay for is the Azure services you choose to use on top, such as Microsoft Defender for Cloud, Azure Monitor and the Log Analytics data it collects, at their normal prices. ESUs and pay-as-you-go licensing for Windows Server and SQL Server are billed through Azure as well. Check each service's pricing before you roll it out across hundreds of servers.

Getting started with Azure Arc

I've written step-by-step guides for each stage, so rather than repeat them here, these are the ones I'd read, in order:

  1. How to onboard a Windows Server to Azure Arc
  2. Register and Manage Linux Servers with Azure Arc Tutorial
  3. Unleashing the Power of Azure Arc: Enabling SQL Server Across Hybrid Environments
  4. Updating the Azure Arc Agent (Connected Machine Agent)
  5. Troubleshooting Azure Arc for Servers

Final thoughts

Azure Arc won't replace every tool in your datacentre overnight, and it doesn't need to. Its real value is letting you apply the same policies, security tools, patching and inventory to everything you run, wherever it lives, while paying only for the Azure services you choose to use.

Start with one server, see what appears in the portal and build from there. If you get stuck, or there's an Azure Arc topic you'd like me to cover, let me know in the comments.