
Introduction
AKS Automatic is built to make production-ready Azure Kubernetes clusters easier to create. But "automatic" describes how the cluster is configured, not how it's billed. There's no single all-inclusive price.
Your bill depends on the management tier, worker-node pools, storage, networking, monitoring, security add-ons, region, and scaling behavior. Teams that budget only for the cluster itself tend to be surprised by the rest.
According to Flexera's 2026 report, organizations estimate 29% of cloud spend is wasted.
This guide separates AKS Automatic from AKS pricing tiers, breaks down recurring costs, compares lower- and higher-cost setups, and shows how to build a realistic budget. Prices are US list prices, checked November 18, 2026.
Key Takeaways
- AKS Automatic is a managed cluster mode; the Azure resources underneath are billed at standard rates.
- Nodes, disks, networking, and logs often outweigh any control-plane fee.
- Lower-cost setups use modest node pools, right-sized disks, and capped logging.
- Higher-cost setups buy capacity, availability, and compliance.
- Estimate with the Azure Pricing Calculator plus a real workload inventory.
How Much Does AKS Automatic Cost? (Pricing Overview)
AKS Automatic has no universal monthly price. The final bill reflects the VMs, disks, load balancers, and monitoring services created for your cluster.
The classic budgeting mistake is treating "managed" as "all-inclusive." Worker nodes, persistent volumes, load balancers, egress, and monitoring all bill separately.
How Automatic Relates to AKS Tiers
Microsoft documents Automatic as a cluster SKU and Free, Standard, and Premium as management tiers. The AKS pricing page shows no Automatic-specific per-cluster fee, and Free cluster management costs nothing.
One conflict is worth flagging: some Microsoft pages describe a Free-tier default, while the tier comparison says Automatic is preconfigured for Standard. Confirm your cluster's actual tier before estimating its control-plane charge or SLA.
Typical Cost Scenarios
The inputs below are East US, USD, pay-as-you-go list prices. They're building blocks, not a cluster total.
| Input | List price |
|---|---|
| Standard_D2s_v5 Linux VM | $0.096/hour (about $70/month at 730 hours) |
| Standard SSD E10 disk (128 GiB) | $9.60/month |
| Standard Load Balancer | First 5 rules $0.025/hour; $0.005/GB processed |
| Log Analytics ingestion | $2.30/GB |
- Dev/test: a small node pool, Standard SSD volumes, and limited log ingestion. Compute dominates.
- Standard production: more nodes across availability zones, a load balancer, and the default monitoring stack. Logs and networking grow noticeably.
- Enterprise: multiple node pools, GPU or specialized compute, high-performance disks, heavy traffic, Defender, and backup. Storage and data transfer can rival compute.

These figures cover Azure infrastructure only. Engineering labor, support contracts, third-party tools, and application costs are extra. Re-check every number in the Azure Pricing Calculator before you budget, since prices change.
Key Factors That Affect the Cost of AKS Automatic (and Cost Breakdown)
Automatic simplifies operations, but it doesn't remove the cost of capacity, performance, availability, and observability decisions.
AKS Management Tier and Control Plane
- Free supports up to 1,000 nodes with no financially backed uptime SLA.
- Standard and Premium support up to 5,000 nodes and include an Uptime SLA, with 99.95% API-server availability when availability zones are used.
- Automatic adds a 99.9% pod-readiness SLA and a separate 99.9% commitment for managed system components on zone-enabled clusters.
- Microsoft documentation conflicts on whether long-term support requires Standard or Premium, and the pricing page lists no numeric Premium fee. Confirm current tier requirements before you plan around LTS.
Worker Nodes, Node Pools, and Autoscaling
Worker nodes are Azure VMs. Cost moves with VM family, vCPU and memory, OS, region, node count, and specialized hardware such as GPUs. Automatic uses node auto-provisioning to pick VM SKUs for your workloads, and new clusters include managed system node pools.
Watch for idle capacity. Oversized pod requests, daemonsets, and minimum node counts leave you paying for headroom the apps never use.
Storage, Persistent Volumes, and Disk Performance
- The default
managed-csiclass uses Standard SSD LRS. - Disks bill by fixed SKU size, not the GiB you requested, and PVCs can't be shrunk.
- Premium SSD v2 bills for capacity, IOPS, and throughput separately.
- Snapshots appear as their own line items.
- The default reclaim policy deletes the disk with its PV, but retained or unattached disks keep billing by type and size.
- Azure Files uses different billing models (provisioned v1 monthly rate, provisioned v2 hourly).
Networking, Data Transfer, and Public Exposure
AKS itself doesn't create most of these charges. The connected Azure services do.
- Load balancers bill for rules and data processed.
- Public IPs vary by SKU; static IPs bill whether or not they're attached.
- Application Gateway adds gateway-hour, capacity-unit, and data transfer charges.
- NAT Gateway bills for resource hours and processed data.
- The first 100 GB of monthly egress is free; beyond that, rates vary by destination and volume.
Monitoring, Security, and Other Add-ons
Automatic's default monitoring includes Managed Prometheus, Container Insights, and Grafana dashboards. Microsoft notes each can incur cost. Analytics Logs bill by ingestion, with 31 days of retention included.
Other recurring items:
- Defender for Containers (priced through Defender for Cloud)
- Azure Container Registry tiers (Basic, Standard, and Premium include 10 GB, 100 GB, and 500 GB)
- AKS Backup, where snapshot charges still apply
Cost Breakdown by Billing Pattern
- One-time: deployment configuration, migration, integration, and policy setup. These are mostly labor, not Azure usage charges.
- Recurring: control-plane fees where applicable, node runtime, storage, networking, monitoring, security, registry, and backup.
- Variable: autoscaling peaks, egress, storage growth, snapshots, and upgrades.

