Home/Library/Azure Arc Cost Considerations
Explainer · Azure · Hybrid · Updated June 2026

Azure Arc and Hybrid Cost Considerations Explained

The most common misconception about Azure Arc is that connecting servers costs money. It does not. The Arc control plane is free, and every dollar of Arc spend comes from the add-on services you choose to enable on top. Here is exactly what is free and what is not.

Last updated: June 2026

Key takeaways

Azure Arc is a free management control plane: connecting servers, Kubernetes, and data services and using inventory, tagging, Resource Graph search, and RBAC costs nothing. Cost appears only when you enable Azure services on Arc-connected resources, such as Microsoft Defender for Cloud, Azure Monitor, Update Manager, or extended security updates, each billed at its own rate. Control Arc spend by enabling those add-ons selectively, not estate-wide.

  • The Arc core control plane (inventory, tags, Resource Graph, RBAC) is free.
  • Paid items are add-on services: Defender, Monitor, Update Manager, extended security updates.
  • Azure Monitor cost is driven by log ingestion and retention, so scope it.
  • Tag and group Arc resources so hybrid spend is attributable and anomalies show.

Azure Arc is Microsoft's hybrid and multi-cloud management plane that projects on-premises servers, Kubernetes clusters, and data services into Azure so they can be governed like native resources. For cost it matters because the projection itself is free, and the spend comes entirely from the Azure services you layer on top of Arc-connected resources. This article is part of our Azure cluster; the pillar it links up to is the complete guide to Azure cost optimization. Understanding what Arc bills for is a See step in our See, Cut, Lock, Run method.

Is Azure Arc free?

The Azure Arc core control plane is free. As of June 2026, per the Azure Arc pricing page, connecting servers, Kubernetes clusters, and data services to Arc and using resource inventory, tagging, Azure Resource Graph search, role-based access control, and basic management tools such as Run Command and the Custom Script Extension costs nothing. You begin paying only when you enable Azure services on those Arc-connected resources. This is the single most important fact for budgeting Arc: the management layer is not the cost, the services you attach to it are. Verify the current details on the linked Azure page before acting, because pricing changes.

CapabilityCostNotes
Connecting servers and clusters to ArcFreeThe core control plane
Inventory, tags, Resource Graph, RBACFreeOrganize and query at scale
Run Command, Custom Script ExtensionFreeBasic management actions
Microsoft Defender for CloudPaidPer server per month, per plan
Azure MonitorPaidBy log ingestion and retention
Update Manager, extended security updatesPaidPer managed or covered machine

What does Azure Arc actually charge for?

Azure Arc charges for the add-on Azure services you run on Arc-connected machines, never for Arc itself. The common billable items are Microsoft Defender for Cloud plans charged per server per month, Azure Monitor charged by log ingestion volume and retention, Azure Update Manager for orchestrating patching, extended security updates for operating systems past end of life, and Arc-enabled SQL Server or Kubernetes capabilities. Each of these has its own meter and would cost the same on a native Azure VM, so the right mental model is that Arc simply lets you point Azure services at machines that live outside Azure. Budgeting Arc is therefore an exercise in deciding, per machine, which paid services actually earn their cost.

Hybrid spend creeping up through Arc add-ons?

Our Azure cost audit inventories which paid services are enabled across your Arc estate, switches off the ones adding no value, scopes Monitor ingestion, and makes hybrid cost attributable. On the performance model you pay only from realized savings. No savings, no fee.

Book an Azure cost audit →

How do you control Azure Arc hybrid cost, step by step?

Because the control plane is free, every step targets the add-on services and the data they generate.

  1. Inventory which paid services are enabledList every Arc-connected machine and the billable add-ons switched on for each, such as Defender plans or Monitor. The result is a clear map of where Arc cost actually originates.
  2. Enable add-ons only where they add valueTurn off Defender and other paid services on machines that do not need them rather than enabling estate-wide by default. The result is paying for protection and monitoring only where it matters.
  3. Scope Azure Monitor data collectionLimit the metrics and logs collected from Arc servers and set retention deliberately, since ingestion and retention drive Monitor cost. The result is the largest variable Arc cost brought under control.
  4. Govern extended security updatesBuy extended security updates through Arc only for machines that still need them and upgrade or decommission the rest. The result is end-of-life support cost confined to genuine need.
  5. Tag and group Arc resources for allocationApply tags and management groups so hybrid cost is attributable and anomalies surface alongside native spend. The result is hybrid resources governed like everything else in Azure.

Does Azure Arc reduce hybrid cloud costs?

Azure Arc is a free management layer, so it adds no baseline cost, and it can lower hybrid cost indirectly by giving one place to inventory, govern, and apply policy across on-premises and multi-cloud resources. The savings come from the visibility and governance Arc enables, not from any Arc discount, and only materialize if you enable the paid add-on services selectively. Used carelessly, with Defender and Monitor switched on across an entire estate by default, Arc can quietly grow a hybrid bill; used deliberately, it is the place where hybrid cost becomes visible and controllable. That governance posture is the Lock step in our method, and it connects to the compute-side levers in our guide to Azure VM Scale Sets and autoscale for cost efficiency.

Free and paid boundaries, service names, and meters reflect Azure as of June 2026. Verify current pricing on the linked Azure documentation before acting, because service packaging and rates change.

Go deeper · free guide

The Azure Cost Optimization Field Guide includes the Arc add-on inventory worksheet and the Monitor scoping checklist we apply on hybrid engagements. It is the downloadable companion to this article.

Frequently asked questions

Is Azure Arc free?

The Azure Arc core control plane is free. Connecting servers, Kubernetes clusters, and data services to Azure Arc and using inventory, tagging, Azure Resource Graph search, role-based access control, and basic management tools such as Run Command costs nothing. You pay only when you enable Azure services on those Arc-connected resources, such as Microsoft Defender for Cloud, Azure Monitor, Update Manager, or extended security updates, each billed at its own rate. Verify current pricing on the Azure Arc pricing page.

What does Azure Arc actually charge for?

Azure Arc charges for the add-on Azure services you run on Arc-connected machines, not for Arc itself. The common billable items are Microsoft Defender for Cloud plans per server per month, Azure Monitor log ingestion and retention, Azure Update Manager for managed update orchestration, extended security updates for end-of-life operating systems, and Arc-enabled SQL Server or Kubernetes features. The control plane that organizes and queries the resources is free.

How do I control Azure Arc hybrid cost?

Control Arc cost by inventorying which paid add-ons are enabled per machine, switching off Defender plans and other services where they add no value, scoping Azure Monitor data collection and retention since ingestion drives cost, buying extended security updates only for machines that still need them, and tagging Arc resources so hybrid spend is attributable. The control plane is free, so all the cost levers sit in the add-on services.

Does Azure Arc reduce hybrid cloud costs?

Azure Arc itself is a free management layer, so it does not add baseline cost, and it can reduce hybrid cost indirectly by giving one place to inventory, govern, and apply policy across on-premises and multi-cloud resources. The savings come from the visibility and governance it enables, not from Arc pricing, provided you enable paid add-on services selectively rather than across the whole estate.

The short version

Azure Arc is free at the control plane; the bill is the add-on services you attach to it. Inventory what is enabled, switch on Defender and Monitor only where they earn their cost, scope Monitor ingestion, govern extended security updates, and tag everything. When you want your Arc estate inventoried and the add-on spend right-sized, that is exactly what our Azure cost optimization service delivers.

Primary sources & further reading

Cloud pricing and service behavior change frequently. Verify the specifics in this guide against the providers’ own current documentation and the FinOps Foundation: Azure pricing ↗, Azure documentation ↗ and FinOps Foundation Framework ↗. This article also reflects Cloud Cost Room’s hands-on, vendor-neutral engagement experience.

Written by Morten Andersen

Co-founder of Cloud Cost Room and a FinOps Certified Practitioner, with 20 years in IT and cloud cost optimization across AWS, Azure, Google Cloud and OCI. More about Morten →

More from the Azure Cost Optimization cluster

See every guide in the Azure Cost Optimization cluster →

The Cloud Cost Brief

Cloud pricing moves. We tell you when it matters.

New commitment instruments, FOCUS changes, hyperscaler pricing shifts, and the plays that actually move a bill. No schedule, no filler.

Subscribe · Work email only