Keep list pricing, discounted commitments, usage charges, and internal operating costs in separate columns of your budget.
Low-Cost vs Higher-Cost AKS Automatic Configurations: How to Estimate the Right Budget
Cheaper isn't automatically better. The right design balances performance, availability, resilience, compliance, and operational effort.
Lower-Cost Configuration
A dev, test, or low-traffic cluster fits here:
- Modest general-purpose nodes
- Limited persistent storage on Standard SSD
- Capped log retention
- Minimal public exposure
- Scaling that lets idle capacity fall
The trade-offs are lower resilience, fewer performance guarantees, slower scaling, and poor fit for mission-critical workloads.
Higher-Cost Configuration
Production and enterprise clusters typically need:
- Larger or multiple node pools
- Zone-redundant availability
- Performance-oriented disks
- Redundant networking
- Broad observability and security services
- Steady baseline capacity
Those costs buy measurable outcomes: uptime, latency, recovery capability, compliance, and headroom for peaks.
Budget Estimation Workflow
- Inventory the workload. Map clusters, environments, services, and replicas. Note CPU and memory demand, peak-to-average traffic, storage size and performance, log retention, and data transfer.
- Price each component. Add every node pool and connected service to the Azure Pricing Calculator with your region, tier, OS, and runtime.
- Build three estimates. Model baseline, normal, and peak. Apply savings from autoscaling, scheduled shutdowns, Spot, reservations, or savings plans only where the workload tolerates them.
- Add contingency and validate. Document assumptions, include a buffer for growth and price changes, then compare against Azure Cost Management data after launch.

After launch, Azure budgets refresh about every 24 hours and send alerts, but they don't stop spending. AKS Cost Analysis, available on Standard and Premium clusters, breaks costs down by Kubernetes construct.
What Most People Miss When It Comes to AKS Automatic Cost
Defaults hide usage costs. Monitoring, networking, and autoscaling are easy to switch on without seeing what they'll bill. Review every default and optional component before deployment.
Storage waste piles up quietly. These keep billing long after you stop using them:
- Unattached disks and unused PVCs
- Stale snapshots
- Oversized disks
- Performance tiers beyond what the app needs
Microsoft confirms unattached disks continue to incur charges by type and size.
Lucidity's Lumen gives real-time visibility into every block-storage volume across clouds and flags four idle-disk types: unattached, reserved, unmounted, and zero-I/O. These can account for up to 70% of unused block-storage spend. Lumen also analyzes IOPS, throughput, latency, and cost to suggest better tiers. That does not change AKS base pricing; it addresses the disk waste around it.
Don't commit too early. Savings plans lock in hourly spend for one or three years. Rightsize your actual baseline first.
Don't cut blindly. Trimming monitoring, resilience, or disk performance can save money but break your service-level targets. Test the effect first.
Conclusion
AKS Automatic simplifies cluster deployment, but your total price still reflects the Azure capacity and supporting services the workload consumes. Budget by separating management-tier charges from compute, storage, networking, monitoring, security, and variable usage.
Build a documented, scenario-based estimate, validate it in the Azure Pricing Calculator, and keep checking it against Azure Cost Management data. A single headline price won't tell you what you'll pay.
Frequently Asked Questions
What is the latest version of AKS?
As of November 18, 2026, the AKS release tracker lists Kubernetes 1.37.1 and 1.37.0. Kubernetes 1.37 went GA on AKS in a release dated October 25, 2026. That's separate from the AKS Automatic feature itself.
How much does AKS Automatic cost per month?
There's no universal monthly price. It depends on node pools, runtime, storage, networking, monitoring, management tier, region, and workload demand.
Is AKS Automatic a separate pricing tier?
No. Automatic is a cluster SKU, while Free, Standard, and Premium are management tiers. Verify your cluster's tier in Microsoft's documentation, since some pages differ.
What is included in the price of AKS Automatic?
The managed cluster experience, including preconfigured autoscaling and managed system components. Worker VMs, disks, networking, monitoring, and security add-ons bill separately.
Is AKS Automatic suitable for production workloads?
Yes. It reached GA on September 16, 2025, and Microsoft recommends it for most production workloads. Windows nodes aren't supported, and you can't migrate from base AKS, so validate features first.
How can I reduce AKS Automatic costs?
Rightsize nodes and pods, tune autoscaling, delete orphaned disks and snapshots, and control logs and egress. Schedule non-production shutdowns, and use Spot or commitments only where safe.